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

2026-10-16 06:46:41 +09:00
parent b543c26c95
commit 16207d353a
3 changed files with 236 additions and 2 deletions
@@ -0,0 +1,95 @@
+# Repair21 — source submission; tests NOTRUN
+
+P04-01 source-only performance repair. Changes are restricted to the checker,
+the new `bulk_reader_equivalence.py` fixture, and this status file. No Git
+command, test, fixture, collector, Runner, native/Godot run, agent, commit,
+branch or integration operation was executed by the worker.
+
+`read_blobs` validates full lowercase 40-hex OIDs before starting a process,
+deduplicates/sorts them, and uses one `git cat-file --batch` process per nonempty
+request. Empty requests start no process. `check_output` inherits stderr and
+raises for nonzero exit status just like `git_bytes`. The separately injectable
+byte parser verifies ordered OIDs, blob type, decimal size, exact framing and
+complete output consumption. There is deliberately no blob cache, so no object
+can be reused across `_GIT_ENV` namespaces. The two bulk call sites preserve
+selected-path sorted manifests and every actual-file byte/mode comparison.
+
+No existing require message or assertion was removed. The `NATIVE_RUNS` through
+`verify_native` region, commit-type checks, ancestry, merge-tree isolation,
+status/untracked/symlink/module checks, schema/encoder, six existing suites and
+role case IDs were not edited. Checker self-blob reads remain unchanged.
+
+The fixture source covers binary NUL/CR/LF/trailing LF, empty and large blobs,
+unicode `ls-tree -z` path resolution, duplicates, empty input, malformed/short
+OIDs, missing objects, tree/commit objects, invalid/truncated/oversized/garbage
+responses, process failure, one-process sorted input, and private object
+visibility inside versus outside and across isolated namespaces. It has not run.
+
+Static validation: `ast.parse` and in-memory `compile(..., 'exec')` completed for
+the checker and new fixture. Neither module was imported or executed. This is
+syntax validation only. Tests: **NOTRUN**. Runtime equivalence and completion
+within the registered 180 seconds remain for Root to measure.
+
+The existing schema2 index at B/p04-evidence/index.json was read as data, along
+with the existing builder and role fixture. Its registered/execution/tested
+roles remain deb1bcb/9767b0a/5f6bc11 and original_credit remains 13/88.
+The existing index and r20 collection are untouched. No new generation is
+needed if Root confirms the recomputed payload is identical. If generation is
+needed, use a new explicit destination, never overwrite existing evidence.
+Original P04-01 remains incomplete; criteria and nativeWindows pending status
+are unchanged. No original credit or acceptance is claimed.
+
+## Root execution order — all NOTRUN
+
+Use the clean new auto-submitted checkout, whose SHA is assigned after this
+source submission. Do not use the registered base SHA as the new submission.
+
+```sh
+export B=/Users/korizatou114/Projects/TheTree-managed-worktrees/p04-01/.runtime/P04-01/build
+export E=docs/plans/original-completion-2026-10-02/execution/p04-01
+export BUILD_OUTPUT_DIR="$B"
+export PYTHONDONTWRITEBYTECODE=1
+python3 "$E/bulk_reader_equivalence.py"
+python3 "$E/checker_negative_fixtures.py"
+python3 "$E/checker_applicability_fixtures.py" --native-bundle "$B/audit-support/native-first-current"
+python3 "$E/checker_native_fixtures.py" "$B/audit-support/native-first-current"
+python3 "$E/checker_series_fixtures.py" --build "$B"
+python3 "$E/checker_encoder_fixtures.py"
+python3 "$E/checker_join_fixtures.py" --build "$B"
+python3 "$E/checker_role_fixtures.py" --build "$B" --evidence "$B/p04-evidence"
+```
+
+Next run the registered validation on the **new auto-submitted SHA**, retaining
+its existing 180-second timeout and actual timed receipt. The supplied formal
+API call is exactly:
+
+```python
+runner.validate("P04-01")
+```
+
+The external Runner launcher/configuration is not present in the supplied task
+context; use Root's already registered invocation, without substituting an
+invented CLI, changing timeout, or treating direct checker timing as registered
+validation. Record actual SHA, elapsed time and exit status from that invocation.
+
+Then run direct real-candidate controls from actual clean submitted, merged and
+final checkouts, preserving the formal review/integration state machine:
+
+```sh
+python3 tools/check_p04_order_evidence.py --verify-only
+python3 "$P04_MERGED_CHECKOUT/tools/check_p04_order_evidence.py" --verify-only
+python3 "$P04_FINAL_CHECKOUT/tools/check_p04_order_evidence.py" --verify-only
+```
+
+After required formal validation/review and exact final-source binding, run the
+full178 product regression once, using a fresh output destination:
+
+```sh
+python3 "$P04_FINAL_CHECKOUT/tools/run_all_tests.py" \
+  --project-root "$P04_FINAL_CHECKOUT" --output "$B/p04-final-product-full-r21"
+```
+
+Do not regenerate raw collections, overwrite index/r20 evidence, alter existing
+case semantics, or run an additional native/full suite to compensate for a
+timeout. Any unrelated improvement is deferred. Pending Root execution is not
+a worker specification gap and does not change this submission's scope.