P04-01: 同時発生の更新規約

docs/plans/original-completion-2026-10-02/execution/p04-01/CHECKER_PROTOCOL.md

@@ -1,52 +1,26 @@
-# Current checker protocol — repair22
+# Current checker protocol — repair29
 
-Source preparation, NOT RUN. ORDER_AUDIT.md and order-audit.json are the single
-current seven-domain table. REPAIR17–21 remain untouched historical records;
-their current-status and B1 power-credit claims are superseded.
+Worker **SOURCE-READY / NOTRUN**. [CURRENT_STATUS.md](CURRENT_STATUS.md) is canonical for execution facts; creation-time NOT RUN in REPAIR22–28 and runbooks is historical. [ORDER_AUDIT.md](ORDER_AUDIT.md) and order-audit.json give the eleven-phase/seven-domain audit. [D05_REMAINING_ORDER_CANDIDATE.md](D05_REMAINING_ORDER_CANDIDATE.md) is approval material only.
 
-The registry remains exactly15 conditions + EV. No accepted originals, counts,
-CurrentAlphaScope, three safety outcomes or30/88 denominator change. Original
-13/88 gains no credit. P04 main9b stays frozen; no integration is claimed.
+B = `/Users/korizatou114/Projects/TheTree-managed-worktrees/p04-01/.runtime/P04-01/build`.
+The checker remains a61 (`a61c5b496e656f60c66898e42500bc9a2d45f947690ce8f5f19a03984ebbc850`), with its registry unchanged. Fifteen conditions + EV, seven domains, three safety outcomes and30/88 denominator remain fixed. Original credit13/88 unchanged; P04 remains incomplete.
 
-C's NATIVE_RUNS / native_ownership / verify_native block is unchanged. C25 and
-all existing fixture cases remain. R's verify_shift_completion derives three
-distinct process IDs from the existing raw start/process/end joins, with all
-end flags, exit0 and complete SHA checks retained. The one1080 SALE joins the
-original serviceID and priceSnapshot via service.payment.<serviceID>, actual
-receipt entries and idempotency transaction ID; no fixed PID or ledger number.
+| Evidence | Root-measured current fact |
+| --- | --- |
+| B/p04-s4-native-r28 | 4/4 PASS; PIDs49940,50044,50078,50105 all ended; guards0; cleanup0. |
+| B/audit-support/p04-root-fb8b-s4-r01 | S4 controls and native receipts PASS. |
+| B/audit-support/p04-root-fb8b-local-r01 | Local8 PASS and registered validation fb8b PASS28.095s. |
+| B/audit-support/p04-raw-collect-r22 | Current collection, preserving raw and exact relocation/series SHA256 bindings. |
+| B/p04-evidence/index.json | Schema2; missing_conditions=[]; all15 conditions + EV mechanically verified. |
 
-S1 uses the full existing writer-<case>-observations Variant data in
-B/p04-s1-native-r02. The pre-travel ACTIVE reservation, requester/task, assigned
-staff and original staff_cell join the later boarded task and trip. Reserve
-exhaustion is measured before the normal tick, and depleted raw must show
-mana0 and the actual elevator unpowered. JSON summaries do not replace typed raw.
+Root-measured native product5f6bc11d/main9b1a18c1. Current product is B/audit-support/p04-r17-full-inputs-r01/product, not deb11300. Static current hashes and handler/function lines, plus exact proof pins, are in REPAIR29_STATIC_SOURCE.json. The index preserves source/config/input/environment applicability and native ownership joins; mechanical PASS does not grant D05 approval or original completion.
 
-S3 B1 remains a combined dependency/closure diagnostic. Its actual interruption
-reason is RELATED_FACILITY_INACTIVE. It supplies no power_stop evidence and no
-priority approval. The strict power-vs-closure order is D05 pending/unknown.
+C NATIVE_RUNS/native_ownership/verify_native remains unchanged. C shift proof joins actual owned start/end PIDs, serviceID, original priceSnapshot, service.payment key and receipt entries; no fixed PID or ledger number. S1 typed raw joins pre-travel ACTIVE reservation/task/staff/cell to boarded trip; JSON summaries do not replace typed evidence.
 
-Only S4 supplies power_stop. The new verifier requires source-pinned native
-ownership, complete product1338 + sole QA override, three whole4-member formal
-packages per process, separate Writer/Reader, exact Runtime typed restoration
-and full typed replay. Actual NO_POWER, operating dependency, powered/ACTIVE
-kitchen, positive mana and open operator are mandatory. Raw graph edges and
-revision prove the isolated consumer and exact reconnect; source-derived
-evaluation/hold determines recovery. Duration−1, zero stopped charges, original
-service/reservation identity, one SALE and unchanged replay are joined from raw.
-Every intervening held minute is retained and checked. No normalization or
-dropped Runtime fields is allowed. S4 is pending Root execution, not accepted.
+Only S4 supplies isolated power_stop. It preserves native ownership, full product1338 plus sole QA override, Writer/Reader packages, exact Runtime typed restoration and replay, actual NO_POWER, operating dependency, powered/ACTIVE kitchen, positive global mana and open operator. Raw graph/revision, source-derived hold, intervening held minutes, zero stopped charge, original identity and one recovery sale are joined without canonicalization or dropped fields. S4 causes NO_POWER by directly calling disconnect_nodes; it is not global-depletion proof. Global depletion appears only in B1 combined diagnostic; B1 has RELATED_FACILITY_INACTIVE and supplies neither isolated power_stop nor priority approval.
 
-checker_join_fixtures retains every previous case and adds rejection controls
-for B1 masquerading as power, dependency false, kitchen unpowered, closure,
-pre-travel mismatch, absent outage, wrong PID and transaction join. Consistently
-renamed dynamic PID/transaction/service IDs are positive controls. These fixtures
-have NOT RUN. They require actual S4 raw for the S4 positive control.
+The low authority finding remains explicit: destruction_stop is bound to BASELINE:183, a mana-depletion line, not destruction authority. An explicit D05 destruction rule is required; pin/registry correction only after approval through normal repair. Observation and mechanical verification do not resolve this gap. A01 midnight ownership upkeep, dependency hold and18:00 are approved and are not re-asked. Other mandatory priorities remain pending under D05(a–d).
 
-The fresh R collection is B/audit-support/p04-raw-collect-r22. It re-reads existing
-C/S1/S2a/S2b/S3 without native reruns and newly collected S4; no result scalar is
-authority. It binds the current verifier hash. The old r17/r20 collection and
-21615-check proof remain immutable. New checker bytes differ; no1339 identity
-claim. Missing raw, changed pins, mandatory undefined rules or unsupported
-joins must fail. Final index/applicability, registered validation, support53cb
-registered rebind, independent review, normal integration and individual
-nativeWindows obligations remain Root work. No final acceptance is asserted.
+Full178 used checker f5 (`f5b44827958f2ae352fe5c4bc3a1ffd4211ec7a41fc4c0759c8b954891662324`),21615 checks; exact receipt preserved at B/audit-support/p18-regression-support-final-r01/native-full178/runner-ended.json (runner-input.json selected_source_map preserves all1339 selected inputs; source-start.json records initial product sources). **No full1339 run against a61 exists.** Suites/parse not executing Python support checker-independent product applicability only. Static full178 selected-map comparison found one test-source difference (tests/business/test_required_kitchen.gd: full3a9c92f8…, current5dcc86d6…); no game-source difference. Runner must preserve that test applicability binding; no blanket1338 identity is claimed. Do not relabel the old full proof as a61 validation.
+
+Remaining Runner work: owner D05 decisions after review, any subsequent normal repair, support53cb normal registered rebind, final full run and final applicability binding, formal independent review, integration P04 first then support on main9b1a18c1, and individually applicable nativeWindows obligations. Missing original authority or unknown mandatory rules remain gaps regardless of mechanical PASS. No probe or test is requested or run by this docs-only repair.