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

2026-10-16 06:12:33 +09:00
parent accd07c91d
commit b543c26c95
19 changed files with 3076 additions and 24 deletions
@@ -0,0 +1,78 @@
+# Repair19 — incomplete; execution constraint clarification pending
+
+This is not a ready submission and not formal acceptance. Original credit stays
+13/88. All 15 conditions plus EV retain their existing scope; nativeWindows
+remains pending for each. No product, acceptance, domain or outcome was changed.
+
+## Blocking instruction conflict
+
+The recorded repair19 direction requires local fixture reruns, isolated temp-Git
+negative and positive controls, and removing the Stage-A refusal only after
+those tests pass. The final worker instructions prohibit Git writes and say
+tests are formally executed by Runner. This dispatch has requested clarification
+on whether that prohibition exempts the specifically requested file-only and
+isolated temp-Git fixtures. There is no answer at the time of this report.
+No exemption has been assumed. This is an execution-constraint blocker, not a
+claim that pending formal acceptance itself blocks implementation.
+
+## Changes actually made in this dispatch
+
+- `p04_native_series.py`: retain both JSON and Variant Writer/Reader phase-byte
+  comparisons, but increment the S3 pair metric only for `.var`. The requested
+  interpretation is 352 checked file pairs representing 176 observations. A
+  new execution output confirming that count has not been generated.
+- `p04_native_series.py`: add the B1 `power_stop` join for the five observations
+  at 959–963, positive finite original reserve, actual public mana and power
+  flags, direct closure, same service identity/progress/reservations, queued B
+  release/stock/patience, recovery payment and unchanged next ledger. Bind the
+  saved 961 recovery command and the APPLY_COMMANDS phase. Preserve the actual
+  `RELATED_FACILITY_INACTIVE` reason. This code is untested; its addition to the
+  verifier's returned conditions is conditional on every assertion succeeding
+  when Runner executes it. No successful power_stop result is claimed here.
+- `REPAIR19_CORRIGENDUM.md`: correct the StringName/order-only explanation,
+  distinguish raw getter from public persistence, list all six supplied typed
+  Array header changes, and record the actual source call-chain full-body pins.
+
+## Static observations and preservation
+
+- In-memory Python `compile` of the edited series module succeeded. No fixture,
+  native, Godot, full-regression or Runner run occurred.
+- The exact relocated operations source was read. All five complete function
+  bodies, lengths and hashes equal
+  `B/audit-support/p04-repair19-close-r01/ROOT_ACTUAL_PERSISTENCE_CALL_CHAIN.json`.
+  The hash table and exact call-chain explanation are in the corrigendum.
+- The checker region from `NATIVE_RUNS` through `verify_native`, inclusive of
+  the C constants and helpers, equals its HEAD bytes. Region SHA256:
+  `5d778b3cfab7c139ca03812489508ce9aae90c1d17f8c2249c340f30d1496b3b`.
+- No R17/R18 output or status file was edited. The existing uncommitted R18
+  checker changes remain. No Git write, agent, integration or Runner operation
+  occurred. No native evidence was created or modified.
+- No collector was run. Both the existing r17 collection and the required fresh
+  r19 destination remain untouched by this dispatch. Since the series verifier
+  bytes changed, the old r17 collection cannot validate these new verifier bytes;
+  it must never be overwritten or represented as a repair19 collection.
+
+## Remaining implementation and validation
+
+Repair19 is incomplete. R2's C-backed paid shift join, R3's exact encoder port
+and fixtures, Stage A's actual Git-role verifier, new index generator, fixture
+protocol repairs and all requested fixture executions remain to be completed.
+The old Stage-A unconditional refusal remains in place. The old
+`verify_product_target` has not been edited or replaced in this dispatch.
+The 9b1a18c anchor resolves to
+`9b1a18c1eb25ca1300dcd59da78423c0dda2f498`; the old checker constant has not yet
+been changed as part of a complete Stage-A repair.
+
+No new output JSON is reported, and no old fixture success is reused as success
+for the edited module. B4a/B4b semantics, frozen save_restore measurements and
+its current open result remain unchanged. The 25 C negatives and 56 series
+negatives have not been rerun.
+
+There are no valid repair19 index-generation or submitted/merged-candidate Root
+commands yet: the required generator and role verifier are not implemented.
+Providing plausible commands for nonexistent functionality would be misleading.
+The completed follow-up must supply those exact commands after implementing and
+validating the protocol, retain all existing outputs, and collect exclusively
+into the fresh `B/audit-support/p04-raw-collect-r19` destination.
+
+Here `B=/Users/korizatou114/Projects/TheTree-managed-worktrees/p04-01/.runtime/P04-01/build`.