2.1 KiB
2.1 KiB
Verify Stale Missing Hard Dependency Through Bundled CLI
Test Type
- forward skill execution
Purpose
- validate that a single agent can use
skills/repo-memory/to record confirmed knowledge with a missing hard dependency, runverify, and observe the expectedstaleoutcome
Preconditions
skills/repo-memory/assets/repo-memoryexists and is executable- the test runner can create a temporary Git repository fixture
- the repository fixture has a valid Git HEAD before verification starts
- the hard dependency path referenced by the entry does not exist
Inputs
SKILL_PATH=/.../skills/repo-memoryTMPDIR=/tmp/...DB_PATH=TMPDIR/repo-memory.dbREPO_PATH=TMPDIR/repo-fixtureMISSING_PATH=REPO_PATH/missing.txt
Execution Parameters
- one agent only
- per-agent timeout:
3m - overall timeout:
4m
Execution Steps
- Create a temporary Git repository fixture under
REPO_PATHand ensure it has an initial commit. - Ask the agent to use
$repo-memoryagainstDB_PATH. - Have the agent add one
confirmedentry that declaresMISSING_PATHas a hard dependency. - Have the agent run
verify, then inspect the result withlistandevents. - Capture the agent summary and the final entry status it reports.
Validation Commands
Run these from the main thread after the agent stops:
SKILL_PATH/assets/repo-memory verify --db DB_PATH --repo REPO_PATH
SKILL_PATH/assets/repo-memory list --db DB_PATH --repo REPO_PATH --status stale
SKILL_PATH/assets/repo-memory events --db DB_PATH --id 1
Expected Outcomes
verifyreports one stale entrylistreturns the target entry instaleeventsincludes amarked_staleevent for the target entry
Assertions
- the agent used the bundled CLI for the full verify flow
- the stale result is driven by the missing hard dependency, not by a generic command failure
- the final state is visible in both current listing output and event history
Cleanup
- keep the temporary DB and repo on failure
- remove temporary artifacts on success only if replay evidence is not needed