31 KiB
Shared Technical-Light Theme Implementation Plan
For Codex: REQUIRED SUB-SKILL: Use
executeplanto implement this plan task-by-task.
Goal: Make readable state text, labeled fields, complete accent states, focus, busy feedback and reusable interaction recipes consistent across every sister UI before local visual migration.
Architecture: Evolve the existing Razor Class Library; do not replace its shell or copy mockup CSS into applications. Add compatible component parameters and semantic text tokens, retaining existing signal colors and SSR behavior. Publish one reviewed package and migrate consumers against the same contract.
Tech Stack: .NET 10 Razor Class Library, Bootstrap 5 consumer utilities, CSS custom properties, IBM Plex, xUnit 2.9.3, bUnit 2.7.2 (BunitContext / Render), GB-validated AngleSharp family (pre-GB direct pin 1.5.0), existing Node script tests.
Required testing prerequisite
Complete bUnit standardization and close GB before any task in this chapter, including local fixes and candidate UI pilots. All bUnit snippets below use the post-GB BunitContext / Render / AddAuthorization API; their inherited helpers must be migrated in GB. Preserve framework HtmlRenderer methods and xUnit runner APIs where used. Non-bUnit runtimes retain their existing harnesses, but their UI work also waits for the family gate. Old package pins are discovery baselines, not targets for this chapter.
Baseline and boundaries
- Repository:
/Users/dohertj2/Desktop/scadaproj; library root:/Users/dohertj2/Desktop/scadaproj/ZB.MOM.WW.Theme. - Current library source: 0.5.3 in
Directory.Build.props. The parent repository advanced after the review only in telemetry/observability files; Theme source did not change. - Inputs: shared recommendations, Theme report, component concept, contrast evidence.
- Read the master plan before executing. G1 is this chapter's release gate; all named versions in dependent chapters remain placeholders until release decisions are recorded.
- Preserve Plex, warm paper, white surfaces, existing 8px panels, 220px desktop rail, native mobile disclosure, nav state persistence, current button class composition,
ScrollNav, and statelessTreeTablebehavior. - This chapter plans changes. Tests, builds, package publication and deployments have not been run as part of planning.
Paths below are relative to the library root unless prefixed with /Users/. All shell blocks state their working directory. New test files are proposed; existing files have been checked. Every step is a separate small action; repeat a step per component family rather than combining the family into an unreviewable edit.
Contract supplied at G1
| Contract | Exact decision |
|---|---|
| Text inks | Add --ok-ink:#236f34, --bad-ink:#b42121, --idle-ink:#535d66; set existing --warn-ink:#855000, --ink-faint:#626970 |
| Signal colors | Retain --ok, --warn, --bad, --idle for dots/stripes/charts; route small text through semantic inks |
| Accent | Keep Accent; add optional AccentDeep, AccentTint, AccentBorder, AccentFocus; emit --accent-deep, --accent-tint, --accent-border, --accent-focus only when supplied |
| Semantic info | Add --info-ink with the existing blue deep value; informational status remains deliberately independent of brand accent |
| Fields | Optional For, HintId, ErrorId on TechField; caller controls input id, aria-describedby, aria-invalid; no guessing an arbitrary ChildContent control |
| Busy action | Optional BusyText; aria-busy reflects Busy; keep Type, disabled and attribute/class behavior intact; caller owns a separate outcome status region |
| Focus/motion | Visible focus for all shared interactive controls; reduced motion shows final content immediately and retains text state |
| Recipes | Labeled filter, table sort/disclosure, empty/error/freshness and managed confirmation examples; domain behavior remains local |
| Version | THEME_VERSION selected under the documented token compatibility policy; never publish over 0.5.3 or assume a minor version |
A full family dark theme is not a prerequisite for G1. Preserve each application's explicitly supported scheme and require new semantic aliases there; do not claim family dark support from one application's overrides. Record additional dark-theme expansion as separate work.
Task TH-01: Capture post-GB baseline and Theme compatibility decisions (DS-06)
Files:
- Read:
Directory.Build.props,Directory.Packages.props,README.md,src/ZB.MOM.WW.Theme/Components/ThemeShell.razor. - Create:
/Users/dohertj2/Desktop/scadaproj/components/ui-theme/RELEASE-DECISION.md. - Modify later:
/Users/dohertj2/Desktop/scadaproj/components/ui-theme/GAPS.md.
-
Record branch, commit and existing changes; use a suitable checkout/branch with prefix
codex/without overwriting unrelated work. Re-read applicable repository instructions. -
Establish the unchanged baseline from library root:
dotnet build ZB.MOM.WW.Theme.slnx -c Release dotnet test tests/ZB.MOM.WW.Theme.Tests/ZB.MOM.WW.Theme.Tests.csproj -c Release --no-buildExpected: existing build/tests pass, warnings remain errors. Record actual counts; do not copy historical totals. If restore/feed failure occurs, record it as infrastructure failure, not a test failure.
-
Record actual consumer pins and transitive resolution using the master adoption matrix. Inspect authored
.btnusages as well as local sizing definitions: a selector can exist but match no consumer markup. -
State that current policy treats token changes as breaking. Select a version consistent with that policy; document any deliberate policy revision before assigning
THEME_VERSION. Component parameter additions alone do not justify silently overriding token policy. -
Record light/dark scheme support, default/green/teal/purple accent inputs and a zero-domain-behavior-change boundary.
-
Commit only the release-decision record:
docs(theme): define accessible theme release contract.
Exit: GB is closed, the post-migration baseline and explicit Theme compatibility decision exist; no release has yet occurred.
Task TH-02: Introduce readable semantic text inks (DS-01)
Files:
- Modify:
src/ZB.MOM.WW.Theme/wwwroot/css/theme.cssandsrc/ZB.MOM.WW.Theme/wwwroot/css/layout.css. - Create test:
tests/ZB.MOM.WW.Theme.Tests/ThemeTokenContrastTests.cs. - Modify existing test:
tests/ZB.MOM.WW.Theme.Tests/StaticAssetsTests.cs(replace the old--idletext assertion with--idle-ink; keep background and asset protections). - Modify docs:
/Users/dohertj2/Desktop/scadaproj/components/ui-theme/spec/DESIGN-TOKENS.md.
-
Add a behavioral token-pair contrast test. Complete starting test class:
using System.Globalization; using System.Text.RegularExpressions; namespace ZB.MOM.WW.Theme.Tests; public sealed class ThemeTokenContrastTests { private static string Css => File.ReadAllText(Path.GetFullPath(Path.Combine( AppContext.BaseDirectory, "..", "..", "..", "..", "..", "src", "ZB.MOM.WW.Theme", "wwwroot", "css", "theme.css"))); private static string Token(string name) { var match = Regex.Match(Css, Regex.Escape(name) + @"\s*:\s*(#[0-9a-fA-F]{6})\s*;"); Assert.True(match.Success, $"Missing hex token {name}"); return match.Groups[1].Value; } private static double Luminance(string hex) { double Channel(int start) { var value = int.Parse(hex.Substring(start, 2), NumberStyles.HexNumber, CultureInfo.InvariantCulture) / 255d; return value <= .04045 ? value / 12.92 : Math.Pow((value + .055) / 1.055, 2.4); } return .2126 * Channel(1) + .7152 * Channel(3) + .0722 * Channel(5); } private static double Ratio(string a, string b) { var x = Luminance(a); var y = Luminance(b); return (Math.Max(x, y) + .05) / (Math.Min(x, y) + .05); } [Theory] [InlineData("--ok-ink", "--ok-bg")] [InlineData("--warn-ink", "--warn-bg")] [InlineData("--bad-ink", "--bad-bg")] [InlineData("--idle-ink", "--idle-bg")] [InlineData("--ink-faint", "--paper")] [InlineData("--ink-faint", "--card")] public void Small_text_pairs_meet_AA(string foreground, string background) => Assert.True(Ratio(Token(foreground), Token(background)) >= 4.5); [Fact] public void Contrast_reference_is_black_on_white() => Assert.Equal(21d, Ratio("#000000", "#ffffff"), 6); } -
Run from library root:
dotnet test tests/ZB.MOM.WW.Theme.Tests/ZB.MOM.WW.Theme.Tests.csproj --filter FullyQualifiedName~ThemeTokenContrastTestsExpected red: missing semantic tokens and inadequate current warning/faint contrast; the black/white reference passes.
-
Add/update only the token values in the G1 contract. Retain signal-color values.
-
Migrate foreground declarations, one group per edit:
.chip-*,.s-*,.conn-pill[data-state],.kv .v.*, aggregate caution/alert/success text and notices. Do not replace dot/stripe/background colors mechanically. Use--info-inkfor semantic informational text. Keep identifiers and state labels textual. -
Update the old idle-foreground assertion and token documentation to express the new semantic contract. Do not “fix” the failing contrast test by lowering its threshold.
-
Run the targeted tests, then the full Theme test project. Expected green. In a real consumer, measure computed chip/notice/value text including opacity; token math alone cannot prove selector application.
-
Commit:
fix(theme): make shared status and supporting text readable.
Acceptance: current backgrounds plus semantic text pairs are ≥4.5:1; no brighter signal colors are lost; no CSS literals outside the token authority are added. Test coverage verifies contrast behavior, not a snapshot of every CSS declaration.
Task TH-03: Associate TechField labels and descriptions (DS-02)
Files:
- Modify:
src/ZB.MOM.WW.Theme/Components/TechField.razor. - Create test:
tests/ZB.MOM.WW.Theme.Tests/TechFieldAssociationTests.cs. - Retain:
tests/ZB.MOM.WW.Theme.Tests/CommonControlsTests.cs. - Modify:
README.md(caller ID/ARIA usage).
-
Add this red bUnit case under
TechFieldAssociationTests : BunitContext:[Fact] public void Field_connects_label_hint_and_error_to_the_callers_input() { var cut = Render<TechField>(p => p .Add(x => x.Label, "Name").Add(x => x.For, "secret-name") .Add(x => x.Hint, "Use a stable name").Add(x => x.HintId, "name-hint") .Add(x => x.Error, "Name is required").Add(x => x.ErrorId, "name-error") .AddChildContent("<input id='secret-name' aria-describedby='name-hint name-error' aria-invalid='true'>")); Assert.Equal("secret-name", cut.Find("label").GetAttribute("for")); Assert.Equal("Use a stable name", cut.Find("#name-hint").TextContent); Assert.Equal("Name is required", cut.Find("#name-error").TextContent); Assert.Equal("name-hint name-error", cut.Find("input").GetAttribute("aria-describedby")); } -
Run from library root:
dotnet test tests/ZB.MOM.WW.Theme.Tests/ZB.MOM.WW.Theme.Tests.csproj --filter FullyQualifiedName~TechFieldAssociationTests. Expected red initially: missing new parameters. -
Add nullable string parameters
For,HintId,ErrorId; renderfor="@For",id="@HintId",id="@ErrorId"on the existing label/hint/error. Emit hint/error only when their content exists. Do not insert nested labels or rewrite arbitrary ChildContent. -
Add two related tests: no error node when Error is absent; two fields with explicitly different IDs remain independent. Old consumers with no new parameters still render without exceptions.
-
Document exact consumer usage:
<TechField Label="Name" For="secret-name" Hint="Use a stable name" HintId="name-hint"> <input id="secret-name" aria-describedby="name-hint" class="form-control" /> </TechField>When an error appears, the caller appends its ErrorId to
aria-describedbyand setsaria-invalid; do not include IDs of absent nodes. Use stable per-instance IDs for repeated forms. -
Run targeted then full tests. Browser acceptance: clicking a label focuses its control; a screen reader names the field and reads associated help/error once. Keep focus-on-error and error announcements local to the form.
-
Commit:
feat(theme): associate field labels and descriptions.
Task TH-04: Carry the whole product accent through interaction states (DS-03)
Files:
- Modify:
src/ZB.MOM.WW.Theme/Components/ThemeShell.razor. - Modify:
src/ZB.MOM.WW.Theme/wwwroot/css/theme.css,src/ZB.MOM.WW.Theme/wwwroot/css/layout.css. - Modify test:
tests/ZB.MOM.WW.Theme.Tests/ThemeShellTests.cs. - Modify docs:
README.md,/Users/dohertj2/Desktop/scadaproj/components/ui-theme/spec/DESIGN-TOKENS.md.
-
Add a red render test with
Accent="#2f855a",AccentDeep="#1c6540",AccentTint="#edf5f0",AccentBorder="#bddbc9",AccentFocus="#1c6540"; assert all five intended CSS variables occur on.app-shell. Keep the existing no-accent/no-style and Accent-only tests. -
Run from library root:
dotnet test tests/ZB.MOM.WW.Theme.Tests/ZB.MOM.WW.Theme.Tests.csproj --filter FullyQualifiedName~ThemeShellTests. Expected red: additive parameters missing. -
Add optional parameters and compose only supplied values. Keep
Accentbehavior backward-compatible. Add default--accent-tint,--accent-border,--accent-focus; usevar(--accent-tint)directly in active selectors (or rebind--active-bg:var(--accent-tint)on.app-shell), interactive borders through--accent-border, and focus through--accent-focus. Do not rely on an alias resolved in:rootto pick up a child shell override: inherited custom-property values can already be computed there. Also bind Bootstrap component variables at the actual component scope. Bootstrap.btn-primaryhard-codes its own button colors; changing root--bs-primaryalone does not recolor it. Add--on-accent:#ffffffin the canonical token block, verify each approved accent supports readable white text, and map the primary/ghost components without disturbing button sizing/group seams. Minimum primary mapping:.btn-primary { --bs-btn-color: var(--on-accent); --bs-btn-bg: var(--accent); --bs-btn-border-color: var(--accent); --bs-btn-hover-color: var(--on-accent); --bs-btn-hover-bg: var(--accent-deep); --bs-btn-hover-border-color: var(--accent-deep); --bs-btn-active-color: var(--on-accent); --bs-btn-active-bg: var(--accent-deep); --bs-btn-active-border-color: var(--accent-deep); --bs-btn-disabled-color: var(--on-accent); --bs-btn-disabled-bg: var(--accent); --bs-btn-disabled-border-color: var(--accent); } .btn-link { --bs-btn-color: var(--accent); --bs-btn-hover-color: var(--accent-deep); }Check existing local primary/ghost overrides before deletion. Use the shared visible outline for primary focus and remove an inherited blue-only Bootstrap focus shadow where it conflicts; do not remove all focus feedback. Cover normal/hover/pressed/disabled and selected table actions in the browser computation check.
-
Preserve independent informational blue:
--info-inkand--info-bgare semantic info colors, not automatically product accent. Test actual contrast instead of assuming green/purple substitutions are safe. -
Verify nested subtree scope and a page with no per-product override. Ensure no inline style is emitted when all parameters are absent; no style parameter accepts untrusted remote input.
-
Browser-compare default blue, Historian green, BTDB teal and Overview purple, including hover/active/focus. Assert the actual computed active background equals each supplied tint; checking inline custom-property text alone misses root-scope alias resolution. Record approved exact tint/deep/border values in the adoption matrix.
-
Run the targeted and full tests; commit
feat(theme): support complete product accent states.
Task TH-05: Complete busy feedback without changing disabled semantics (DS-04)
Files:
- Modify:
src/ZB.MOM.WW.Theme/Components/TechButton.razor. - Modify test:
tests/ZB.MOM.WW.Theme.Tests/TechButtonExtensionsTests.cs. - Modify docs:
README.md.
- Add a red test rendering Busy=true/BusyText="Saving changes…"; assert disabled,
aria-busy="true"and visible busy text, then render Busy=false and assert original child label returns. Preserve the existing tests for caller disabled, class composition, Type and click behavior. - Run:
dotnet test tests/ZB.MOM.WW.Theme.Tests/ZB.MOM.WW.Theme.Tests.csproj --filter FullyQualifiedName~TechButtonExtensionsTestsfrom library root. Expected red: missing parameter/state attribute. - Add optional
BusyText; when busy and nonempty show that text, otherwise preserve ChildContent. Render explicitaria-busy; keep spinner decorative. RetainBusy || CallerDisabledand current class merging. - Document a caller-owned, persistent
role="status"region for operation completion/failure. Never put secret values or every polling update in it. Do not attach a global assertive live region to every button. - Run targeted/full tests; browser-check slow success, slow failure, caller-disabled and keyboard focus after completion. Commit
feat(theme): expose accessible busy action state.
Task TH-06: Focus, reduced motion and responsive recipes (DS-04/05)
Files:
- Modify:
src/ZB.MOM.WW.Theme/wwwroot/css/theme.css,src/ZB.MOM.WW.Theme/wwwroot/css/layout.css. - Create docs:
/Users/dohertj2/Desktop/scadaproj/components/ui-theme/spec/INTERACTION-RECIPES.md. - Modify:
README.md.
-
In the two pilot consumers described in the master plan, establish a failing browser observation: an affected custom control lacks a clear focus treatment or a
.riseelement animates with reduced motion. Save the before evidence with the route/commit, not just a CSS grep. -
Add a shared
:focus-visiblerule using--accent-focus, leaving existing stronger specialized focus handling intact. Use an intentional outline width/offset; check clipping inside scroll regions. -
Add
prefers-reduced-motion: reducefor.riseto render the final state immediately; replace pulse with a stable connection state. Avoid a global 0.01ms animation override. -
Document semantic recipes with complete minimal examples: labeled filter and clear action, table caption/headers/scroll region, sortable header button and
aria-sort, true row disclosure button witharia-expanded, empty vs failed vs stale state, and a confirmation focus lifecycle. -
For example, a table action must use the real input path:
<th scope="col" aria-sort="@(_ascending ? "ascending" : "descending")"> <button type="button" @onclick="ToggleSort">Updated (UTC)</button> </th>ToggleSortmust sort the actual displayed dataset and preserve selection. A cursor alone is not sorting; keep domain sorting logic in the consumer. -
Specify the dialog contract: associated heading/description; initial safe focus; Tab/Shift+Tab within visible enabled controls; real DOM keydown event and
preventDefault; safe Escape; inert background; focus return; busy-close rules. Reuse an existing strong implementation for each pilot; nowindow.eventacross asynchronous Blazor interop. A native dialog is allowed only after host/browser suitability is verified. -
Run real-browser checks at 1440×900, 1024×768 and 390×844, actual 200% zoom, keyboard and reduced motion. Test mobile nav both open and closed: content must stay visible, focus reachable, tables scroll internally. No new unit tests merely asserting a CSS declaration.
-
Commit
feat(theme): standardize focus motion and interaction recipes.
Exit: recipes work in two representative host modes. G1 does not require a new generic modal component; extracting one has a separate evidence gate G2.
Task TH-07: Documentation, package contents and local canary (DS-06)
Files:
- Modify:
Directory.Build.props,README.md. - Modify docs:
/Users/dohertj2/Desktop/scadaproj/components/ui-theme/README.md,/Users/dohertj2/Desktop/scadaproj/components/ui-theme/spec/SPEC.md,/Users/dohertj2/Desktop/scadaproj/components/ui-theme/spec/DESIGN-TOKENS.md,/Users/dohertj2/Desktop/scadaproj/components/ui-theme/shared-contract/ZB.MOM.WW.Theme.md,/Users/dohertj2/Desktop/scadaproj/components/ui-theme/GAPS.md. - Create release evidence:
/Users/dohertj2/Desktop/scadaproj/components/ui-theme/releases/THEME_VERSION.md(substitute the actual selected version in the filename). - Read scripts:
build/pack.sh,build/push.sh; do not blindly publish all existing artifacts.
-
Resolve
THEME_VERSIONfrom TH-01, update source version once and correct obsolete “not started,” version, asset and JavaScript statements in adoption docs. Include a parameter migration example and semantic-token migration table. -
Commit reviewed source/version changes before the final package build, verify a clean source tree, and record that exact commit as the package source revision. Documentation-only validation evidence can be committed separately afterward. Run from library root:
dotnet build ZB.MOM.WW.Theme.slnx -c Release dotnet test tests/ZB.MOM.WW.Theme.Tests/ZB.MOM.WW.Theme.Tests.csproj -c Release --no-build ./build/pack.shExpected: clean build, all tests green and exactly the intended version package newly produced. Do not use baseline test totals as a target.
-
Inspect the exact
.nupkgwithunzip -l artifacts/ZB.MOM.WW.Theme.<resolved-version>.nupkg. Expected: DLL, CSS, fonts, nav-state script and correct static-web-assets metadata; no unrelated package. Recordshasum -a 256for that exact artifact. -
Use an isolated local NuGet source to restore that package into Overview and one large consumer pilot (ScadaBridge), without changing deployment credentials or replacing existing production packages.
dotnet restore <explicit-project> --source <local-package-directory> --source <existing-feed>must use existing feed credentials/config and include all other approved configured sources needed for public dependencies; explicit--sourceoptions override source selection. Do not diagnose a missing public dependency as a UI regression after accidentally omitting its approved source. Verify project.assets.json resolves the intended Theme version and one font/CSS authority. -
Complete pilot tests and the master visual matrix. If a pilot failure requires a Theme change, fix/retest that affected task before release; do not hide the failure with local override copies.
-
Commit acceptance documentation:
docs(theme): document and validate the shared UI release. The package must remain the byte-verified output from the clean source/version commit in step 2; do not relabel its source revision with this later evidence-only commit.
Task TH-08: Export canonical static assets for public-feed-only and native consumers (DS-05/06)
Files:
- Create:
build/export-web-assets.pyandbuild/test_export_web_assets.py. - Modify:
README.mdand release evidence. - Output (generated, exact version):
artifacts/technical-light-web-assets.<THEME_VERSION>.zip.
Why: ignitionoee registry explicitly permits only public NuGet dependencies. Do not introduce a private Theme package prerequisite. Perspective needs native JSON styles, not Blazor components. Export from the already validated package bytes, not from a second hand-maintained palette.
-
Write
unittestcases inbuild/test_export_web_assets.pyusing a synthetic input nupkg: byte-for-byte CSS/font parity, correct package ID/version and source hash, complete required asset set, missing-asset refusal, and deterministic repeated export. Assert a changed input CSS byte changes its manifest hash. These are artifact-integrity behavior tests, not CSS declaration snapshots. -
Run from library root:
python3 -m unittest discover -s build -p 'test_export_web_assets.py' -v. Expected red: exporter missing. Keep tests offline; use temporary files and synthetic package fixtures. -
Implement an explicit
--package,--source-revision,--source-tag,--outputCLI using Python standard libraryzipfile,hashlib,json,re,argparse,xml.etree.ElementTree. Read the input package's nuspec; refuse a package ID other thanZB.MOM.WW.Theme. Derive version from nuspec, not the output filename. Refuse missing required static assets; do not silently skip them. -
Copy these package entries to the export root without altering bytes:
Nupkg prefix / entry Export root staticwebassets/css/theme.csscss/theme.cssstaticwebassets/css/layout.csscss/layout.cssstaticwebassets/fonts/ibm-plex-sans-400.woff2fonts/ibm-plex-sans-400.woff2staticwebassets/fonts/ibm-plex-sans-600.woff2fonts/ibm-plex-sans-600.woff2staticwebassets/fonts/ibm-plex-mono-500.woff2fonts/ibm-plex-mono-500.woff2Entry paths above were verified in existing Theme packages. Verify them again for the actual new package. No consumer needs a private-feed restore to use this zip.
-
Generate
tokens.jsonfrom the canonical:rootdeclarations after stripping CSS comments. Use the exact shape{ "schemaVersion": 1, "themeVersion": "<resolved version>", "tokens": { "--paper": "#f4f4f1", "--active-bg": "var(--accent-tint)" } }with every canonical root token in the tokens object. Preserve raw token values and references; include schema version and Theme version. Native consumers select/resolve the semantic tokens they support; do not claim the parser implements arbitrary CSS. Refuse malformed/missing required semantic tokens. -
Generate
manifest.jsonwith this contract (example values are placeholders):{ "schemaVersion": 1, "themeVersion": "<resolved THEME_VERSION>", "sourcePackage": "ZB.MOM.WW.Theme", "sourcePackageSha256": "<actual package sha256>", "sourceRevision": "<actual source commit>", "sourceTag": "<actual release tag or explicit untagged marker>", "files": { "css/theme.css": "<sha256>", "css/layout.css": "<sha256>", "fonts/ibm-plex-sans-400.woff2": "<sha256>", "fonts/ibm-plex-sans-600.woff2": "<sha256>", "fonts/ibm-plex-mono-500.woff2": "<sha256>", "tokens.json": "<sha256>" } }Hash all payload files before serializing the manifest; do not put a self-hash into the manifest. Use stable zip ordering/timestamps so identical inputs produce identical output. Reject path traversal entries and unexpected duplicate required entries when reading the zip.
-
Run the artifact tests green. Generate the export from the exact TH-07 nupkg, passing the recorded source revision/tag; record the export's sha256 beside the package's hash. Independently unpack and recompute every payload hash. Source revision must correspond to the reviewed clean package build; do not fill metadata from a different checkout.
-
For a limited pre-G1 candidate pilot, have registry restore its current public-feed graph unchanged, import the export into
registry/src/Registry.Host/wwwroot/shared-theme/, and validate fonts/CSS/manifest paths in its pilot. It may consumetheme.cssand keep its domain selectors; loadlayout.cssonly where actual matching markup and dependencies have been verified. -
Commit exporter/tests/docs:
build(theme): export versioned canonical web assets. Store/publish the exact zip through the agreed artifact delivery channel; record immutable filename/hash, not a mutable URL alone.
Exit: package and static-export parity are proven. G1 cannot close for the whole family without this export. Registry and Perspective chapters own import/native mapping, not the Theme RCL.
Task TH-09: Publish G1 and govern shared extraction (DS-05/06)
Files: release evidence and the shared adoption matrix in the master plan; consumer version files belong to later chapters.
- After the reviewed package and local canary pass, publish only the exact validated
.nupkgusing the repository's configured feed and existing credential environment. Execution must have package-publication authorization; this planning request does not publish anything. Never repack/reuse an immutable version or push a wildcard containing other packages. - Download that version from the feed independently, compare hash with TH-07, and verify one consumer restores it without the local source. Record actual
THEME_VERSIONand artifact hash. Record the verified TH-08 static export alongside it. This closes G1. - Continue shared Secrets UI and consumer adoption in master order. Hold the exact prior app artifact/package lock for rollback; keep backend schema/protocol behavior unchanged.
- After two completed dialog pilots, compare the duplicated behavior. If they share a stable API, make a separate task/release to extract the helper/component into Theme. Add two-host browser contract tests before switching callers. If not, retain validated local adapters and shared recipes; do not create a speculative abstraction.
- Record G2 (common interaction recipe verified in at least two consumers, with an extraction decision) without making generic extraction a prerequisite for already safe local repairs.
- Commit release evidence:
docs(theme): record release and consumer pilot results.
Finding coverage and exit checklist
| Finding | Tasks | Required evidence |
|---|---|---|
| DS-01 | TH-02, TH-07 | Pair tests + computed-style/state captures |
| DS-02 | TH-03, Secrets caller migration | Rendered label relationships + browser name/focus |
| DS-03 | TH-04, all consumer adoption tasks | Four accent families across default/hover/active/focus |
| DS-04 | TH-05/06 | Busy/disabled tests, keyboard and reduced motion |
| DS-05 | TH-06/08/09 | Two consumer interaction pilots, no domain imports |
| DS-06 | TH-01/07/08/09 | Explicit compatibility/version, hash, restore graph, adoption ledger |
- G1 package immutable and independently verified; exact version resolved.
- Theme full tests and both pilots green; findings tied to actual current source.
- Colors, type, space, borders and state semantics match the shared contract across accents.
- Login remains static POST with host antiforgery and safe return URL; TreeTable ownership unchanged.
- Existing supported dark scheme remains readable; no claim of unsupported family dark behavior.
- Rollback artifact/version identified; no incompatible backend changes bundled.
- Final @impeccable audit evidence and bounded @impeccable polish recorded after implementation.