chore: sync the frontend template from 5434760 to ebea300
Carries 21 template commits: the shared IndexedDB connection/transaction
kernel and the four runtimes moved onto it, the adapter barrel boundary and
the architecture rule that enforces it, the feature adapter contribution
model, `feature-http-binding`, the split of several oversized test files,
and the release identity now derived from the package name.
Product identity is unchanged. The three hard-coded `tech-log-frontend/…`
verifier ids are gone because the template derives them from the package
name and this package is `tech-log-frontend`.
Two decisions worth naming. The platform HTTP executor is the template's
verbatim — it now takes the installed contract so a feature's types flow
through the binding — and TechLog's four gateways, which address operations
by id, reach it through one adapter at the composition root instead of being
rewritten here. And the three derived CI baselines were recomputed from the
merged `config/ci/gates.json` rather than taken from either side: 94 command
definitions, 106 references, 141 artifacts, gate shape `629e5898…`. The
method was checked by first reproducing the pre-merge values from the
pre-merge file.
Verified here: types, lint, architecture, adapter inventory, CI contract,
design system, diagnostics, remediation ledger, browser security and build
all pass; 1789 unit, 152 component, 415 TechLog, 102 integration, 19
reference-feature, 17 recipe and 7 contract tests pass. Five gates stay
red and every one was reproduced at b297d65 first: `check:i18n`,
`check:registries`, `test:runtime-schema`, `verify:documentation` and
`test:sample-removal`.
Full decision record, including what was deliberately not carried and the
five open follow-ups, in `docs/operations/template-sync-2026-09-21.md`.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This commit is contained in:
co-authored by
Claude Opus 5
parent
b297d659f5
commit
afde2b1da1
@@ -15,14 +15,37 @@ type Equal<Left, Right> =
|
||||
: false;
|
||||
type Expect<Value extends true> = Value;
|
||||
|
||||
type RequiredKeys<Value> = {
|
||||
[Key in keyof Value]-?: Record<never, never> extends Pick<Value, Key>
|
||||
? never
|
||||
: Key;
|
||||
}[keyof Value];
|
||||
|
||||
type InstalledInputs = ReturnType<typeof createInstalledFeatureInputs>;
|
||||
type _InstalledIdsAreExact = Expect<
|
||||
Equal<keyof InstalledInputs, "reference-feature" | "tech-log">
|
||||
|
||||
/**
|
||||
* Template sync (ebea300). The composed map became
|
||||
* `Partial<ApplicationFeatureInputs>` upstream, and the template's new
|
||||
* local-draft demonstration feature declares a third key, so `keyof` no longer
|
||||
* says which features a build installs — every declared feature is a key,
|
||||
* present or not. What this product needs held is the split itself: TechLog is
|
||||
* its own domain and is always composed, and a manifest-governed feature stays
|
||||
* optional because a build may narrow it out.
|
||||
*/
|
||||
type _TechLogIsAlwaysInstalled = Expect<
|
||||
Equal<RequiredKeys<InstalledInputs>, "tech-log">
|
||||
>;
|
||||
type _ReferenceFeatureStaysOptional = Expect<
|
||||
Equal<
|
||||
"reference-feature" extends RequiredKeys<InstalledInputs> ? true : false,
|
||||
false
|
||||
>
|
||||
>;
|
||||
type _TechLogRegistryValueIsExact = Expect<
|
||||
Equal<ApplicationFeatureInputs["tech-log"], TechLogFeatureInput>
|
||||
>;
|
||||
void (0 as unknown as _InstalledIdsAreExact);
|
||||
void (0 as unknown as _TechLogIsAlwaysInstalled);
|
||||
void (0 as unknown as _ReferenceFeatureStaysOptional);
|
||||
void (0 as unknown as _TechLogRegistryValueIsExact);
|
||||
|
||||
function inputOf(document: WorkingCopy) {
|
||||
@@ -40,6 +63,14 @@ function installedInputs(
|
||||
return createInstalledFeatureInputs({
|
||||
studioSource,
|
||||
publicSource,
|
||||
// Template sync (ebea300). The platform capability the manifest-governed
|
||||
// contributions declare in `needs`. Composition builds the reference
|
||||
// feature's gateway from it and never calls it here.
|
||||
http: {
|
||||
async execute() {
|
||||
throw new Error("platform executor is not used by composition tests");
|
||||
},
|
||||
},
|
||||
contractOperations: {
|
||||
async execute() {
|
||||
throw new Error("reference executor is not used by composition tests");
|
||||
|
||||
Reference in New Issue
Block a user