P04-01: 同時発生の更新規約
This commit is contained in:
Agent Control Runner
@@ -1,4 +1,136 @@
|
||||
# REPAIR41 history and REPAIR42/43 status
|
||||
# REPAIR41 history and REPAIR45 status
|
||||
|
||||
## REPAIR45 — implementation ready for submission
|
||||
|
||||
The supplied byte-verified M engine-free context resolved the REPAIR44 UID dependency.
|
||||
UID controls: all 14 PASS, exit 0. Both supplied helper SHA-256 pins match exactly.
|
||||
AST and explicit fresh BUILD-cfile py_compile passed for all eight touched Python
|
||||
files, with python3 -B and PYTHONDONTWRITEBYTECODE=1. No source was changed in
|
||||
REPAIR45; retained passing controls were not rerun. The no-pyc static check
|
||||
passed again (exit 0); generated compile files exist only under allocated BUILD.
|
||||
The prior UID failure remains recorded as failed, not replaced with a PASS.
|
||||
|
||||
Sequential check-only S1, S2a, S2b, S3, S4 and S5 each returned exit 2:
|
||||
`ValueError: checkout is not clean`
|
||||
The initial missing-tested-tree argument refusals are also retained. The later
|
||||
attempt used the actual HEAD tree solely as a guard input, not a claim of final
|
||||
Q, clean source or C. No engine started. Root executes clean exact-Q check-only
|
||||
after automatic submission. Full argv/stdout/stderr and compile paths are in
|
||||
REPAIR41_STATIC_CHECKS.json. No Git writes, Runner or native run were performed.
|
||||
|
||||
Implementation is ready; the whole original unit remains incomplete and P04
|
||||
credit remains 0. Deferred Root conditions, in order: freeze final Q; affected
|
||||
pure controls; clean exact-Q check-only; capacity check; one heavy lease with
|
||||
fresh native S1–S4 and all ten S5 cases; independent Reader and adapters on actual
|
||||
raw (including fresh Reader order positives); fresh collect; full 184 suite once;
|
||||
index; --verify-only; registered validation before review; independent whole-unit
|
||||
Opus review; normal prepare / exact C / integration / final / Root DB join /
|
||||
ledger / main push. Native Reader and acceptance remain pending.
|
||||
patience_release stays pending unless fresh S3 raw shows it. Product freeze,
|
||||
M, allowed paths, REQUIRED membership/thresholds, all seven domains, G1/G2,
|
||||
R40–R44 and the existing one-trailing-LF spec protocol remain unchanged.
|
||||
|
||||
|
||||
## REPAIR44
|
||||
|
||||
**Worker stopped: unreadable required check dependency.** The UID pure control
|
||||
cannot read `/Users/korizatou114/Projects/TheTree-managed-worktrees/p04-01/P04-01-root-q-r43-eb94e1d7/tools/run_all_tests.py`:
|
||||
`PermissionError: [Errno 1] Operation not permitted`. REPAIR44 explicitly requires
|
||||
stopping for an actually unreadable file. No permission bypass or alternate
|
||||
positive is claimed. REPAIR44_PURE_RESULTS.json retains the failed invocation.
|
||||
Eleven other pure programs completed successfully (including the new 17 paid
|
||||
mutation negatives and roster/name-sync/regex/no-pyc controls). The already
|
||||
launched sequential batch finished power-adapter and repair44 controls after
|
||||
the UID failure; these results are recorded within their limited scope.
|
||||
AST/build-cfile compilation of all touched Python files and check-only S1–S5
|
||||
were not reached. The implementation below is work in progress, not a completed
|
||||
REPAIR44 submission. Resume requires a readable verified check dependency.
|
||||
|
||||
Same original unit, W and submitted S=eb94e1d7dbae3b0be84171b4ef0024b4f6b0ae97;
|
||||
M=c0ea009b28a7649aca6a433a1a24dc0be5e7ab81. No reset or new counted work.
|
||||
Original whole unit remains incomplete, formal 16/88, P04 credit 0.
|
||||
R43 import/parse/Writer passed (2749/0), then run_s5_native.py:525 compared
|
||||
sorted receipt branches to insertion-order CASES. G/H preceded E/F; all nine
|
||||
cases were present but Reader never started. R43 native remains FAILED,
|
||||
alongside r35/r36/R40 native. Q37 remains its own-version local PASS only.
|
||||
Seven Writer-only typed derivers/G1/G2 and twelve pure/six check-only passes
|
||||
are not independent Reader, replay or acceptance.
|
||||
|
||||
The canonical wrapper roster is now sorted(CASE_TABLE). LABELS, SLOTS and
|
||||
receipt comparisons derive from it, with exact lengths, uniqueness and set
|
||||
membership. Reader independently enumerates CASE_TABLE. The new pure controls
|
||||
reproduce the old failure, accept insertion/reverse order and reject missing,
|
||||
duplicate or unknown cases and missing/extra/duplicate slots. The ten cases are
|
||||
`S5A_PURE`, `S5B_DEPENDENCY`, `S5C_DESTRUCTION_COMMAND`, `S5D_DESTRUCTION_RAID`,
|
||||
`S5D_IN_FLIGHT`, `S5D_PAID_BEFORE_INCIDENT`, `S5E_MIDNIGHT`, `S5F_EXIT`,
|
||||
`S5G_SHIFT_1080`, `S5H_PAUSED_MIDNIGHT`.
|
||||
|
||||
New fixture: primary queues at N-duration-1, starts at N-duration and completes
|
||||
at N. Secondary queues at N-2 and starts at N-1, holding its own reservation;
|
||||
two meals are stocked through _stock. Cafeteria definition capacity=12 (line22),
|
||||
staff_min=2 (line18), base_service_minutes=45 (line24), base_price=25 (line26),
|
||||
inventory_inputs=one meal (line27), exact file sha256
|
||||
86d540fe2d78b9dcdbe5a0af6e4a001f4cec54934636ed01deb25a943c79128a.
|
||||
Staff setup derives staff_min; prices/duration subsequently bind to the primary
|
||||
service snapshot. Capacity permits the concurrent secondary; no product value
|
||||
is changed. Seed 420558 is a distinct deterministic fixture seed following the
|
||||
existing 42055x private-QA family, not a product RNG policy change.
|
||||
|
||||
M source proof (full bodies, file hashes and line ranges in
|
||||
REPAIR44_SOURCE_FACTS.json): simulation_kernel.advance_one_minute line122,
|
||||
body sha b9587ef722d8c8640248025462819374ae5eca1c3d8bbe600b6bc9c328567777,
|
||||
runs FACILITY_COMPLETION, VITALS_AND_ENVIRONMENT, INCIDENTS_AND_EVENTS,
|
||||
FACILITY_QUEUES in that order. _run_phase line236, body sha
|
||||
52461eeb288892a4bb4b6a99570185af08a30758ef88b0046a911baaa6f318e1,
|
||||
emits phase-start observations before handlers; therefore completion is
|
||||
observed as ACTIVE at FACILITY_COMPLETION start and COMPLETED with one receipt
|
||||
at VITALS_AND_ENVIRONMENT start. Receipt phase is FACILITY_COMPLETION.
|
||||
Runtime registers the handlers at lines400–428. _advance_relationship_events
|
||||
line8637, body sha 20ca7abfdcbbc914f91545c3eded46e3e87035ff4153541ffcbf92471b02b03f,
|
||||
starts the queued automatic event in INCIDENTS_AND_EVENTS. Public registration
|
||||
and enqueue functions are at lines6878/6887 (full hashes in the source facts).
|
||||
_validate_event_action line9991, body sha
|
||||
83e0cce3b59244440b11acdee6f87dd521859701769b1689ff2775db5c92c5f5,
|
||||
allows SET_FACILITY_STATE for this non-Defense-owned facility. _apply_event_action
|
||||
line10040, body sha d79e7aca02eed06f500ffc632c6160cd80d76c3d7c5c90dc097f71b60380d365,
|
||||
calls set_operational_status with durability=0 and suspension_reason=DESTROYED.
|
||||
The fixture never registers the busy facility as a Defense asset and expects no
|
||||
guard. FacilityService.start_next_service line449 (body sha
|
||||
2eb1cf1226fb1496b6b96c39184ad6a767b4fde747923df599097372435ffa4c) checks the
|
||||
actual instance capacity and starts secondary work with ordinary active staff.
|
||||
ServiceInstance.mark_failed line128 stores completed_at for failure timing,
|
||||
body sha 178c6879e64385f0e3ff99fa98ae6ceb4dc67f6c2c981b0effb229f5d4d647fa.
|
||||
|
||||
The independent adapter retains payment/release/sales/phase helpers. It proves
|
||||
the pre-completion state, single typed receipt/Runtime-ledger/idempotency joins,
|
||||
surviving identical boundary/held sale, one primary wallet debit, financial day
|
||||
from ledger absolute_minute, positive pre-event durability and BROKEN/DESTROYED
|
||||
afterward. Secondary stays active/reserved through N and fails/releases once at
|
||||
N+1 with unchanged wallet, no remaining request/reservation or generated service.
|
||||
The checker adds this raw-recomputed sub-gate inside D05-P04-DESTRUCTION.
|
||||
All previous gates and REQUIRED names/thresholds stay intact. Pure mutations
|
||||
cover every requested failure, including AFTER-copy; they are serializer units,
|
||||
not substitutes for fresh native Writer/Reader raw.
|
||||
|
||||
The six explicitly named __pycache__/*.repair43.pyc were read, byte sizes,
|
||||
headers and SHA-256 inspected, then deleted; no source/evidence was deleted.
|
||||
Execution-scope .gitignore now excludes __pycache__/ and *.pyc. Python checks
|
||||
use -B and explicit py_compile cfile under allocated build. The static control
|
||||
rejects any remaining *.pyc in the allowed execution tree.
|
||||
|
||||
All existing R40–R43 cases, G1/G2 shadow oracle and negatives, R41 diagnostic,
|
||||
historical/fresh S4 pin separation, 43+ controls and the Step 0 table below are
|
||||
preserved. Product source/values/guards, permissions, billing, all seven domains
|
||||
and 15+EV thresholds are unchanged. Approval raw SHA-256 exactly matches
|
||||
cd365ded1b777a0327d090709f0a4161f5005562819183455d9f2e106fba3e96.
|
||||
The spec raw is 7000 bytes, sha
|
||||
d28aadb044633f7d804de5a92c8d4c4a7438dfbf44c3243dca978951f4def25f;
|
||||
stripping exactly its one final LF gives the registered
|
||||
9ec722e7dfb0bee178d291624a026420c08412574e238bba1fde012c7a6f7881.
|
||||
This is the existing spec-only EOF protocol; all other hashes compare raw bytes.
|
||||
REPAIR41_STATIC_CHECKS.json records actual worker checks only. Native Reader,
|
||||
formal acceptance and patience_release remain pending (the last needs fresh S3).
|
||||
Root freezes final Q and follows the twelve steps in s5/S5_ROOT_RUN.md.
|
||||
|
||||
## REPAIR42/43 implementation submission
|
||||
|
||||
|
||||
Reference in New Issue
Block a user