[Brian Krabach (bkrabach)]

0.96.1: published operations delivery — prepared and merged

Prepared head da23cc10b69b1f24900edf0ba7c3631a1d44fbb3, tree a77f7be698754f6ea4d81052884ef491587f0504, sole parent accepted 69220ad6aac6b98fe133583ea68d06932dc22ab6. Passive GH/Git read confirms this same PR was promoted and merged at 22:24:33Z as 453e6b9444fe6f441fa7b616cbb62ed10142759f, exactly the prepared tree with zero Git diff. No new worker merge, version cut, tag, publisher dispatch/watch or live adoption. Publication and official WITH-dependencies smoke remain RM-owned and are not claimed successful here.

Only four release metadata files differ from pinned accepted main: 4 insertions / 3 deletions; all 3919 other paths/modes/blobs are identical. The 910-byte RM-authored entry SHA256 062f372f1071348fcdd19ad0a115fc193578387a11700aae5acc10292feef061 has two changes and empty notices. All 483 prior raw entries, values and notice IDs are preserved (484 total). PATCH covers accepted artifact selection/documentation/component-publication maintenance without changing runtime behavior, defaults, authority, graph or Stop behavior.

Accepted #2100 selects original operations-v0.1.0 at b6c58bb24cb92c495ded1c42683dc8496c92a6ea, receipt SHA 1e03ad557a4d463198857deb7f98dce9df7029b9f653b4f910239c18b8cf61a4, wheel SHA 05675519079bbfb75be9ce0bc6fcba8c4a4ba6fd06dc8105ca706aec5ac43a1a. All three top-level operations runtime files are byte-identical to 0.96.0. The new provenance/license records ship under Unified's sole distribution ownership. No component republish, coinstall, moving producer selection or download. Accepted #2098 workspace-metadata publication tooling and #2099 explicit-profile MCP error-fidelity documentation are retained.

Current qualification

• Owned Python3.13.12/Node22.23.5/npm10.9.9 toolchain and matching npm cache reused. Exact existing 106-entry preparation graph 9c8a3cf9... is verified pre/post; root/worker requirements and committed lock are unchanged except the app version. Only root editable mapping changed to owned 9a3a90e3...; no new environment or fresh moving-main resolution.
• One canonical release.py prepare --version 0.96.1 --notes-file ... --build attempt retained metadata but failed before a frontend build because the empty prepared-client directory contained only a prematurely linked npm cache. Maintained client preparation corrected setup order, followed by one successful actual build at 22:07:53–22:08:04Z, reproducing all 663 selected client files, 316 static files/build 2cceae6c5a546047 and shared inputs. No hand-generated output, extra feature suite or second actual build.
• 32 notes tests passed in 10.60s; 2 asset checks passed, zero skips. Locked dev/artifacts dry-run, client verification and all four offline component selectors/Hatch wheel verifications passed. Dry-run changes were not applied.
• Current-head candidate 70a78e3c56bb06567046b5a60d9fc4739c55267e4d72bacef0d3ba9899718f74, normal stage-source, sdist→wheel, maintained release/candidate/package checks passed. Wheel SHA e9ee34c780fa4c34acacf44096635ae2df4a72809690d648427b75b1e1edb995; sdist SHA 6467eb6b36dacf98d764831157a5bad8a5c75ed182a41dda990a858c71d48e26.
• Complete 980 payload files (979 owning Git/Hatch selections + current stamp), 985 RECORD rows (984 hash/size + self), CRC, 3262 sdist files and all 316 static files match. Eight actually loaded module hashes, including all three operations modules, and eight installed component record/license hashes join Git→sdist→wheel→installed origins. All operations runtime bytes are unchanged; Unified is the sole owner of six inspected package imports with no standalone component coinstall.
• Outside-checkout noneditable isolated env -u PYTHONPATH python -I maintained PROBE passed 22:13:37–22:13:38Z, including nested -I -S worker imports. Actual host has 63 dependencies, graph 4ec3deb4..., unchanged and an exact subset of selected preparation106. Stamp binds the prepared da23cc10 revision, not future merge/publication identity.
• Required Fast 43646659667 passed in 49 seconds, explicitly release-smoke. Bounded current-head snapshot: 18 SUCCESS / 3 SKIP / no pending. Default-installed, integration and windows-bootstrap-offline skips are not passes. Source optional contracts43643708625 were later observed completed SUCCESS at source d915aafd..., not retroactively green at intake. No dispatch/rerun or bypass.

Two other ordinary setup/CLI failures remain retained: preflight expected a nonauthored worker uv.lock (before install/build), and stage-source was initially given candidate/evidence flags belonging to release_qualification.py (argparse failure before stamp/package). Corrected paths/schemas proceeded without replaying uncertain effects, redoing successful builds, changing dependencies or modifying production source. Original raw evidence remains explicit; failures are not relabeled passed.

Main's independent accepted 113-case/source/artifact proof is reused at its recorded inputs, not repeated or expanded. The short package PROBE/import/hash observations do not claim journal mutation/cursor rollback/Stop execution, native Windows, provider/model, guest, browser, live account, adoption or full moving ecosystem qualification. No extra critic/Main ACK is required. Final finite handoff/raw/wheel/sdist is retained for RM; original 0.96.0 artifacts and frozen 0.94.2 work remain unchanged.

Five resources remain ACTIVE under explicit RM retention/next-cleanup custody: execution/toolchain5909, current source9a3a, probe, previous223d0960, frozen dirtyc6630942. Ten earlier archives retain every file/ref; no additional cleanup is authorized. HOME/CODEX_HOME are inherited unchanged. Old0942task remains frozen; unknown0960task-create is not replayed. Routine five-minute total target was exceeded due setup repair, host admission/response and orchestration overhead; build/CI durations alone are not total release time.

[Brian Krabach (bkrabach)]

Nonblocking next-repair intake notice from Spark-1 Release Manager/bec94bb7: #2095 currentd551e3f4 remains draft pending its owner’s final Fable/exact-graph negative-control qualification; production unchanged from30cd, earlier native663PASS and current checks progressing. It is explicitly EXCLUDED from this already-merged0.96.1/453e6b and active publisher43647942408. Do not expand/rebuild this release or wait for2095. Existing intake2095#6884114472 tracks a next ordinary available patch after final acceptance; no version reservation, competing publisher, new test campaign or live adoption is started here. This is an overlap record, not a request to acknowledge or block this publication.

[Brian Krabach (bkrabach)]

Post-0.96.1 coordination: accepted repair2095 merged71f55faf (parent453e6b). Release Manager Spark-1/bec94bb7 selects and owns ONE 0.96.2 patch preparation/publication for that repair under the standing user release instruction, coordinated with repair managerb005 and sourcewriterfbc61 (neither publishes). Exact current preflight: no open release PR or active publisher; only2095 unpublished. Existing0961 is complete and immutable. Scope/reservation recorded2095#6884114472. No extra feature/native campaign or live adoption requested; this is ownership disclosure, not an ACK gate.