Skip to content

[SVG-RELEASE-D] Qualify and activate the current Release-D coherent receiver successor #4644

Closed
2 of 2 issues completed

Description

@EHotwagner

Owner

Programme/root (current Codex coordinator) owns the Release-D cross-repository join and this single post-pin receiver qualification. Existing producer, Wizard release and workspace receiver owners retain source/publication authority; no new source implementation is selected.

Done when

Complete the current SVG-RELEASE-D successor through the exact compatible public producer set and full Wizard/workspace receiver acceptance specified by the owning plan. A Templates-only receiver result cannot stand for full adoption.

Current deliverable

Current-public D.5 remains owned by #4849. Source PR769 is delivered at protected 3b7cd90e2cb28b6595062d091638eab44562ebe0. Root accepted 40057752243/a1 only as original UID-map failure evidence and scoped two-group/outer-unit retirement; collection-incomplete is secondary and parent diagnostics are not child-cause proof. SDK/backend and receiver semantics were not reached. Original40047202735 retains its own failure/retirement scope. No successor activation or runtime is selected.

Preserved accepted clean-creation tail:

Post-pin clean-creation/default-readback tail independently accepted on39988246429/a1, exact Templatesaf7a603f118acdf5b63c82695fdcc2db617d2b49. Artifact12516283858 SHA1cdd00f5e0d9407afe689e2cf1f95d39bfb313cfd472ae8658f88daa01890169 has20verifiedmembers; four builds, dedicated direct/provider/Wizard browser checks, typed-sdd/player omission, explicit none/typed and four current hives pass. Seven determining source/pin files remain byte-identical. This operation is retired; full4644 is not closed.

Next action

Root and the existing D.5 source owner propose a bounded kernel-audit plus loaded-policy/package-source read for the same literal prerequisite, only after separately reviewed source, operational profile and a fresh condition. No such source activation or native operation is selected. Do not infer AppArmor causation, weaken NNP/namespace flags/policy, use an alternative backend or resend either original. Resolve the prerequisite with actual evidence before selecting any later rehearsal; all three rehearsal receivers and the full raw-plus42-case matrix still need their own qualified evidence.

Acceptance evidence

Current diagnostic disposition: run40057752243/a1, protected 3b7cd90e2cb28b6595062d091638eab44562ebe0 / PR769, and Root acceptance. Condition6378268333 was used for one original POST: T0 2026-10-24T03:18:15.538559Z, latest first step 03:23:15.538559Z, observer end 03:58:15.538559Z; no renewal or retry. Artifact12546420237 SHA256 4ec06657a40c870ce4aff0d00c0d12be61ca8c2e32a3d5671c28cc7103c91906: 21 original files/15 indexed entries independently verified. Accepted scope is original failure custody, two managed groups and joined outer-unit retirement, plus bounded reader direct handles. Initial census uncertainty and original log-read refusal remain retained. No SDK/backend or child-cause acceptance; original40047202735 remains unchanged.

Previous pre-dispatch/source checkpoint (historical; its no-successor/T0-unset census is superseded above):

Diagnostic successor source delivered: FS-GG/FS.GG.Templates#769, protected3b7cd90e2cb28b6595062d091638eab44562ebe0/tree78ed40d3bb21697a7f82ec516ec5635b98d2c9a7, matching reviewed33c04e384784cfb5e5ca443921c3f5300d1c4382. New conditional SOURCE selection #4849 (comment) expires for first dispatch at2026-10-24T03:30:00Z. Current manual census retains only failed40047202735/attempt1; no successor run/T0/intent is selected. Thirteen determining native source files match the reviewed tree, including current reader/adapter seals; the complete public tuple and canonical owner remain unchanged. Source delivery supplies no runtime or cause acceptance.

Preserved preceding evidence:

Current D.5 original failure and scoped retirement: https://github.com/FS-GG/FS.GG.Templates/actions/runs/40047202735 (attempt1), source8179803c31d27490edacb269a51a8aad3d8800cc / FS-GG/FS.GG.Templates#768; owning evidence and Root acceptance on #4849. Artifact12541488846 SHA256 d92b514c0306c8874d1fd6a48d85cb9affd535800fb76867b4d2487beb99b4e4:21 safe members,15 indexed entries verified; two contained groups with EOF/reap/empty removal, independent same-boot original-unit birth absence and bounded receiver retirement. This is scoped failure/custody acceptance, not backend/refusal/matrix success; native UTC trust/skew and provider disposal stay unproved.

Preserved preceding acceptance evidence:

Current accepted tail: https://github.com/FS-GG/FS.GG.Templates/actions/runs/39988246429/a1, artifact12516283858/sha256:1cdd00f5e0d9407afe689e2cf1f95d39bfb313cfd472ae8658f88daa01890169. Dedicated browser cases pass1each; broader suites retain16passed/21skipped x3 and public2passed/18skipped, unchanged from priorfull qualification; no blanket browser coverage claim. Root scoped acceptance/retirement preserves the current backend/refusal matrix gap.

Current candidate acceptance: #4644 (comment); completed prerequisite #4811 and public activation PR4838/1fac8e920392b9dca50b8ae315bcadb36216cd3f. Prior full run39946080162 preceded that activation and is not post-pin evidence. The following original history is preserved at its recorded scope.

2026-10-21 original-tag-intent hold: root accepted source765eda5c6d75f11134c2d3011f0d9868e98c3f19/tree43034, all20 source checks and33 actual F# entry controls, plus fresh READ-ONLY preflight39541203598/a1/all5ZIPs7JSON/19completecensusABSENT/19scopeGET200/19public404. Accepted full02 browser45/nativeAT15/four speech/27 evidence and original19 producer4ec archives remain valid and distinct from publication. STAGE1 original tag run39541842303/a1 failed in cut job119031172204: only refs/tags/fs-gg-ui/v0.32.3→4ec6eafbbbf02264db9b0db4780c590abe0bf9cd was push-requested at04:02:47.727566Z; exit1/Unknown by04:02:48.642629Z, no acknowledgement, one read-only first-ref probe then stop. Both original plan/cut ZIPs and exact receipts are retained. Independent subsequent native reads show allthree refs ABSENT, but do not prove historical no-effect or settle the original Unknown. Classification says workflow-permission/remote-rejection; raw server cause was not retained/authenticated. Bounded source assessment confirms Rendering check/cut has no authenticated same-original-intent settlement or continuation. Proposed distinct administrative recovery was NOT admitted: a new identity, current absence, workflow fencing or credential grants alone cannot authorize resend. No disable/enable, replacement ref, rerun, publisher or notification effect occurred. Root holds the affected tag/publication path pending original authenticated transaction evidence OR a separately qualified authorized Rendering same-original-intent mechanism. Process finding owned by this4709 owner: tag helper captured but discarded raw failure output, leaving only classification/counts and preventing authenticated original-outcome diagnosis. Future logs cannot reconstruct this original; retain the eventual natural source diagnostic/Atlas capture gap, with no filler PR/framework or protected source change selected. Original source-plan publicationReady:false, source actualScreenReader:not-observed, separate genuine AT proof, historical failures/Unknowns and whole public/installed/downstream promise remain unchanged.

Preserved preceding acceptance checkpoint:
2026-10-21 SOURCE merge checkpoint: PR1458 merged normally as protected765eda5c6d75f11134c2d3011f0d9868e98c3f19/tree43034e402e4699cc66a5613f3bd3704f8e348fa6, parentbeed, after all20 current checks/all5 required contexts, independent review and native CLEAN/protection joins. Actual pinnedSDK401 F# typed186/45/15/4/27 predicate and all33 actual-entry controls passed67.520s without credentials/network/receipt; actual testedAPImerge c639 parentsbeed+9001 has the identical reviewed tree, and Deterministic checked out9001. Original watch01 timed out as an observer only (EOFfalse preserved, exact known groups absent); watch02 exited0/EOF/reaped and exact known groups absent. Fresh read-only preflight for final executor765 is prepared DISABLED with the genuine original4ec archives/full02 evidence and actual8input schema; root separate admission, fresh authority/collisions and a new original operation are required. No new preflight/tag/package/feed/publication effect follows this source merge. Effective writer authority and all public/installed/downstream promises remain unproved/open.

Preserved preceding acceptance checkpoint:
2026-10-21 source/read-only checkpoint: PR1457 merged normally as beed7ff901292d13b9242c381c1ff676201a8651/treeadd4f31f after all20 current checks and tested-tree joins. Root accepted only the new original READ-ONLY preflight39537924887/a1: all5 original ZIPs/seven JSON members verified, all19 complete active/deleted census ABSENT, all19 existing-ID scope GETs HTTP200 and public target404. Supported GitHub NuGet-client baseline restore passed while the separate direct archive403 remains historical/read-path evidence; effective writer acknowledgement remains unproved. Before any tag/package effect, composition diagnosis found the transitive F# writer still refused0323. The prior six-path source change and independent top-level review omitted that entry, despite the intentionally correct earlier read-only selector. Same owner repaired the complete existing entry/typed eligibility/controls in PR1458 FS-GG/FS.GG.Rendering#1458 at independently reviewed9001e1898025172f390f29a7e9baf72dc2976144/tree43034e402e4699cc66a5613f3bd3704f8e348fa6, exactly five paths. Distinct closed0323 joins preserve raw plan89369/original4ec19 archives and full02 native AT;186/45/15/4/27 eligibility preserves both historical predicates.59 Python controls passed; actual pinnedSDK401 F# compilation and33 credential-free entry cases are pending on original gate39539364232/a1. Owned disposition: transitive writer-entry qualification must be inspected and actually executed in the existing no-credential source job, rather than inferred from top-level Python source tests; no duplicate standards/framework introduced. New source1800 retired185.802s and separate metadata1800 now owns this delivery. No tag, package/feed write, preflight rerun, publication or adoption is selected; all original promises, immutable plan/read qualification fields, failures and current authority Unknowns remain.

Preserved preceding acceptance checkpoint:
2026-10-21 source checkpoint: Rendering PR1457 FS-GG/FS.GG.Rendering#1457 is OPEN at independently reviewed4fa8c6a81b03532840bbc8c760e555f6657199fd/treeadd4f31fe94c1706afab1ce04f06a17817008ba0, base4e48c97533554ccece8db3db828c4cc327464050. Exactly six maintained paths bind accepted full02 run39531420324/a1/artifact12315224479/root7dab9d3473110961508570af4ad7e95cbc05918dde4b23f2a61a64c8f6d02c4f to the qualified0.32.3 source route;57 source+26 tag controls and sole independent source review PASS. Original19 producer4ec archives/source run39509314882, immutable source plan publicationReady:false, separate source actualScreenReader:not-observed and genuine AT observation remain distinct. Historical0321/0322 attempts, GitHub baseline403 and current write-authority Unknowns remain. This qualifies SOURCE only; no publication/tag/feed/OIDC/full-runtime operation is selected. Current required/material hosted CI is pending on original39535743917/a1. Source1800 retired1013.928s; separate metadata1800 is active. Original source/control refusals and all full02 evidence are retained.

Preserved preceding active checkpoint (observed history):
Prior deliverable: SVG4709 candidate receiver/AT prerequisite advanced within the broader parent promise. Root accepted the second closed original Rendering 0.32.3 receiver/AT qualification, run 39531420324/attempt1, protected caller4e48c97533554ccece8db3db828c4cc327464050 and Templates752a2ac1fa996c3235ac0330ffbcefb6b8301cb4:45 exact single-attempt browser cases,186 Provider assertions,15 real Orca actions/four genuine speech observations and scoped custody/cleanup joins. Original producer4ec6eafbbbf02264db9b0db4780c590abe0bf9cd/run39509314882/a1/artifact12305198394 and all19 original archives remain unchanged. Full02 artifact12315224479/rawSHA256 d6df73c1baf26d7a75a7db7e13e0c0c55429a69e150ea4581f8afcbabb9aa2c5; independent root scoped acceptance7dab9d3473110961508570af4ad7e95cbc05918dde4b23f2a61a64c8f6d02c4f. This is scoped candidate receiver/AT acceptance, not publication, public adoption, Template728 merge or complete Delivery acceptance. First full39526276388 log-cap failure and historical public0.32.1 material font failures remain separate original evidence. Root released the4e48 qualification horizon after retention; historic512MiB watcher Unknown remains reserved.

Prior next action: Same SVG4709 owner is preparing closed publication progression with Rendering producer source owner: current protected release-source-guard deliberately refuses 0.32.3 acquisition/events/readiness, so first deliver a separately reviewed immutable full02 proof binding/validator/acquisition/event/tag source extension through the existing publisher route, preserving0.32.1/0.32.2 subjects and original19 bytes. Historical preflight39520796171 all19 NuGet verify-key HTTP200 authorization is retained separately from GitHub baseline archive403 and effective writer Unknown; fresh selected-executor source/authority/collision gates still precede any admitted publication. No publication POST, rebuild/repack, speculative public default or Template728 merge is selected. Root retains final source/profile/operation admission;4709 then4644 remain In progress for this active owned continuation. Full Done when and downstream/installed/default/lifecycle/bundle promises remain unchanged.

Blocked on

The new diagnostic attempt failed before SDK/Go/package acquisition, backend or typed receiver qualification. The child’s post-exec/post-CLONE denial cause is unproved; parent observations alone do not settle it. Missing later executable/input metadata remains a collection secondary. All43 D.5 receivers and complete #4849/#4644 acceptance remain open. Provider physical disposal, native UTC skew, universal metadata-descendant containment and all439+46 plus the named earlier-three hold remain Unknown/unreleased. No new operation or policy activation is selected.

Activity

  1. EHotwagner commented on Oct 22, 2026

    @EHotwagner
    ContributorAuthor

    fdev 2026-10-23: child #4709 is accepted complete: the public SVG successor is qualified through the full public Wizard route on Workspace.Template 0.19.2, SDD 2.4.0 and Wizard 0.21.0, with Rendering 0.32.3. A new blocker for this Outcome's default-activation claim is filed as #4811: when the lifecycle is omitted, Wizard creation records sdd, not the D.5 typed-sdd, because the typed-sdd default is pinned to Workspace.Template 0.15.0 only. That Wizard-owner fix is needed before #4644 can claim the activated default.

  2. EHotwagner commented on Oct 23, 2026

    @EHotwagner
    ContributorAuthor

    fdev refresh (user-delegated): Next action and Blocked on

    The old original-tag-intent hold no longer gates this Outcome. Per #4709's acceptance:

    The old Current deliverable ("None") and Next action are retained as history.

    Current deliverable: #4709 accepted.

    Blocked on: #4811. Wizard 0.21.0 records sdd for an omitted fable-game lifecycle; D.5 promises typed-sdd.

    • selectScaffoldLifecycle is pinned to descriptor ::0.15.0 (Program.fs L160–170).
    • The fix must explicitly supersede tsdd-knowledge-wizard.md L424 (PR Bootstrap typed project knowledge before Wizard handoff #4142, 2026-10-03): "0.17 and provisional 0.18 descriptors remain Standard SDD unless a caller explicitly selects typed SDD".
    • Deriving the default from the descriptor keeps fable-bindings at sdd: its parameters entry key: lifecycle has default: sdd, while fable-game declares typed-sdd.

    Next action, after #4811 merges and a Wizard successor is published:

    1. One read-only qualification on fable-reference-public full, with a new closed cohort for that Wizard (the FS.GG.Templates#739 pattern), on the current published Workspace.Template (0.19.3 today).
    2. Assert: Wizard omitted → typed-sdd with quint-specification-v1; the refusal path; explicit tokens and bundles unchanged.
    3. D.5's tail: update the public pins, repeat clean creation, and read back the default independently.

    Retained-workspace upgrades stay a separate qualification.

    — fdev

  3. EHotwagner commented on Oct 23, 2026

    @EHotwagner
    ContributorAuthor

    fdev 2026-10-23, Templates owner: default Wizard SVG creation is now typed-sdd, qualified hosted. This is read-only full run 39946080162 on Wizard 0.22.0 + Workspace.Template 0.19.3 + SDD 2.4.0: passed.

    Verifier flip: Templates#760 merged as a3b5476b85a1630b84c5b8bae40916a575a21219.

    • Pin: Wizard 0.22.0, nuget.org signed archive caa91285e5370edc7a8a14a5a46f6cfef236d1db95f1e186357e6591b9ec7bd5, revision 6e6fb9b9f7677e26f0c7d58cab1646323e81df58 (the tag new-sdd-workspace/v0.22.0 and the nuspec commit agree).
    • Full mode:
      • the Wizard 0.21.0 sdd override is deleted;
      • the Wizard route and the public default (player bundle) now assert typed-sdd;
      • the superseded 0.21.0 cohort is refused.
    • Review: the first independent review returned REQUEST CHANGES. Part of the Wizard omitted-lifecycle default falls back to sdd for current templates (typed-sdd only for Workspace.Template 0.15.0) #4811 spec (verifier L103 and L112–113, test L159 and L289, roadmap L468) belongs to the Wizard 0.19/0.20 metadata route, where sdd is correct, so those lines stay sdd (#4811 comment 6363447499). The second review gave ACCEPT on 1a017d46.
    • Merge: green checks, and main's tree equals the reviewed head.

    The run:

    • Dispatched once at 11:26:23Z, attempt 1, head a3b5476b. Success at 11:44:34Z.
    • Artifact 12499500583, sha256:df3132da607f310f3d847514fa0ccb8cc7fbea4baf765fcb4f490b21ed80bf0c.
    • qualification.json: disposition: passed, wizardQualification: passed, Wizard 0.22.0/caa91285/6e6fb9b9, SDD 2.4.0 1df2e74f, Workspace.Template 0.19.3 9594ec20 (tag at 7be0bcf5), descriptor 6b3d8f2d.
    • readback.sha256 lists exactly those four identities.

    The D.5 activation evidence. These are the Wizard scaffold effectiveParameters, compared with the Wizard 0.21.0 run 39915065069 on the same template and SDD:

    receiver lifecycle requested 0.21.0 recorded 0.22.0 recorded
    wizard-public (player, the exact public default) omitted sdd typed-sdd
    wizard (complete) omitted sdd typed-sdd
    wizard-typed typed-sdd typed-sdd typed-sdd
    wizard-none none none none
    • What the typed-knowledge path adds: the default-created workspaces gain exactly four files that 0.21.0 did not create: .fsgg/knowledge/records/project-knowledge.json, .fsgg/knowledge/schema.json, .github/workflows/project-knowledge.yml and scripts/check-project-knowledge.py. Nothing was removed.
    • The checker's own assertion passed: the public default's scaffold-provenance.json has lifecycle typed-sdd, bundle player and generator SDD 2.4.0.
    • Builds and browser: all four receivers (direct, provider, wizard, wizard-public) built with 0 warnings and 0 errors. Every per-project test total is identical to 0.21.0's: for example, wizard-public has Domain 18, Protocol 26 and Server 20, all passing. The browser runs on direct, provider and wizard each passed.
    • Hives: all four Wizard hives (wizard, wizard-public, wizard-typed, wizard-none) resolved Workspace.Template 0.19.3.

    Limits:

    For #4811 and #4644: the Templates receiver flip is merged, and the published Wizard 0.22.0 now creates typed-sdd by default on the current public SVG template, proven hosted. I am not closing or changing the status of anything; closure is for the coordinator.

  4. EHotwagner commented on Oct 23, 2026

    @EHotwagner
    ContributorAuthor

    Programme/root selected and dispatched exactly one D.5 post-pin full qualification: https://github.com/FS-GG/FS.GG.Templates/actions/runs/39988246429 / attempt1, source af7a603f118acdf5b63c82695fdcc2db617d2b49, started 2026-10-23T16:36:58Z. The12 exact inputs use Workspace.Template0.19.3 / SDD2.4.0 / Wizard0.22.0 and their previously authenticated hashes. Native unique-run readback matches the original successful POST; no prior post-pin attempt exists. An earlier launcher clock-initialization error occurred before any API call/send and is retained separately.

    Current protected source/runtime bytes and activated registry/projection pins matched before dispatch. Selected resource is the existing single GitHub-hosted public-reference job (70-minute job cap); provider scheduling controls queue/allocation, with no fabricated numeric CPU/RAM or spare-org-slot claim. BAR1055, enrollment4848 CI and historical439+46holds remain accounted separately. Original metadata/evidence deadline18:06:48UTC; no automatic rerun or cancellation. Root owns run/artifact/default readback and full owning-plan acceptance; green workflow alone will not close this Outcome.

  5. EHotwagner commented on Oct 24, 2026

    @EHotwagner
    ContributorAuthor

    Root decision — 2026-10-24 ~15:10 UTC, fdev (Programme/root), under the repository owner's explicit delegation in the interactive session ('you decide the rest').

    User-namespace prerequisite. On ephemeral GitHub-hosted runners only, the diagnostic or qualification job may run the reviewed step sudo sysctl -w kernel.apparmor_restrict_unprivileged_userns=0 before the backend starts, and record the before/after value. This is a controlled A/B test of the AppArmor hypothesis, not an inference of it. It is never applied to Home or self-hosted machines. The NNP/namespace flags and the backend stay unchanged. If the denial persists with the restriction off, AppArmor is ruled out and the original diagnosis continues.

  6. EHotwagner commented on Oct 24, 2026

    @EHotwagner
    ContributorAuthor

    fdev: hosted user-namespace prerequisite cause established by A/B (AppArmor restriction on ubuntu-24.04): evidence #4849 (comment) and follow-up (permanent hosted step Templates#773, Atlas #774) #4849 . No D.5 receiver qualified; #4644 remains open pending a fresh Root selection of the D5 rehearsal.

  7. EHotwagner commented on Oct 24, 2026

    @EHotwagner
    ContributorAuthor

    fdev: D5 first rehearsal original 40121103111/a1 (Root-delegated single dispatch) failed at the ProviderTool backend check, a qualifier-source layout defect, after passing namespace, SDK/Go/packages, 3/3 rehearsal receiver checks and the default-backend author/inspect/refusal on provider-omitted. 0/43 receivers qualified; details and next step: #4849 (comment) . #4644 stays open.

  8. EHotwagner commented on Oct 24, 2026

    @EHotwagner
    ContributorAuthor

    fdev: D5 first-rehearsal rerun 40124373443/a1 passed (receiver-checks-complete): 3 of 3 rehearsal receivers incl. default quint-specification-v1 author/inspect/wrong-profile refusal on both typed receivers; 3 of 43 evidenced, pending Root acceptance. Details: #4849 (comment) . #4644 stays open (40 receivers, matrix, browser/AT scope).

  9. EHotwagner commented on Oct 24, 2026

    @EHotwagner
    ContributorAuthor

    fdev: D5 full-matrix original 40127488229/a1 passed (receiver-checks-complete): 43 of 43 receiver checks incl. both typed receivers' default-backend author/inspect/refusal; pending Root acceptance. Details: #4849 (latest owner comment). #4816 earlier-three 40125840475 also passed (#4816 (comment)). Closure remains Root's.

  10. EHotwagner commented on Oct 24, 2026

    @EHotwagner
    ContributorAuthor

    fdev, #4849/#4816 owner (Root-requested reconciliation): #4644 whole remaining promise versus what is now accepted. Read at protected .github main 1cdc6266 and Templates main 668bc698. This is a list for Root's parent-level decision; it accepts nothing and changes no Status.

    The promise. "Complete the current SVG-RELEASE-D successor through the exact compatible public producer set and full Wizard/workspace receiver acceptance specified by the owning plan. A Templates-only receiver result cannot stand for full adoption." Constraints from the design table (2026-10-19-board-clearing-lifecycle-design.md, #4644 row): preserve the original public/default, explicit lifecycle/SVG choices and separately promised retained upgrades; durable public hosting #491 stays separate; source versions do not prove activation.

    Accepted (with the evidence Root already recorded):

    Component of the promise Evidence Status
    Exact compatible public producer set published and registry-reconciled Wizard 0.22.0 (registry PR .github#4838 1fac8e92, registry/dependencies.yml, docs/registry/compatibility.md show new-sdd-workspace 0.22.0, fs-gg-workspace-template 0.19.3); SDD 2.4.0; Rendering 0.32.3 via #4709 accepted (#4709, #4811, #4642 are CLOSED)
    Public default and lifecycle activation Wizard omitted -> typed-sdd (verifier Templates#760, hosted run 39946080162; candidate acceptance 6364132303); omitted fable-game default follows descriptor (#4811 closed) accepted
    Clean creation, four builds, dedicated browsers on the post-pin tuple 39988246429/a1, artifact 12516283858 (20 verified members) accepted
    Full Wizard/workspace receiver contract: omitted routes, explicit lifecycle tokens, named SVG bundles, default backend author/inspect, wrong-profile refusal #4849 (CLOSED, acceptance): rehearsal 40124373443/a1 3/3; full matrix 40127488229/a1 43/43 accepted
    Hosted user-namespace prerequisite A/B 40116649986: AppArmor apparmor_restrict_unprivileged_userns; hosted-only step in the profile (Templates#773, #776) accepted

    What activation still requires (nothing in the first four rows is open source work):

    # Remaining item Why it matters to #4644 Supplier
    1 A parent-level acceptance/decision comment reconciling the table above Parents are never rolled up automatically; Blocked on/Next action in the #4644 body still describe the failed 40057752243 attempt and say no operation is selected, which is stale Root (Programme/root); body refresh is Root's Status/body write
    2 Decide whether separately promised retained upgrades gate #4644 The design table says to preserve them, they live under #4816/#4646. Evidence now: 0.13 (40032045163) and 0.10/0.11/0.12 (40125840475) materialization, five transaction controls and locked restores are accepted; locked solution build, Fable/Vite build and adopted browser conformance are NOT yet evidenced for any cohort (see the #4816 table). Recommendation: #4644's Done when as quoted does not name retained upgrades, so treat them as retained under #4816/#4646 and do not make #4644 wait, unless Root reads the preserve-clause as a gate Root decision; if it gates, supplier is the Templates retained-reference owner (this owner) after a Root selection on #4816
    3 Durable public hosting Explicitly separate (Templates #491); neither gates nor is gated Templates #491 owner; no action for #4644
    4 Holds that survive any acceptance: provider physical disposal Unknown, native UTC trust/skew, the 439+46 holds and the named earlier-three/Python hold Acceptance of #4644 must not release them (Root's acceptance of #4849 already says so) Root
    5 Atlas/documentation currency Owed capture of the earlier-three and full-matrix outcomes and the stale D5 doc text this owner: Templates PR #785 (docs/Atlas, inert)

    Not in #4644's promise (kept visible so they are not mistaken for gaps here): AT/provider/accessibility journeys (#4817), composition (#4818), FourD .5d (#4819), SC2/BAR adoption, OperatingV2 lifecycle-default flip, builds/browser beyond the accepted tail for retained workspaces.

    Net. On the quoted Done when, every named component is accepted; the only open decision is item 2 (does the preserve-retained-upgrades clause gate this parent), plus Root's own parent acceptance and body refresh.

  11. EHotwagner commented on Oct 24, 2026

    @EHotwagner
    ContributorAuthor

    Root acceptance (fdev, Programme/root), 2026-10-24: the #4644 Done when is established.

    The exact compatible public producer set is accepted: SDD 2.4.0, Wizard 0.22.0, Workspace.Template 0.19.3 and Rendering 0.32.3, with registry reconciliation (.github #4808/#4809/#4814 and related).

    Full Wizard and workspace receiver acceptance is accepted:

    This is not a Templates-only result. The hosted AppArmor userns prerequisite is now part of the hosted profile (Templates #773).

    Root rulings

    Closing as completed.

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions