5 Commits

This Branch

This Branch

All Branches

Author	SHA1	Message	Date
ops-01	9abd7e386f	chore: serialize CI run — same tree as 9af456c, fresh pipeline head ... Per ops-ci-01 (PR #1324 comments 23413/23422) and fred's one-at-a-time authorization: one serialized run of #1324's tree on the pinned image (ci-base:lock-9cb7ffcd8828, carried since the cb9a0d1 absorb). This commit changes no files — the tree is identical to 9af456c; it exists only to mint a fresh pipeline head instead of restarting 2545.	2026-08-19 19:45:20 -05:00
ops-01	9af456c240	merge: absorb next (pin cb9a0d1 + #1325 + #1129) for the controlled pinned-image rerun ... Per ops-ci-01's procedure (comments 23386/23394, brain D27): pipeline config travels with the commit under test, so the controlled rerun requires the pinned anchor in the PR head itself. This merge absorbs everything next took since the original merge parent (1bdeed62): the ci-base pin (cb9a0d1, lock-9cb7ffcd8828), the legacy-credential removal (#1325), and the ci-queue-wait statuses:null fix (#1129 — the branch from the divergence analysis, now landed). One conflict, same file as round 1: test:framework-shell union — our 54-entry chain plus next's new test-ci-queue-wait-no-status.sh entry at its position (55 entries, every target existence-verified). Enumeration guard green: population 61, enumerated 46, excluded (signed) 16.	2026-08-19 18:43:19 -05:00
ops-01	2508f0aa99	fix(merge): round-2 CI failures — pipefail sites, verify:release mirror, format ... Pipeline 2534 (018d96a), two test-step failures plus the format failure root-caused by rev-code-01 (id 202): 1. pipefail-early-exit.test.mjs: main's window wrote the test but never wired scripts/*.test.mjs into its own CI, so its tools/install.sh pipes were never executed against it; next's test wiring runs them and flags two load-bearing pipes. Both rewritten pipefail-safe via process substitution (newest_matching_file ls|head, check_fleet_transport sed|head|tr|awk). Test now 7/7 locally. 2. verify-release.test.mjs: merge kept main's 9-command ci.yml sanitization but next's 4-command canonical stage. Canonical updated to mirror ci.yml exactly (9=9, order verified). upgrade-guard checked equal (4=4). 3. format: docs/reports/quality/1099-pipefail-sweep.md (from main f158be8) prettier-formatted under pinned 3.8.1. Enumeration guard re-verified: population 60, enumerated 45, excluded 16.	2026-08-19 17:27:30 -05:00
ops-01	018d96a412	fix(merge): drop fleet test-start-agent-session.sh from framework-shell chain — review B1 ... Review stack#1324 id 201 (rev-code-01): the union resolution chained main's #1073 fleet test while keeping next's signed exclusion of it (#1271 burn-down: the test asserts missing-binary behavior but CI provides pi on PATH — fails by design). check-test-enumeration CONTRADICTORY EXCLUSION, CI pipeline 2532 terminal failure. Fix per verified review recommendation: remove the chain entry (55 -> 54 parts), keeping next's exclusion and #1271 state. Guard now passes: population 60, enumerated 45, excluded (signed) 16.	2026-08-19 16:44:31 -05:00
ops-01	b01950e92f	merge: absorb main into next — 23-commit divergence (08-05..13 base=main window) ... 17 content commits + 3 merge bubbles were genuinely missing from next (~8,000 lines: goal controller #1152, framework enforcement #1174/#1195, pr-edit wrapper #1173/#1200, pipefail series #1100/#1105/#1106/#1107, git-tools fixes #1073/#1085/#1086/#1089, #991, #1007, enrollment tolerance #1094). 3 commits were already in next by content (#1060 identical, #1066/#1062 evolved twins — conflicts resolved to next's side). Per-commit classification and evidence: mosaic-brain fleet/lanes/stack-remediation/main-next-divergence.md. Conflict resolutions (6 files) itemized in the PR body.	2026-08-19 16:27:17 -05:00