|
| 1 | +# Independent regression acceptance |
| 2 | + |
| 3 | +The integrated source at `0818ea1812a028e1c14cd0b0511b44863407bc52` |
| 4 | +(tree `98c6c2f05364c8274d404ae5f6ecc56bb73450d2`) is accepted for the next |
| 5 | +complete candidate CI run. Production publication remains pending. |
| 6 | + |
| 7 | +Four fresh-context workers ran in parallel with disjoint temporary state and |
| 8 | +shared test locking. All 63 selected original test files executed: **2,423 pass, |
| 9 | +0 fail, 0 skip**. Separate current-source GUI verification passed 48 tests; |
| 10 | +a separate runner-isolation preflight passed 25. Those counts are not added to |
| 11 | +2,423. The candidate GUI build succeeded and its 94 generated artifact hashes |
| 12 | +remained unchanged through the manual browser verification. |
| 13 | + |
| 14 | +| Area | Original tests | Additional acceptance | |
| 15 | +| --- | ---: | --- | |
| 16 | +| Native accounts, catalog and fallback | 990 | Seventeen HTTP scenarios and the actual account CLI, including revoked versus transient credentials, replacement races, hard locks, precise model refusal and committed output. | |
| 17 | +| Request bytes, compaction and tool history | 370 | UTF-8 threshold captures, destination and cancellation controls, typed Messages errors, recovery limits, and ordered immutable Ollama tool history. | |
| 18 | +| Pairing, identity and existing-format accounting | 363 | Actual CLI minting, HTTP redemption, browser interaction, identity race negatives, capacity refusal, and durable legacy-journal restart/corruption. | |
| 19 | +| Provider, platform, CLI and historical fixtures | 700 | Discovery and saved-effort persistence across processes, operator commands, synthetic launcher controls, and eight separately executed original historical files. | |
| 20 | + |
| 21 | +A fresh independent acceptance review found no blocker to final candidate CI. |
| 22 | +Two independent visual reviews found only Low wrapping and validation-layout |
| 23 | +polish issues, with no observed clipped text or blocked controls. These are |
| 24 | +retained follow-ups, not claimed fixes or a complete accessibility audit. |
| 25 | + |
| 26 | +## Evidence limits and failed attempts |
| 27 | + |
| 28 | +Failed harness executions remain failed in the private evidence ledger. They |
| 29 | +were not overwritten or included as passing executions. Corrected probes use |
| 30 | +source-backed fixture contracts. Two request-probe expectations received a |
| 31 | +separate independent adjudication: cancellation prevented another physical send |
| 32 | +although the legacy reset-only counter remained zero; a preflighted compaction |
| 33 | +stream legitimately returned HTTP 400 rather than the HTTP 200 required for an |
| 34 | +already-open Messages stream. Neither result proves complete legacy accounting |
| 35 | +or preservation of client-visible partial compaction text. |
| 36 | + |
| 37 | +Manual expiry evidence proves rejection of an expired signed mint capability, |
| 38 | +not expiry of an issued pairing code. Current CLI/HTTP/browser pairing passed; |
| 39 | +full native SSH enrollment at this candidate was unavailable. Earlier native |
| 40 | +join/replacement and teardown evidence remains historical. The named pairing |
| 41 | +owners are byte-identical, which does not make that a fresh integrated native run. |
| 42 | + |
| 43 | +Every one of the 20 uniquely named assertions from the earlier broad failed run |
| 44 | +maps to a current pass in its original file. The former GUI setup error has |
| 45 | +current original-file coverage as well. This does not certify the old broad run |
| 46 | +or identify its historical state writer; its original 21-failure/one-error total |
| 47 | +is preserved. Complete cross-platform CI is still required. |
| 48 | + |
| 49 | +The original Antigravity Windows/multi-account report remains unproven, the real |
| 50 | +launcher scenario remains unavailable, and packaged Windows login behavior is |
| 51 | +not established by native helper/parser tests. The canonical spend migration |
| 52 | +remains excluded; the landed capacity repair preserves the existing format. |
| 53 | +Previously recorded accounting, diagnostic and dependency limitations remain |
| 54 | +explicit. No current required product failure was waived by those limitations. |
| 55 | + |
| 56 | +All owned processes, listeners and disposable homes were closed or removed; |
| 57 | +source and build identity were rechecked. The artifact validator only proves |
| 58 | +schema/source consistency; semantic acceptance comes from the reviewed scenario |
| 59 | +matrix and the explicit dispositions above. |
| 60 | + |
| 61 | +Next: run the complete `lane=all` CI at the accepted source SHA, inspect every |
| 62 | +requested job, then follow the separate version pre-move, promotion and publication |
| 63 | +procedure. This documentation record adds no product changes to that source. |
0 commit comments