Files
repo-scoping/workplans/RREG-WP-0015-self-assessment-input-hygiene.md

2.7 KiB

id, type, title, domain, repo, status, owner, topic_slug, created, updated
id type title domain repo status owner topic_slug created updated
RREG-WP-0015 workplan Self-Assessment Input Hygiene capabilities repo-scoping active codex foerster-capabilities 2026-05-15 2026-05-15

Self-Assessment Input Hygiene

The first post-WP0014 self-assessment rerun proved that the acceptance boundary is doing useful work, but it also exposed a sharper input problem: repo-scoping was scanning its own runtime var/checkouts/ directory. That pulled checked-out copies of llm-connect, markitect, and other repositories into repo-scoping's own candidate graph and recreated the provider-routing false positive from foreign source trees.

This workplan keeps the self-improvement loop honest by making the source set for self-assessment match the repository, not its local runtime cache.

T01: Exclude Runtime Checkout State From Scanning

id: RREG-WP-0015-T01
status: done
priority: high

Prevent deterministic scanning from reading repo-local runtime state such as var/checkouts/ when the repository is analyzed from its working tree.

Acceptance criteria:

  • var/ runtime content is excluded from scanner file traversal.
  • A regression test proves nested checkout files do not produce LLM-provider facts for the parent repo.
  • Normal repository documentation, source, test, and manifest scanning still works.

Implementation note 2026-05-15: added var to the deterministic scanner's ignored directory set and covered the repo-scoping-like failure with test_scanner_ignores_runtime_var_checkouts. Runtime checkout files no longer contribute documentation, language, or LLM-provider facts to the parent repo.

T02: Capture Clean Post-Acceptance Self-Assessment

id: RREG-WP-0015-T02
status: todo
priority: high

Rerun repo-scoping self-assess after input hygiene is fixed and save a reviewable challenger artifact and comparison report.

Acceptance criteria:

  • The artifact is release-bound to the repo-scoping commit that generated it.
  • The artifact no longer includes files from var/checkouts/.
  • The comparison report clearly separates remaining candidate-generation quality issues from approved registry truth.
  • The artifact/report names make their relationship to WP0014/WP0015 clear.

T03: Triage Remaining Generator Quality Gaps

id: RREG-WP-0015-T03
status: todo
priority: medium

Use the clean rerun to identify the next generator-quality workplan.

Acceptance criteria:

  • Remaining missing expected capabilities are summarized.
  • Remaining forbidden or downgraded candidates are summarized with source refs and quality-gate outcomes.
  • The next workplan is scoped around generator improvements, not deterministic acceptance.