Skip to content

fix: retain Studio fonts and qualify original font-disposal receiver - #728

Merged
EHotwagner merged 8 commits into
mainfrom
routine/svg4709-template-font-ui-20261020
Oct 22, 2026
Merged

EHotwagner merged 8 commits into
mainfrom
routine/svg4709-template-font-ui-20261020

Conversation

@EHotwagner

@EHotwagner EHotwagner commented Oct 20, 2026 •

Copy link
Copy Markdown
Contributor

2026-10-22 update (fdev, accountable owner after takeover). Rendering 0.32.3 is now published from the original producer 4ec6eafb bytes by protected publisher run 39817794639/1 (verified on nuget.org; see FS-GG/.github#4709). Commit 370a3f90 repins the public Rendering consumer axis from 0.32.1 to 0.32.3:

  • the provider pin through bump-rendering-pin.sh, the README and a written PIN HISTORY entry;
  • the SvgFoundation/Studio defaults and the CodecProbe/Tactical refs;
  • six regenerated template lockfiles (version and contentHash lines only);
  • the external-reference public input identity (version, source 4ec6, custody 7dbd, signed raw and lock hashes), its candidate-verifier branch, workflow producer rows and static control;
  • the Release C default-pin assertions;
  • tests, including refusals for the old 0.32.1 pin.

The existing reviewed font-disposal route is unchanged. Merge commit ae856f2e brings the branch up to main 68f101f3 so the routine-eligibility base join holds; it has no conflicts and adds only main's own reviewed commits. The Release C public producer source qualification must now pass its genuine late-font cases against public 0.32.3; they are not waived.

Studio now waits for bounded font readiness or a diagnostic, mounts the genuine OfflineNoto text, and retains or disposes its native FontFace/Blob across replacement, undo/redo, stale completion, errors and unload. Seven maintained browser cases and the current authoring observer preserve strict readiness, mounted text, painted glyph and terminal-disposal assertions. The immutable public Template0.13/Rendering0.31 receiver separately selects its exact historical observer through the closed archive/source/default join.

A distinct font-disposal reusable input binds the original Rendering0.32.3 source4ec6eafbbbf02264db9b0db4780c590abe0bf9cd, run39509314882/attempt1/artifact12305198394, original ZIP/custody and raw release-plan hashes. It builds canonical Studio against the candidate archives and requires eight historical reference cases plus seven strict Studio/font cases in each of Chromium, Firefox and WebKit, then the existing real fifteen-action Orca journey. Reports bind genuine file/describe/leaf identities. This candidate route is not public release acceptance. Historical0.32.1/0.32.2 defaults, tuples and eight-case populations stay unchanged. (Superseded 2026-10-22 by commit 370a3f90: the public default and the public external-reference tuple now point to published 0.32.3. Historical 0.32.1 can be re-qualified only from an older Templates SHA; the 0.32.2 candidate tuple and the eight-case populations are unchanged.)

Preflight remains the default and checks the actual workflow inputs, authenticated archive/source joins and refusal controls before qualification. Only the new route uses a fresh exact SDK10.0.401 root and an explicitly selected sixty-minute hosted limit; historical routes retain thirty-five minutes. Existing actual-YAML/transport/ordering/refusal checks cover this finite change; no custom model or claimed CI savings. Forty-five tests at thirty seconds plus the existing five-minute Orca ceiling leave32.5minutes for setup/build/custody in the new envelope; completion is not guaranteed by that arithmetic.

Validation: independent exact357b445 source review PASS, resolving the preserved209a1ad report-ancestry finding. Closed-environment hermetic controls passed: sixty actual workflow fixtures, all three receipt binders and refusal cases, genuine4-direct+4-nested+7-font report shape, thirteen identity/population/outcome counterexamples, and actual pre-effect shell guards. No real SDK, browser, npm, Node or Orca ran locally. Compilation/browser/Orca require actual hosted qualification. Prior exact1b0596b composition and historical-public qualification passed; its material source qualification remains an original failure (thirteen passed, three late-cancel FontFace cases failed, twenty-one skipped) against published Rendering0.32.1. Those strict failures are not skipped, waived or reclassified by this source change.

Continues FS-GG/.github#4709 under FS-GG/.github#4644 . Full current public-Wizard receiver/runtime/default/lifecycle/bundle, publication/adoption, installed, browser/formal and parent acceptance remain open. No issue closure or reservation release.

The first full retained0.32.3 run39526276388/a1 passed all45 exact single-attempt browser cases, including allseven strict Studio/font cases in each browser. The separate Orca journey failed its original4MiB log safeguard at4,199,889 bytes while navigating toward action15; allfour speech announcements had been observed, but the final activation/journey/full-binding receipts are absent. The original failure and cleanup evidence remain preserved. This is no full AT qualification or publication eligibility.

The reviewed logging repair752a2ac retains genuine speech from the pinned Ubuntu46.1 speech-module call path, its exact source/birth readiness marker, and vendor warning/severe diagnostics. Higher severity cannot bypass reserved speech/readiness marker checks. It delegates to the unchanged vendor formatter and preserves the4MiB cap,300-second original AT budget,15 real keyboard actions, allfour speech assertions,45 browser cases and cleanup/health binders. Official Ubuntu46.1-1ubuntu1 source hashes match allfour hosted source pins. Independent exact source review passed;96 baseline inert controls, nine affected warning/marker controls and exact upstream-AST delegation controls passed. Unaffected controls were not repeated; no actual Orca/browser ran locally. A later normal caller-pin update and independently admitted real qualification remain necessary.

@EHotwagner EHotwagner changed the title Fix Studio Noto readiness and mounted font lifetime fix: retain verified Studio fonts and bind historical observer Oct 20, 2026
@EHotwagner EHotwagner changed the title fix: retain verified Studio fonts and bind historical observer fix: retain Studio fonts and qualify original font-disposal receiver Oct 21, 2026
@EHotwagner

Copy link
Copy Markdown
Contributor Author

fdev 2026-10-22: Rendering 0.32.3 is published. Handing back to this PR's existing owner for the repin and Release C re-run.

FS.GG.Rendering 0.32.3 came from run 39817794639 at protected executor fc2b177e, using the original producer 4ec6eafb archives (artifact 12305198394, custody 7dbd4329…).

Next for this PR's owner (svg_current_public_receiver, under Programme/root):

  • Repin the public Rendering consumer axis from 0.32.1 to 0.32.3 at head 752a2ac1. That includes:
    • providers/rendering.providers.yml via bump-rendering-pin.sh;
    • the SvgFoundation and Studio FsGgSvg*Version defaults and build.sh defaults;
    • the CodecProbe and Tactical FS.GG.UI.Scene references;
    • the version-pinned tests/composition/fable-game/external-reference-public.py and its test.
  • Then re-run "Release C public producer source qualification". It previously failed the three genuine public 0.32.1 late-font cases (13 passed / 3 failed / 21 skipped). Those failures are not waived; they must pass against public 0.32.3.
  • Then do the ordinary review and merge.
  • Workspace.Template publication, registry update, Wizard/SDD default adoption and full public Wizard qualification follow under their own admissions.

No source change, rerun or Status change was made here.

@EHotwagner

Copy link
Copy Markdown
Contributor Author

fdev 2026-10-22: Owner takeover. The previous svg_current_public_receiver owner has shown no activity on this PR since 2026-10-21 01:43Z (head 752a2ac1). At Programme/root direction, fdev takes over as the accountable owner of this same PR and branch. Scope: repin the public Rendering consumer axis from 0.32.1 to 0.32.3 (published by run 39817794639), keep the existing reviewed font-disposal changes, re-run Release C public producer source qualification against public 0.32.3 with the genuine late-font cases unwaived, get independent review of the exact final head, then do the ordinary merge. Publication and default changes stay separately admitted.

EHotwagner and others added 2 commits October 22, 2026 19:39
…-GG/.github#4709)

Rendering 0.32.3 is published from the original producer 4ec6eafb bytes by protected
publisher run 39817794639/1. This moves every shipped public default and its
verification bindings from 0.32.1 to 0.32.3:

- provider pin FS.GG.UI.Template::0.32.3 via scripts/bump-rendering-pin.sh, plus the
  README and a written PIN HISTORY entry;
- SvgFoundation/Studio FsGgSvg*Version and build.sh defaults; CodecProbe.Net/Fable and
  Tactical FS.GG.UI.Scene refs;
- six regenerated template packages.lock.json files (version and contentHash lines
  only, including the opt-in Wasm lock);
- external-reference-public.py: VERSION, source 4ec6, custody 7dbd, signed nuget.org
  raw hashes and lock content hashes for Scene/KeyboardInput/SvgBrowser; the real
  acquisition matches all three against original custody;
- verify-external-reference-candidate.sh public branch, the workflow 'public' producer
  rows and their static control (a historical 0.32.1 source remains a refused mutation);
- verify-svg-preview-c-source.sh Release C default-pin assertions;
- tests: fixtures follow the current default and add refusals for the old 0.32.1 pin.

The existing reviewed font-disposal route and historical fixtures are unchanged.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
…/.github#4709)

Brings the PR up to main 68f101f so the routine-eligibility base join holds.
No conflicts; no content change beyond main's own reviewed commits.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
@EHotwagner
EHotwagner merged commit 2f8d400 into main Oct 22, 2026
26 of 28 checks passed
@EHotwagner
EHotwagner deleted the routine/svg4709-template-font-ui-20261020 branch October 22, 2026 18:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant