mirror of
https://github.com/Dicklesworthstone/coding_agent_session_search.git
synced 2026-09-22 11:59:25 +08:00
43203283cb
Continuation of 66cee372 ("chore(repo): reorganize evidence trees") — the
FTUI visual-parity bundle and the cass bakeoff validation note still lived at
the top of `docs/`, surrounded by living references. Move them into the
named subtrees the prior reorg established and tighten the scratch-output
ignore list so the next round of skill-loop runs can't re-pollute the repo
root.
Moves (content-identical, verified by diff against deleted blobs):
- `docs/ftui_feature_audit.md` → `docs/artifacts/ftui-parity/feature_audit.md`
- `docs/ftui_parity_baseline_bundle.md` → `docs/artifacts/ftui-parity/baseline_bundle.md`
- `docs/ftui_visual_parity_manifest.json`→ `docs/artifacts/ftui-parity/visual_parity_manifest.json`
- `docs/cass_bakeoff_validation.md` → `docs/reference/cass_bakeoff_validation.md`
The first three are "captured run artifact" by definition (manifest + audit
+ baseline bundle) so they belong under `docs/artifacts/`. The bakeoff note
is a living reference (operators consult it; it isn't a snapshot of one
campaign), so it goes under `docs/reference/`.
`docs/ftui_visual_parity_rubric.md` keeps its top-of-`docs/` location (it's
the active scoring rubric, a living reference) but its single pointer to the
old manifest path is updated to the new artifact location.
`docs/artifacts/README.md` registers the new `ftui-parity/` subtree and
explains why the rubric stays put while the manifest moves.
`.gitignore` adds repo-root scratch outputs that the agent-ergonomics
skill loop kept regenerating and accidentally tracking:
/DASHBOARD.md, /final_dashboard.md, /baseline.md, /architecture.md,
/pass*.md, /duplication_map.*, /skill_inventory.json, /slop_scan.md,
/loc_delta_*.numstat, /baseline_*.log, /cargo_*.log,
/touched_rustfmt_check.log, /validation_report.json,
/per_query_scores.json
Durable plans go under `docs/planning/`, durable evidence under
`docs/artifacts/`, reference guides under `docs/reference/` — these patterns
hard-block the corresponding scratch outputs from creeping back in at root.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Preserved Project Artifacts
This directory holds durable evidence bundles that are useful for future maintenance but are not source code, runtime state, or live issue-tracker data.
migration-baseline/contains the frankensearch/FAD migration baseline used byscripts/migration_e2e_validate.sh.ftui-parity/contains reviewed FTUI visual-parity audit evidence, baseline bundle notes, and the machine-readable parity manifest. The active scoring rubric remains indocs/ftui_visual_parity_rubric.mdbecause it is a living reference, not a captured run artifact.no-mock-audit.mdis the durable audit narrative for the no-mock CI policy; the machine-enforced allowlist lives intests/policies/.refactor-runs/contains preserved simplification/refactor proof bundles from prior skill-loop passes.
Archived proof cards may mention their original capture paths, such as
refactor/artifacts/..., because those command transcripts are preserved as
historical evidence. For current references, use the paths under this directory.
Transient local logs, ad-hoc command output, temporary databases, and generated
test results should stay ignored. In particular, tests/artifacts/ is for
local test/profiling output; move only reviewed, durable evidence here when it
has long-term maintenance value.