chickenbstrips/TheTree_mock
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: preserve P13-03 gate failures and bounded final repair inputs

Browse Source
This commit is contained in:
Takeshi
2026-10-13 03:45:23 +09:00
parent 1f6c46d9f5
commit 5f766c5bf1
10 changed files with 98 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/plans/original-completion-2026-10-02/execution/p13-03/P13_ORDER_FINAL_REPAIR_INPUT.md
+10
View File
@@ -0,0 +1,10 @@
# P13-03 final bounded repair input (root context, not implementation)
Original contract/spec/acceptance1 and repair cap2 remain unchanged. Repair1 used. Initial submitted7645c55149d3bebf3ed602cf3039b15b28fa376f records seven facilities,84slots,six non-facility categories. Root read-only diagnostic ran its --negative-checks: integrity pass,13 mutations rejected. This is not formal acceptance.
Observed defects to fix together:
1. Registered argv is python -B tools/check_p13_content_difference.py --verify-only. It exits2 because argparse lacks --verify-only. Add compatible read-only --verify-only and ensure mandatory negative checks are actually included in the formal registered invocation; preserve negative-checks alias if useful. No registry/spec changes.
2. Exact unchanged Runner reviewer body for initial candidate is905065bytes under default JSON-escaped guard; cap500000. ActualUTF8 body880555. diff441818/sources431771/validation_sources22198. Do not invoke known-over-cap formal review, change Runner core/cap, truncate evidence or split the original delivery. Deduplicate repeated definition catalogs, sources, search observations and long path/hash/record metadata within the allowed ledger; use stable IDs and checked references, retaining every facility,84slots, all matched line text and provenance. Preserve source data semantics and unknown statuses. Keep readable ledger concise with shared sections. Guard-byte total should be below450000 to leave room for final validation receipts/integration. Root will preflight the EXACT final packet. No shallow sample or omitted required rows.
3. Current-source plan status changes after start. expected() currently adds current_checkout work_packages SHA into the immutable ledger and insists on exact equality; integration against current main1f6c46d fails because that plan status was updated to in_progress. The frozen authority input is raw work_packages blob at contract basee1a1651, which remains verified. Use its actual base_git_blob provenance for the report, not a stale current_checkout hash. Record scope explicitly: live plan state is maintained separately, not content completion evidence. This is not permission to ignore stale game/assets/original sources; those still require exact current applicability/hash rejection. Other current files match. Do not regenerate a new candidate for every bookkeeping edit.
Do not edit original docs/spec, Runner core/state/policy, game, values, assets or outside allowed paths. No new task or repair cap reset. No engine, GUI or full regression. Preserve initial failure evidence in root checkpoint. Implement all original conditions, then run registered exact argv and negative rejection checks. Update output hashes/receipt consistently. Do not claim formal Claude review before Runner executes it.