Files
ai-workflow-skill/docs/tests/repo-memory-skill/verify-stale-missing-hard-dependency-through-bundled-cli.md
T

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, run verify, and observe the expected stale outcome

Preconditions

  • skills/repo-memory/assets/repo-memory exists 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-memory
  • TMPDIR=/tmp/...
  • DB_PATH=TMPDIR/repo-memory.db
  • REPO_PATH=TMPDIR/repo-fixture
  • MISSING_PATH=REPO_PATH/missing.txt

Execution Parameters

  • one agent only
  • per-agent timeout: 3m
  • overall timeout: 4m

Execution Steps

  1. Create a temporary Git repository fixture under REPO_PATH and ensure it has an initial commit.
  2. Ask the agent to use $repo-memory against DB_PATH.
  3. Have the agent add one confirmed entry that declares MISSING_PATH as a hard dependency.
  4. Have the agent run verify, then inspect the result with list and events.
  5. 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

  • verify reports one stale entry
  • list returns the target entry in stale
  • events includes a marked_stale event 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