Label planning artifacts as TEST_ONLY and update references

This commit is contained in:
Bill
2026-02-26 14:22:14 -07:00
parent ff75faf5cb
commit 9198a70d35
8 changed files with 30 additions and 17 deletions

View File

@@ -146,5 +146,5 @@ Start Phase A:
Parallel planning tranche (active):
- `sprint228_plan.md` to `sprint231_plan.md`
- baseline artifacts:
- `logs/taskitem_runs/spec_planning_baseline_20260226/fullstack_spec_readiness.json`
- `logs/taskitem_runs/spec_planning_baseline_20260226/deterministic_spec_readiness.json`
- `logs/taskitem_runs/TEST_ONLY_spec_planning_baseline_20260226/fullstack_spec_readiness.json`
- `logs/taskitem_runs/TEST_ONLY_spec_planning_baseline_20260226/deterministic_spec_readiness.json`

View File

@@ -72,3 +72,6 @@
- example product meta specs (10)
- Batch report:
- `docs/spec_hardening_batch_report_2026-02-26.md`
- Artifact isolation update:
- moved planning/hardening outputs to `logs/taskitem_runs/TEST_ONLY_*` paths.
- wrapper default now writes to `TEST_ONLY_spec_hardening_gate_*`.

View File

@@ -12,13 +12,13 @@ Corpora:
## Batch Artifacts
Drive batch:
- `logs/taskitem_runs/drive_spec_hardening_batch_20260226/results.jsonl`
- `logs/taskitem_runs/drive_spec_hardening_batch_20260226/summary.json`
- `logs/taskitem_runs/drive_spec_hardening_batch_20260226/quality_summary.json`
- `logs/taskitem_runs/TEST_ONLY_drive_spec_hardening_batch_20260226/results.jsonl`
- `logs/taskitem_runs/TEST_ONLY_drive_spec_hardening_batch_20260226/summary.json`
- `logs/taskitem_runs/TEST_ONLY_drive_spec_hardening_batch_20260226/quality_summary.json`
Example project meta batch:
- `logs/taskitem_runs/example_projectmeta_hardening_batch_20260226/results.jsonl`
- `logs/taskitem_runs/example_projectmeta_hardening_batch_20260226/summary.json`
- `logs/taskitem_runs/TEST_ONLY_example_projectmeta_hardening_batch_20260226/results.jsonl`
- `logs/taskitem_runs/TEST_ONLY_example_projectmeta_hardening_batch_20260226/summary.json`
## High-Density Outcomes

View File

@@ -1,8 +1,8 @@
# Spec Planning Baseline - 2026-02-26
Run artifacts:
- `logs/taskitem_runs/spec_planning_baseline_20260226/fullstack_spec_readiness.json`
- `logs/taskitem_runs/spec_planning_baseline_20260226/deterministic_spec_readiness.json`
- `logs/taskitem_runs/TEST_ONLY_spec_planning_baseline_20260226/fullstack_spec_readiness.json`
- `logs/taskitem_runs/TEST_ONLY_spec_planning_baseline_20260226/deterministic_spec_readiness.json`
## Results

View File

@@ -25,12 +25,12 @@ Planned and started:
## Baseline Evidence
- `logs/taskitem_runs/spec_planning_baseline_20260226/fullstack_spec_readiness.json`
- `logs/taskitem_runs/spec_planning_baseline_20260226/deterministic_spec_readiness.json`
- `logs/taskitem_runs/spec_planning_hardening_20260226/sprint228_before.json`
- `logs/taskitem_runs/spec_planning_hardening_20260226/sprint228_after.json`
- `logs/taskitem_runs/spec_planning_hardening_20260226/sprint228_hardened.md`
- `logs/taskitem_runs/spec_hardening_gate_20260226_s228_r2/report.json`
- `logs/taskitem_runs/TEST_ONLY_spec_planning_baseline_20260226/fullstack_spec_readiness.json`
- `logs/taskitem_runs/TEST_ONLY_spec_planning_baseline_20260226/deterministic_spec_readiness.json`
- `logs/taskitem_runs/TEST_ONLY_spec_planning_hardening_20260226/sprint228_before.json`
- `logs/taskitem_runs/TEST_ONLY_spec_planning_hardening_20260226/sprint228_after.json`
- `logs/taskitem_runs/TEST_ONLY_spec_planning_hardening_20260226/sprint228_hardened.md`
- `logs/taskitem_runs/TEST_ONLY_spec_hardening_gate_20260226_s228_r2/report.json`
Observed baseline:
- both sample docs currently return `needs_spec_hardening`
@@ -49,7 +49,7 @@ Pipeline hard-gate proof:
Reusable flow wrapper:
- `tools/mcp/run_spec_hardening_gate.sh`
- example invocation:
- `tools/mcp/run_spec_hardening_gate.sh sprint228_plan.md logs/taskitem_runs/spec_hardening_gate_20260226_s228_r2`
- `tools/mcp/run_spec_hardening_gate.sh sprint228_plan.md logs/taskitem_runs/TEST_ONLY_spec_hardening_gate_20260226_s228_r2`
## Explicit Completion Signal

View File

@@ -29,3 +29,8 @@ These are useful for history but should not be treated as current execution trut
## Rule For Next Agents
When docs disagree, trust newest dated execution tracker + run artifacts under `logs/taskitem_runs/`.
## Test-Only Artifact Rule
- Treat directories under `logs/taskitem_runs/TEST_ONLY_*` as validation artifacts only.
- Never treat markdown specs generated within `TEST_ONLY_*` directories as authoritative product specs.