Skip to content

ci: native diagram qualification self-test rejects legitimate source drift #2365

Closed
#2374
Closed
ci: native diagram qualification self-test rejects legitimate source drift#2365
#2374
Assignees
schlessera
Labels
agent-readyContext and acceptance criteria are complete enough for an agent to take this unattended.area: ciCI workflows, the gates they run, release scripts, packaging.priority: p1Scheduled into the current or next milestone.type: fixSomething is broken and must behave the way it is documented.
Milestone
0.44.0

Description

@schlessera
schlessera
opened on Oct 17, 2026

Out of scope

Do not refresh qualification hashes merely to admit new source, narrow the source inventory, weaken source/importer/installation/native guards, accept an unqualified retained domain, skip the unit test, or change the private conformance clock. Browser outer-job capacity remains independently tracked in #1788.

Context

Ready confirmation 39068372996, attempt 1, for #1943 head cdacd179b47ea83b069589458283713d2cd1a071 checks out merge d776e31f6e5859c63da97902bd35543fd06ad066, parents main 0d780605fe1ea9a281cce947b1f0074f3f3e7acc and that head, tree 7994c310523897958ff9765f27f512597ce73bb9.

Unit (1), job 117501062535, fails the original COMPLETE_NATIVE_QUALIFICATION_WITHOUT_DOCKER_OR_IMAGE_LOOKUP assertion (test, tests/native-diagram-inputs.test.ts:9-19): expected 859 files, received undefined. The candidate legitimately adds two private core test files and changes one existing test; published contract implementations are unchanged. The test copies the current tracked package domains, then unconditionally expects those current bytes to match a frozen qualified fingerprint. The production binder correctly refuses drift rather than granting retention.

A bounded owned local diagnostic on the exact candidate, Bun 1.4.3, reports status: source-mismatch, sourceInputs 861, expected source e8502b6ffb3c575f2e9a1c93dea8dbf5ceda93ece367da9d542cb10b1c9ac32b, actual 8036b05d11429f6c39843d6df9eca1c04fadb4741c2408ad65481bb5ce6305b7. All three source pins match, and expected/actual installation both equal 0c2758c046f2b69d5f33b66521baf3098db5f44256b73ec96961c98d381e6245. A temporary log-only observer in the test was restored byte-for-byte; its expected 859/undefined failure matches the unmodified hosted test. This is a self-test fixture/current-source mismatch, not evidence that native drift should be accepted.

nativeDiagramSourceInventory (scripts/native-diagram-inputs.ts:28-37) deliberately inventories complete package families, including tests; the fixed binding (qualified, scripts/native-diagram-inputs.ts:20) and source pins (sourcePins, scripts/native-diagram-inputs.ts:22-26) require exact qualification. The test must preserve that conservative behavior and a genuine positive control without requiring every unrelated future candidate to have the frozen qualified source. The #2111 draft also changes a pinned CI-proof file, another current-source drift class to account for. Duplicate searches for the test name, native-diagram-inputs and fingerprint findings found no open exact report.

Supports #1942 / #1943 and the independently prepared #2111 / #2197 qualification. The binder/self-test came from delivered #2126 / #2293. This is a scoped CI correctness prerequisite in the broader #736 verification boundary, not a claimed test-cost optimization or a new product contract.

Scope

Make the qualification self-test use truthful, source-bound positive and negative fixtures that remain valid across legitimate current-tree drift. Preserve the complete exact-identity guard and fresh execution for unsupported inputs. Select the smallest fixture correction after checking the existing immutable source artifact and ownership rules.

Acceptance criteria

  • Preserve the hosted failure, actual candidate identity and source-mismatch diagnostic; identify why current-source copying cannot unconditionally be a qualified positive fixture.
  • Keep a genuine pinned/frozen positive qualification control and independent drift controls for added source, source modes/content, pins, importers and installed origins. Expected qualified content must be independently owned and attributable; do not replace the positive test with an undefined-only assertion.
  • Legitimate candidate additions such as the two private core test files, and legitimate changes to a pinned caller/proof file, require fresh native proof without making this generic self-test fail for the intended refusal.
  • Removing a relevant refusal guard makes the named negative control fail; breaking positive fixture ownership/identity makes its positive assertion fail. Restore and pass both.
  • Run the actual affected self-test on the legitimate changed candidate plus appropriate pinned native/proof controls, required preflight and complete selected hosted proof. No qualification hash or retained-result waiver substitutes for actual source/runtime qualification.

Verification

Use own frozen dependencies and the ordinary guarded CLI in an explicit offline namespace. Reproduce with bun run test tests/native-diagram-inputs.test.ts on the immutable candidate above. A temporary observer may print the existing NativeDiagramDiagnostic after the first bind; restore it and preserve the original assertion. Source/current fixture comparisons remain separate from real native operation compatibility and complete CI evidence.

Contract impact

None selected. Internal CI self-test fixture correction; no brain CLI JSON, MCP, frontmatter or public export change. Priority p1 is inherited from blocked P1 #2228 under the blocker-priority rule. No release milestone is committed by filing this scoped prerequisite.

2026-10-18: Additional independent blocking receipt: #2228 / PR #2369 head 42c83eb2a2d6ba77dc5fc6fe74909a7e822420f9, ready run 39074479367, unit (1) job 117518971447, checkout 50c1bb81b6b96d7fc2d6cb92936dfa5b97f3253b, tree 651c4b0acc7eb3081401b3829fbf967bcc1fbda0, parents 498270fbdc4ef2788fdd3babb259b647d77f6c77 and that head. The same COMPLETE_NATIVE_QUALIFICATION_WITHOUT_DOCKER_OR_IMAGE_LOOKUP assertion expected 859 and received undefined (764 pass / 1 fail / 110321 assertions). This remains distinct from the original #1943 receipt. Subsequent sibling browser closures coincide with failed-worker termination and do not establish an independent browser defect. Scope and frozen qualification pins are unchanged.

2026-10-18 correction: PR #2374's first ready confirmation 39076303374, attempt 1, verify job 117524363094 failed full strict tsc --noEmit with TS2769 at test line 88 (optional diagnostic status passed to an expected-string assertion). That exact error is reproduced locally before correction; the original hosted verify failure and cancelled unit (3)/(4)/proof receipts remain incomplete. Correction requires the diagnostic before status comparison, and a whole-file/diff audit requires source diagnostic and expected-pin record/actual pin existence before identity comparisons. No blind non-null narrowing or assertion weakening is used. Production binder, inventory and qualification hashes are unchanged. Corrected head 80968a3b183af958ddebcb756b632f04909ffec1 integrates main 82a64a13a08c44f2daef425d1a9df2c10840ea8e; full strict typecheck passes, offline controls pass 28 tests, committed preflight passes 453 affected plus 10 import-feedback tests. Missing-diagnostic and missing-pin mutations fail their intended existence assertions, restore byte-identically, and restored targeted controls pass. The original five behavioral mutation receipts remain attributed to the original implementation candidate. Complete fresh selected hosted proof and delivery reconciliation remain required under the parent campaign.

Historical confirmation 39086344533 / attempt 1 passed on head bedb7ba0396df63c3d93a609e1143f1227ca464e, base 68e12f27eb249c9fe7262a498a0397c04bbda8f4, synthetic 566105cd9cae2b76f87a47168dec6c78500b6134, tree 9775660cd663116e39d76b0655f31aa7c6970e62. Selected jobs: changeset 117553667291, verify 117553827444, unit (1) 117553827496, unit (2) 117553827400, unit (3) 117553827431, unit (4) 117553827405, proof 117554702356. Actual requested BASE_SHA/HEAD_SHA and all selected checkouts agree; all four unit resource receipts and the final candidate receipt agree. The aggregate confirms remaining skips were planner-intended, with no retained domains. That is historical passing proof only.

2026-10-18 refreshed candidate: head a67c4196699d0c7b73f28f712de0ea13f6d2f5db, verified integrated base/live main 7f22bb6ac2892360f3a5c4d3a1f93d9997af43e8. Before ready, REST PR requested base, independent live main, fetched synthetic merge and immutable Git API agree: synthetic 5819700fb710620090258ab9902e1494462af62e, parents exactly base/head, tree c6cb485a8816a2945dd36bad23ce0f4b51128ea9. The tested committed head has the same tree.

Five intervening main commits deliver independently frozen generated stylesheet fixtures (#2388), cancellation fixture temp placement (#2407), worker XDG import-order correction (#2299), sandbox-note prepared-output cleanup (#2411) and the callout geometry/capture split with document-binding re-audit (#2393). Worker source changes legitimately change current native source identity. GitHub cached the previous PR base, so verified main was integrated without rewriting history. No conflicts. The PR diff remains only the native self-test; production binder, complete inventory, qualification pins/hashes and frozen source owner remain unchanged. Generated stylesheet and native positives keep their independently owned raw Git blobs.

Fresh ordinary-UID route-free offline controls, with loopback only, dropped capabilities and the unchanged preload/deadlines, pass 28 tests / 51,871 Bun assertions in 17.87 seconds. Full strict bun run typecheck passes. Committed bun run check:pr --base origin/main passes all contribution gates, 453 affected tests / 53,907 assertions and 10 import-graph feedback tests / 51,807 assertions. Self-test SHA-256 remains df368d2c560c1c2ebc8b94a333742258e0b272d2112a035795c6bf1dfc46addd. Original failing-first, TS2769 and intended/restored mutation receipts keep their actual historical attribution. No consumer-visible change or changeset.

Fresh ready confirmation 39111042672, attempt 1, is requested and pending at the initial handoff read. Draft/push feedback 39111013813 is separate; contract run 39111013789 passed. No current hosted green or delivery is claimed. Parent owns watching, actual requested BASE_SHA/selected job checkout and inventory/aggregate validation, fresh review/head/live-base/milestone readbacks, matching-head merge and delivered-main/closure reconciliation. Both issue and PR retain milestone 0.44.0. #2228 / #2369 and all other issue branches remain untouched and need their own qualification after this prerequisite lands.

Implementation custody returns to the parent. Claim p1-2365-native-fixture-20261018-r2 is released under serialized cleanup after fresh uncontested ownership reconciliation; preserved branch and receipts remain available. The implementation sub-agent does not watch or merge. PR linkage is registered and verified.

Campaign candidate, 2026-10-18

Claim 044-native-20261018: refreshed head 2da0ef1d309d86bfb0725eaa6a6821b0a0b34bf6, base 685d83e22cc452e97a2c92ef7ae683f34ceb2371, tree b1d10ffddd898b01c04574a48611696004a2450a. The non-rewriting integration preserves prior head a67c4196699d0c7b73f28f712de0ea13f6d2f5db; main advances #2381, #2415 and #2398 are included. Only the native self-test differs from main. Its SHA-256 remains df368d2c560c1c2ebc8b94a333742258e0b272d2112a035795c6bf1dfc46addd; production binder, complete inventory, qualification pins/hashes and independent frozen source remain unchanged. No shipped package or contract change and no changeset.

Historical ready confirmation 39111042672 attempt 1 passed all selected jobs at the prior head and base 7f22bb6ac2892360f3a5c4d3a1f93d9997af43e8, checkout 5819700fb710620090258ab9902e1494462af62e, tree c6cb485a8816a2945dd36bad23ce0f4b51128ea9. This continuation verified metadata/verify/unit checkouts, all four resource receipts, the final candidate receipt and immutable API parents/tree. The aggregate confirms planner-intended skips with no retained domains. That proof is historical, not proof of the refreshed base.

Fresh local receipts:

  • Initial preflight and offline attempts failed before assertions with ENOSPC. Capacity subsequently became available; those setup failures remain recorded.
  • The first frozen copyfile install from the existing shared cache produced installation identity 0f4614b41729d5f1c974a88f0497b77c088c045de6b71a3012ff91d543c2df51, matching the affected identity already documented in ci: isolate diagnostic dependency edits from the shared install cache #1980. Offline controls failed 23 pass / 5 fail, including the frozen positive. These failures remain separate from source drift and passing recovery evidence.
  • Replacing only this owned installation using a fresh private cache and bun install --force --frozen-lockfile --backend=copyfile restores qualified installation 0c2758c046f2b69d5f33b66521baf3098db5f44256b73ec96961c98d381e6245: 843 packages, 59,516 files, 1,833,832,361 bytes. The recovered Vitest chunk hash is a236001d048380e2c67d05423fc9ea3f26b07ee019ba8d6e622082f29d49102e. The shared cache and other installations were not modified. ci: isolate diagnostic dependency edits from the shared install cache #1980 preventive work remains separate.
  • Ordinary-UID route-free offline namespace controls with loopback only, dropped capabilities and unchanged preload/deadlines pass 28 tests / 51,871 assertions before mutation and again after restoration (10.59 seconds restored).
  • Removing the production source-mismatch refusal makes added package source requires native requalification fail at NATIVE_SOURCE_ADDITION_REQUIRES_REQUALIFICATION because binding is unexpectedly returned. Production binder is restored byte-identically, SHA-256 42defd431b016ab527652188a2dd0bad4f249eb49e52e69097b015f5bdabe4f5. Original positive-ownership/importer/pin/origin and missing-diagnostic mutations retain their historical attribution.
  • Full strict bun run typecheck passes with the recovered dependencies. Committed bun run check:pr --base origin/main passes all contribution gates, 456 affected tests / 53,933 assertions and 10 import-graph feedback tests / 51,807 assertions. git diff --check origin/main passes.

PR #2374 stays draft. No fresh ready-candidate confirmation, auto-merge or merge was requested. Parent retains the serialized assignment and owns the first proof/merge window, actual final requested base/head/selected-job checkout reconciliation, review and milestone readbacks, matching-head merge and delivered-main verification. Both issue and PR retain milestone 0.44.0. #2409 remains independently owned and untouched. This candidate is locally ready for that window; complete fresh selected hosted proof remains required.

Historical identity readback (superseded by the current confirmation section): remote head is 2da0ef1d309d86bfb0725eaa6a6821b0a0b34bf6; live main remains 685d83e22cc452e97a2c92ef7ae683f34ceb2371. Immutable synthetic merge 8b2af25d86150e31b547e056fc7a8c251d206f6b has exactly those base/head parents and tree b1d10ffddd898b01c04574a48611696004a2450a, matching the local tested head. However, REST PR metadata still reports base.sha as 7f22bb6ac2892360f3a5c4d3a1f93d9997af43e8. Resolve/re-read this cached requested-base discrepancy before requesting expensive candidate confirmation; a correct synthetic merge alone does not establish a correct requested BASE_SHA. Draft feedback run 39133700370 is separate cheap feedback, not candidate proof. Parent retains proof/merge custody and the sole issue assignment; no cleanup removes that parent-owned claim.

Current confirmation window — 2026-10-19

Independent review found no code findings in the one-file native qualification self-test correction. The documented REST pull-request update with base=main resolved the stale requested-base metadata without changing source, head or target branch. Separate parent readbacks confirm REST base and independently queried live main 685d83e22cc452e97a2c92ef7ae683f34ceb2371, unchanged head 2da0ef1d309d86bfb0725eaa6a6821b0a0b34bf6, and immutable synthetic merge 8b2af25d86150e31b547e056fc7a8c251d206f6b with exactly those base/head parents and tree b1d10ffddd898b01c04574a48611696004a2450a.

The existing complete local preflight, types and restored mutation receipts remain attributed to this unchanged head/base/tree. Production binder, complete inventory, frozen fixture and qualification hashes remain unchanged. Historical confirmations retain their actual identities; none is relabelled as current proof.

The current campaign owns the first final-confirmation and merge window under transferred claim 044-native-20261018. Fresh ready-candidate confirmation is now requested. Every selected job, actual requested identity, checkout and aggregate must qualify before matching-head merge and main reconciliation. Both issue and PR retain milestone 0.44.0. No merge or current hosted success is claimed.

Delivery reconciliation — 2026-10-19

PR #2374 merged as 90a95123cfceb169bd2ecf7c213544db742eaed7. Fetched remote main contains the squash. Its actual parent is the independently verified qualified base 685d83e22cc452e97a2c92ef7ae683f34ceb2371, and tree b1d10ffddd898b01c04574a48611696004a2450a exactly equals ready-confirmation checkout 8b2af25d86150e31b547e056fc7a8c251d206f6b. Complete selected PR proof is recorded in run 39174651919 attempt 1 and the PR; every actual selected checkout and resource/final receipt agrees. This delivers the scoped native self-test correction without changing production guards or qualification hashes.

Fresh readback confirms PR merged, issue closed, and both retain milestone 0.44.0. Automatic main-push CI 39175300737 is in progress and remains pending post-merge reconciliation; no automatic-main success is claimed yet. Downstream workers were notified of the old/new source identities and must qualify their own candidates. This does not deliver any downstream feature or waive its proof.

Automatic main proof reconciled — 2026-10-19

Automatic main-push run 39175300737, attempt 1, concludes failure on the actual verified squash 90a95123cfceb169bd2ecf7c213544db742eaed7. Fifteen execution jobs pass; browser shard 2 fails the unchanged module-settings dark/320 whole-test 15-second deadline, and the aggregate fails. The same existing failure class is tracked in #1229; its new actual checkout, timings, totals and artifact limitations are recorded there. The responsible phase remains unattributed. No unchanged retry, timeout increase or production patch was selected.

The delivered native self-test correction retains complete selected PR confirmation and an exact matching squash parent/tree; no browser source changed in its diff. Issue #2365 remains closed for that scoped correction, and both PR and issue retain 0.44.0. This does not make automatic main CI green or establish a cause for the separate browser failure. Downstream candidates still require their own complete selected proof.

Activity

  1. schlessera
    added
    type: fixSomething is broken and must behave the way it is documented.
    area: ciCI workflows, the gates they run, release scripts, packaging.
    priority: p2Wanted, not scheduled. Pulled in when a milestone has room.
    agent-readyContext and acceptance criteria are complete enough for an agent to take this unattended.
    priority: p1Scheduled into the current or next milestone.
    and removed
    priority: p2Wanted, not scheduled. Pulled in when a milestone has room.
    on Oct 17, 2026
  2. schlessera
    self-assigned this
    on Oct 17, 2026

  3. schlessera commented on Oct 17, 2026

    @schlessera
    schlessera
    on Oct 17, 2026
    OwnerAuthor

    Claim p1-2365-native-fixture-20261018-r1, branch fix/2365-native-frozen-fixture. Scoped implementation custody for #2365 only. Raising priority p2 to p1 because this blocks P1 #2228 / PR #2369: ready run 39074479367, unit (1) job 117518971447 fails the native self-test expecting 859 files and receiving undefined on checkout 50c1bb81b6b96d7fc2d6cb92936dfa5b97f3253b. The original #1943 failure remains separate evidence. Frozen source ownership, exact refusal guards and independent positive/negative controls remain required; no qualification fingerprint refresh is authorized. Parent owns hosted-check watching and final delivery reconciliation.

  4. schlessera commented on Oct 17, 2026

    @schlessera
    schlessera
    on Oct 17, 2026
    OwnerAuthor

    Source-bound dependency handoff from #2228 / #2369: ready run 39074479367 unit (1), job 117518971447, fails COMPLETE_NATIVE_QUALIFICATION_WITHOUT_DOCKER_OR_IMAGE_LOOKUP: expected 859, received undefined; 764 passed / 1 failed / 110,321 assertions. Actual merge 50c1bb81b6b96d7fc2d6cb92936dfa5b97f3253b, parents 498270fbdc4ef2788fdd3babb259b647d77f6c77 and 42c83eb2a2d6ba77dc5fc6fe74909a7e822420f9, tree 651c4b0acc7eb3081401b3829fbf967bcc1fbda0. This is the same exact native self-test drift class already owned here. #2228 now canonically waits on #2365; blocker priority is raised to P1 by the blocker-priority rule. The #2369 worker does not change native binder sources or qualification. After this independent correction lands, #2369 needs fresh affected preflight and complete selected confirmation on its actual combined candidate.

  5. schlessera
    added this to the 0.44.0 milestone on Oct 17, 2026

  6. schlessera commented on Oct 17, 2026

    @schlessera
    schlessera
    on Oct 17, 2026
    OwnerAuthor

    Scoped implementation handoff for claim p1-2365-native-fixture-20261018-r1: PR #2374 is ready at head e7410e696c5ef8eb8efedd88aaa3749af853c89e, base 498270fbdc4ef2788fdd3babb259b647d77f6c77. The complete frozen positive uses independently owned raw Git blobs from delivered 0d780605fe1ea9a281cce947b1f0074f3f3e7acc; production binder, source inventory, all qualification pins and runtime requirements are unchanged.

    Exact #2369 merge-checkout reproduction fails the original expected-859/undefined assertion. Corrected and restored controls on that same changed checkout pass 28 tests / 51,880 assertions; five source/importer/pin/origin/positive-ownership mutations fail intended named assertions and are restored. Required preflight passes all contribution gates, 453 affected tests / 53,904 assertions, and 10 import-graph feedback tests / 51,804 assertions. Original failed/timeout receipts remain failed and are attributed separately in the PR.

    Ready candidate confirmation 39076303374, attempt 1, is requested and pending at handoff; no jobs are allocated yet. Before ready, live main and PR base both matched the recorded base; synthetic merge f7393c4920c5c67177eb313dc8b2e96ed968819c has exactly that base/head as parents and tree 2aefb2b8f97668bd1c4b19749fbd7d850135c156. The earlier opened-draft run 39076284499 is separate cheap feedback. Parent campaign owns watching, actual selected checkout/aggregate reconciliation, review, current-head/base qualification, milestone readback, matching-head merge and delivered-main/closure verification. Both issue and PR read back milestone 0.44.0. This issue remains open and assigned under the existing claim for that continuation; no hosted green or delivery is claimed. #2228 still needs its own fresh combined-candidate proof after this correction lands.

  7. schlessera commented on Oct 17, 2026

    @schlessera
    schlessera
    on Oct 17, 2026
    OwnerAuthor

    Resuming scoped correction under existing claim p1-2365-native-fixture-20261018-r1 on fix/2365-native-frozen-fixture. Fresh ownership read shows the original assignment and no competing claim. Parent has transferred implementation custody back for the hosted strict-typecheck failure in ready run 39076303374 / verify job 117524363094. PR #2374 is draft during correction; original assignment and other owners are preserved. Parent retains hosted watching and final delivery reconciliation.

  8. schlessera commented on Oct 17, 2026

    @schlessera
    schlessera
    on Oct 17, 2026
    OwnerAuthor

    Correction handoff under original claim p1-2365-native-fixture-20261018-r1: PR #2374 is ready at head 80968a3b183af958ddebcb756b632f04909ffec1, base/live main 82a64a13a08c44f2daef425d1a9df2c10840ea8e. Complete strict tsc --noEmit reproduces the exact old TS2769 failure then passes after explicit diagnostic/pin existence narrowing. Offline fixture/refusal controls pass 28 tests; committed preflight passes 453 affected plus 10 import-feedback tests. Missing-diagnostic/missing-pin mutations fail intended existence assertions, restore byte-identically and pass restored targeted controls. Original five mutation receipts retain their original attribution. Test SHA-256 df368d2c560c1c2ebc8b94a333742258e0b272d2112a035795c6bf1dfc46addd. Production hashes, binder and complete inventory remain unchanged.

    Fresh ready confirmation 39077107584, attempt 1, is pending at handoff. Before ready, REST PR base, independently queried live main, local fetched merge and immutable Git API agree: synthetic ff4a2b4d590353772b102f596a76a22259b1e9c6, parents base/head above, tree 6856786f9d61611cae52b060d37a28fa29778a22. Prior ready 39076303374 remains cancelled with actual verify failure and cancelled sibling units; draft/push run 39077083376 is separate feedback. No hosted green is claimed.

    Implementation custody returns to the parent campaign for watching, actual selected-job checkout/requested-base/aggregate verification, current reviews/head/live-base and milestone readbacks, matching-head merge, delivered main proof and closure reconciliation. Both issue and PR read back milestone 0.44.0. Preserve the original assignment/claim during this transfer; no unrelated ownership is removed. T3 PR linkage is registered and verified. This issue remains open; #2228 needs its own fresh combined-candidate proof after delivery.

  9. schlessera commented on Oct 17, 2026

    @schlessera
    schlessera
    on Oct 17, 2026
    OwnerAuthor

    Additional #2376 receipt on starting main 82a64a13a08c44f2daef425d1a9df2c10840ea8e plus its scoped local Docker-transport edits, Bun 1.4.2: the unchanged native-diagram self-test fails COMPLETE_NATIVE_QUALIFICATION_WITHOUT_DOCKER_OR_IMAGE_LOOKUP, expected 859 / received undefined. An owned observer copy (then removed) records source-mismatch with 859 inputs and all three pins matching. Source expected e8502b6ffb3c575f2e9a1c93dea8dbf5ceda93ece367da9d542cb10b1c9ac32b, actual 48bd2c18d694da6e627023f713eeed58960fcb0698812784bc9a073c318a6f25; installation expected 0c2758c046f2b69d5f33b66521baf3098db5f44256b73ec96961c98d381e6245, actual 0f4614b41729d5f1c974a88f0497b77c088c045de6b71a3012ff91d543c2df51 (843 packages / 59,516 files). This includes legitimate producer changes as well as current installation identity; do not refresh either qualification hash to admit it. #2376 now canonically waits here for the frozen-positive/current-drift fixture correction. Its changed native producer separately executes real original SVG/PNG/PDF and absent-host-state controls twice with complete owned cleanup and no added WSL mounts. No retained qualification or whole-candidate green is claimed.

  10. schlessera commented on Oct 18, 2026

    @schlessera
    schlessera
    on Oct 18, 2026
    OwnerAuthor

    Additional independent receipt from #2118 / draft #2176 on 2026-10-18: integrated candidate 0d48379f0a7dece1032b18f012d56d4a8a4f3e12, parents preserved PR head c0111713eadd60adb12194888fc0d7a0fc504bee and main 775eb17aab740fa759c2182f306c38fc17acbcbe, tree ef5e48c7109942706749fb67df89bb8f6dea5dcc, reproduces COMPLETE_NATIVE_QUALIFICATION_WITHOUT_DOCKER_OR_IMAGE_LOOKUP: expected 859, received undefined. Unmodified tests/native-diagram-inputs.test.ts: 0 pass / 1 fail / 2 assertions; 2.41 wall seconds, 2.54 CPU seconds, 596,740 KiB maximum RSS. Own frozen dependencies with Bun 1.4.2, disk-backed temporary files and an ordinary-UID route-free namespace with dropped capabilities. No source, pin, fixture or assertion was changed to admit this candidate.

    The bounded existing self-test failure leaves #2118's complete qualification pending; no full hosted confirmation is being spent before identifying its cause. The already-owned #2374 correction and its owner remain untouched. This receipt is separate from #2118's passing focused admission tests and historical failed stale-admission run.

    Diagnostic correction: a log-only observer, restored byte-for-byte, establishes installation-mismatch, not source drift. Source is exactly the qualified e8502b6ffb3c575f2e9a1c93dea8dbf5ceda93ece367da9d542cb10b1c9ac32b (859 inputs), and all three source pins match. Expected installation 0c2758c046f2b69d5f33b66521baf3098db5f44256b73ec96961c98d381e6245; actual 0f4614b41729d5f1c974a88f0497b77c088c045de6b71a3012ff91d543c2df51 (843 packages / 59,516 files / 1,833,832,764 bytes). This observation alone does not establish that #2365's frozen-source fixture correction resolves this local installation identity. The coordinated continuation is investigating the installed origin before assigning the dependency.

    Resolved local cause: the coordinated install differential establishes shared-cache contamination copied by the normal frozen installation, rather than legitimate candidate source drift. Against the preserved qualified install, 221 records differ: 214 undici files and six @img/colour files changed mode from 0644 to 0666; one vitest cli-api file contains 403 added bytes of prior REPRO1973 diagnostic instrumentation. This candidate's source/pins were already exact. A fresh isolated dependency cache/install is being prepared; no dependency on #2365 is established for this unchanged-source candidate, and no repair to its owned test/pins is requested. The original failure correctly refused the corrupted installation and remains attributed.

    Fresh isolated-cache result on the same unchanged candidate: installation identity returns exactly 0c2758c046f2b69d5f33b66521baf3098db5f44256b73ec96961c98d381e6245 (843 packages / 59,516 files / 1,833,832,361 bytes), and the original native self-test passes all 13 assertions. The native and admission/planner/workflow group passes 91 tests / 998 assertions. Existing #1980 owns the shared-cache contamination; no duplicate issue or #2365 dependency is introduced for #2118.

  11. 3 remaining items

  12. schlessera
    removed their assignment
    on Oct 18, 2026

  13. schlessera commented on Oct 18, 2026

    @schlessera
    schlessera
    on Oct 18, 2026
    OwnerAuthor

    Dependency coordination from the #2370/#2376 blocker chain, without taking over the existing #2365 custody: main now contains #2388 generated-fixture ownership correction (fcb7d5c), #2407 cancellation-fixture TMPDIR correction (78cfba4), and #2299 worker XDG initialization leaf (ea4c76c). Each landed with complete selected proof and matching actual squash tree. The SDK source movement changes native input identity legitimately; do not refresh frozen qualification pins. Live #2374 remains ready at bedb7ba on recorded base 68e12f2. Its historical green needs current-base assessment and fresh requested-candidate reconciliation before delivery, under the existing owner’s custody. #2372 has a local/hosted prerequisite-boundary correction preserved draft at 5b705e1; focused preflight and types pass, but its separate unchanged native qualification self-test still reproduces the exact 859/undefined positive mismatch. Both #2370 and #2376 canonically wait on this correction. The maintainer explicitly leaves this issue with its current owner.

  14. schlessera
    self-assigned this
    on Oct 18, 2026

  15. schlessera commented on Oct 18, 2026

    @schlessera
    schlessera
    on Oct 18, 2026
    OwnerAuthor

    Continuing #2365 only under claim p1-2365-native-fixture-20261018-r2 on fix/2365-native-frozen-fixture, with explicit custody transferred by the parent campaign. Fresh issue/PR comments and assignments show no competing owner. Historical ready run 39086344533 passed its actual selected jobs and aggregate at head bedb7ba0396df63c3d93a609e1143f1227ca464e, base 68e12f27eb249c9fe7262a498a0397c04bbda8f4, checkout 566105cd9cae2b76f87a47168dec6c78500b6134, tree 9775660cd663116e39d76b0655f31aa7c6970e62. Live main is 7f22bb6ac2892360f3a5c4d3a1f93d9997af43e8; GitHub still caches the old PR base. Refresh will integrate verified main and request a fresh candidate confirmation. Production binder, inventory, qualification hashes and independent frozen fixture ownership remain unchanged. Parent owns watching and final merge; this continuation does not touch another issue branch.

  16. schlessera commented on Oct 18, 2026

    @schlessera
    schlessera
    on Oct 18, 2026
    OwnerAuthor

    Historical confirmation 39086344533 / attempt 1 passed on head bedb7ba0396df63c3d93a609e1143f1227ca464e, base 68e12f27eb249c9fe7262a498a0397c04bbda8f4, synthetic 566105cd9cae2b76f87a47168dec6c78500b6134, tree 9775660cd663116e39d76b0655f31aa7c6970e62. Selected jobs: changeset 117553667291, verify 117553827444, unit (1) 117553827496, unit (2) 117553827400, unit (3) 117553827431, unit (4) 117553827405, proof 117554702356. Actual requested BASE_SHA/HEAD_SHA and all selected checkouts agree; all four unit resource receipts and the final candidate receipt agree. The aggregate confirms remaining skips were planner-intended, with no retained domains. That is historical passing proof only.

    2026-10-18 refreshed candidate: head a67c4196699d0c7b73f28f712de0ea13f6d2f5db, verified integrated base/live main 7f22bb6ac2892360f3a5c4d3a1f93d9997af43e8. Before ready, REST PR requested base, independent live main, fetched synthetic merge and immutable Git API agree: synthetic 5819700fb710620090258ab9902e1494462af62e, parents exactly base/head, tree c6cb485a8816a2945dd36bad23ce0f4b51128ea9. The tested committed head has the same tree.

    Five intervening main commits deliver independently frozen generated stylesheet fixtures (#2388), cancellation fixture temp placement (#2407), worker XDG import-order correction (#2299), sandbox-note prepared-output cleanup (#2411) and the callout geometry/capture split with document-binding re-audit (#2393). Worker source changes legitimately change current native source identity. GitHub cached the previous PR base, so verified main was integrated without rewriting history. No conflicts. The PR diff remains only the native self-test; production binder, complete inventory, qualification pins/hashes and frozen source owner remain unchanged. Generated stylesheet and native positives keep their independently owned raw Git blobs.

    Fresh ordinary-UID route-free offline controls, with loopback only, dropped capabilities and the unchanged preload/deadlines, pass 28 tests / 51,871 Bun assertions in 17.87 seconds. Full strict bun run typecheck passes. Committed bun run check:pr --base origin/main passes all contribution gates, 453 affected tests / 53,907 assertions and 10 import-graph feedback tests / 51,807 assertions. Self-test SHA-256 remains df368d2c560c1c2ebc8b94a333742258e0b272d2112a035795c6bf1dfc46addd. Original failing-first, TS2769 and intended/restored mutation receipts keep their actual historical attribution. No consumer-visible change or changeset.

    Fresh ready confirmation 39111042672, attempt 1, is requested and pending at the initial handoff read. Draft/push feedback 39111013813 is separate; contract run 39111013789 passed. No current hosted green or delivery is claimed. Parent owns watching, actual requested BASE_SHA/selected job checkout and inventory/aggregate validation, fresh review/head/live-base/milestone readbacks, matching-head merge and delivered-main/closure reconciliation. Both issue and PR retain milestone 0.44.0. #2228 / #2369 and all other issue branches remain untouched and need their own qualification after this prerequisite lands.

    Implementation custody returns to the parent. Claim p1-2365-native-fixture-20261018-r2 is released under serialized cleanup after fresh uncontested ownership reconciliation; preserved branch and receipts remain available. The implementation sub-agent does not watch or merge. PR linkage is registered and verified.

  17. schlessera
    removed their assignment
    on Oct 18, 2026

  18. schlessera commented on Oct 18, 2026

    @schlessera
    schlessera
    on Oct 18, 2026
    OwnerAuthor

    Dependency coordination only; the maintainer leaves #2365 with its current owner. Main now includes completed #2375 documentation/qualification through #2381, squash 268b76b over 7f22bb6. That latest advance changes only docs/process/testing.md, with no native source, binder, fixture or qualification pin changes. Your a67c419 candidate retains its historical passing base identity; please assess the docs-only base advance and request confirmation for the actual final base before matching-head merge. #2370 and #2376 remain pending on this prerequisite; this campaign does not take over, rewrite or merge your branch.

  19. schlessera
    self-assigned this
    on Oct 18, 2026

  20. schlessera commented on Oct 18, 2026

    @schlessera
    schlessera
    on Oct 18, 2026
    OwnerAuthor

    0.44.0 campaign claim 044-native-20261018: serialized ownership readback confirms this issue was unassigned. The prior owner has completed its run; preserved implementation and historical receipts remain attributed. GPT-6.1-Sol worker owns readiness, scoped implementation/qualification on fix/2365-native-frozen-fixture (or a recorded unique branch if needed). The campaign coordinator serializes final candidate confirmation and merge windows; this claim does not authorize concurrent merges or bypass any existing proof requirement.

  21. schlessera commented on Oct 18, 2026

    @schlessera
    schlessera
    on Oct 18, 2026
    OwnerAuthor

    Campaign claim 044-native-20261018: read-only handoff audit confirms ready confirmation 39111042672 attempt 1 passed every selected job on head a67c4196699d0c7b73f28f712de0ea13f6d2f5db, base 7f22bb6ac2892360f3a5c4d3a1f93d9997af43e8, checkout 5819700fb710620090258ab9902e1494462af62e, tree c6cb485a8816a2945dd36bad23ce0f4b51128ea9. Metadata, verify, all four unit resource receipts and final candidate receipt agree; the immutable Git API confirms parents/tree. Aggregate reports remaining skips planner-intended and no retained domains. This remains historical proof because main advanced.

    A preserved local integration candidate includes current main 685d83e22cc452e97a2c92ef7ae683f34ceb2371 plus the existing implementation, with only the native self-test differing from main. Neither test implementation nor production binder changed during this continuation. Main advancement includes #2381, #2415 and #2398, so fresh final-base proof remains required.

    Fresh focused preflight passes lint/leakage, environment documentation, changeset package names and contribution changeset checks, then fails before test assertions with ENOSPC creating the workspace-operation directory. The separate ordinary-UID, route-free, loopback-only controls also stop at the same setup error, without running assertions. This is unavailable proof, not passing tests or a new behavioral failure. Shared filesystem capacity must be restored before rerunning the focused preflight and offline controls. Parent retains the serialized claim, final candidate-confirmation window and merge custody. No PR push, ready transition, merge, qualification-hash refresh or unrelated issue change occurred.

  22. schlessera commented on Oct 18, 2026

    @schlessera
    schlessera
    on Oct 18, 2026
    OwnerAuthor

    Campaign candidate, 2026-10-18

    Claim 044-native-20261018: refreshed head 2da0ef1d309d86bfb0725eaa6a6821b0a0b34bf6, base 685d83e22cc452e97a2c92ef7ae683f34ceb2371, tree b1d10ffddd898b01c04574a48611696004a2450a. The non-rewriting integration preserves prior head a67c4196699d0c7b73f28f712de0ea13f6d2f5db; main advances #2381, #2415 and #2398 are included. Only the native self-test differs from main. Its SHA-256 remains df368d2c560c1c2ebc8b94a333742258e0b272d2112a035795c6bf1dfc46addd; production binder, complete inventory, qualification pins/hashes and independent frozen source remain unchanged. No shipped package or contract change and no changeset.

    Historical ready confirmation 39111042672 attempt 1 passed all selected jobs at the prior head and base 7f22bb6ac2892360f3a5c4d3a1f93d9997af43e8, checkout 5819700fb710620090258ab9902e1494462af62e, tree c6cb485a8816a2945dd36bad23ce0f4b51128ea9. This continuation verified metadata/verify/unit checkouts, all four resource receipts, the final candidate receipt and immutable API parents/tree. The aggregate confirms planner-intended skips with no retained domains. That proof is historical, not proof of the refreshed base.

    Fresh local receipts:

    • Initial preflight and offline attempts failed before assertions with ENOSPC. Capacity subsequently became available; those setup failures remain recorded.
    • The first frozen copyfile install from the existing shared cache produced installation identity 0f4614b41729d5f1c974a88f0497b77c088c045de6b71a3012ff91d543c2df51, matching the affected identity already documented in ci: isolate diagnostic dependency edits from the shared install cache #1980. Offline controls failed 23 pass / 5 fail, including the frozen positive. These failures remain separate from source drift and passing recovery evidence.
    • Replacing only this owned installation using a fresh private cache and bun install --force --frozen-lockfile --backend=copyfile restores qualified installation 0c2758c046f2b69d5f33b66521baf3098db5f44256b73ec96961c98d381e6245: 843 packages, 59,516 files, 1,833,832,361 bytes. The recovered Vitest chunk hash is a236001d048380e2c67d05423fc9ea3f26b07ee019ba8d6e622082f29d49102e. The shared cache and other installations were not modified. ci: isolate diagnostic dependency edits from the shared install cache #1980 preventive work remains separate.
    • Ordinary-UID route-free offline namespace controls with loopback only, dropped capabilities and unchanged preload/deadlines pass 28 tests / 51,871 assertions before mutation and again after restoration (10.59 seconds restored).
    • Removing the production source-mismatch refusal makes added package source requires native requalification fail at NATIVE_SOURCE_ADDITION_REQUIRES_REQUALIFICATION because binding is unexpectedly returned. Production binder is restored byte-identically, SHA-256 42defd431b016ab527652188a2dd0bad4f249eb49e52e69097b015f5bdabe4f5. Original positive-ownership/importer/pin/origin and missing-diagnostic mutations retain their historical attribution.
    • Full strict bun run typecheck passes with the recovered dependencies. Committed bun run check:pr --base origin/main passes all contribution gates, 456 affected tests / 53,933 assertions and 10 import-graph feedback tests / 51,807 assertions. git diff --check origin/main passes.

    PR #2374 stays draft. No fresh ready-candidate confirmation, auto-merge or merge was requested. Parent retains the serialized assignment and owns the first proof/merge window, actual final requested base/head/selected-job checkout reconciliation, review and milestone readbacks, matching-head merge and delivered-main verification. Both issue and PR retain milestone 0.44.0. #2409 remains independently owned and untouched. This candidate is locally ready for that window; complete fresh selected hosted proof remains required.

  23. schlessera commented on Oct 18, 2026

    @schlessera
    schlessera
    on Oct 18, 2026
    OwnerAuthor

    Final identity readback: remote head is 2da0ef1d309d86bfb0725eaa6a6821b0a0b34bf6; live main remains 685d83e22cc452e97a2c92ef7ae683f34ceb2371. Immutable synthetic merge 8b2af25d86150e31b547e056fc7a8c251d206f6b has exactly those base/head parents and tree b1d10ffddd898b01c04574a48611696004a2450a, matching the local tested head. However, REST PR metadata still reports base.sha as 7f22bb6ac2892360f3a5c4d3a1f93d9997af43e8. Resolve/re-read this cached requested-base discrepancy before requesting expensive candidate confirmation; a correct synthetic merge alone does not establish a correct requested BASE_SHA. Draft feedback run 39133700370 is separate cheap feedback, not candidate proof. Parent retains proof/merge custody and the sole issue assignment; no cleanup removes that parent-owned claim.

  24. schlessera commented on Oct 18, 2026

    @schlessera
    schlessera
    on Oct 18, 2026
    OwnerAuthor

    2026-10-19 custody reconciliation: the prior P1 campaign coordinator explicitly transfers its retained #2365 implementation-coordination, confirmation and merge custody to this user-authorized 0.44.0 campaign. It reports no live worker or local run conflict and has stopped its PR watch. Retain claim 044-native-20261018 and its sole assignment; this is a custody continuation, not a competing claim.

    Remote head remains 2da0ef1d309d86bfb0725eaa6a6821b0a0b34bf6, independently queried live main 685d83e22cc452e97a2c92ef7ae683f34ceb2371, and immutable synthetic merge 8b2af25d86150e31b547e056fc7a8c251d206f6b. REST base still reports 7f22bb6ac2892360f3a5c4d3a1f93d9997af43e8. Preserve the fully attributed local receipts and correct production guards. Resolve this requested-base discrepancy before fresh confirmation; no historical proof is relabelled current. This campaign reserves the first final-confirmation and merge window for this shared prerequisite.

  25. schlessera
    closed this as completedin #2374on Oct 18, 2026

  26. schlessera commented on Oct 18, 2026

    @schlessera
    schlessera
    on Oct 18, 2026
    OwnerAuthor

    Delivery reconciliation — 2026-10-19

    PR #2374 merged as 90a95123cfceb169bd2ecf7c213544db742eaed7. Fetched remote main contains the squash. Its actual parent is the independently verified qualified base 685d83e22cc452e97a2c92ef7ae683f34ceb2371, and tree b1d10ffddd898b01c04574a48611696004a2450a exactly equals ready-confirmation checkout 8b2af25d86150e31b547e056fc7a8c251d206f6b. Complete selected PR proof is recorded in run 39174651919 attempt 1 and the PR; every actual selected checkout and resource/final receipt agrees. This delivers the scoped native self-test correction without changing production guards or qualification hashes.

    Fresh readback confirms PR merged, issue closed, and both retain milestone 0.44.0. Automatic main-push CI 39175300737 is in progress and remains pending post-merge reconciliation; no automatic-main success is claimed yet. Downstream workers were notified of the old/new source identities and must qualify their own candidates. This does not deliver any downstream feature or waive its proof.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

agent-readyContext and acceptance criteria are complete enough for an agent to take this unattended.area: ciCI workflows, the gates they run, release scripts, packaging.priority: p1Scheduled into the current or next milestone.type: fixSomething is broken and must behave the way it is documented.

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions