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
@@ -4,8 +4,10 @@
|
||||
* The implementation lives in `src/contracts/compatibility.ts`: it is a pure
|
||||
* predicate over release tokens with no application state, and
|
||||
* `src/contracts/release-tokens.ts` needs it, which previously made contracts
|
||||
* import the application layer. This module re-exports it for application-side
|
||||
* and script-side callers.
|
||||
* import the application layer. This module is retained only as a migration
|
||||
* shim; internal callers use src/contracts/compatibility.ts directly.
|
||||
*
|
||||
* @deprecated Import compatibility contracts from ../../contracts/compatibility.ts.
|
||||
*/
|
||||
export {
|
||||
COMPATIBILITY_TUPLE_FIELDS,
|
||||
|
||||
@@ -21,9 +21,23 @@ export type IndexedDbSynchronizationState =
|
||||
| "CONFIRMED";
|
||||
|
||||
export type IndexedDbConnectionStatus =
|
||||
| Readonly<{ kind: "CLOSED"; reason: "NOT_OPENED" | "VERSION_CHANGE" | "FORCED" }>
|
||||
| Readonly<{
|
||||
kind: "CLOSED";
|
||||
/**
|
||||
* NOT_OPENED means the current open attempt has settled without a live
|
||||
* connection. A blocked upgrade may therefore be observed as BLOCKED
|
||||
* while it is waiting, then transition to CLOSED/NOT_OPENED when its
|
||||
* blocked deadline fails closed.
|
||||
*/
|
||||
reason: "NOT_OPENED" | "VERSION_CHANGE" | "FORCED";
|
||||
}>
|
||||
| Readonly<{ kind: "OPENING"; targetVersion: number }>
|
||||
| Readonly<{
|
||||
/**
|
||||
* A live open/upgrade attempt is currently waiting for another
|
||||
* IndexedDB context. BLOCKED is transient and is not the settled state
|
||||
* after the blocked deadline has expired.
|
||||
*/
|
||||
kind: "BLOCKED";
|
||||
currentVersion: number;
|
||||
targetVersion: number;
|
||||
|
||||
@@ -1,13 +1,9 @@
|
||||
/**
|
||||
* The single success/failure carrier used across application input boundaries.
|
||||
* Adapters map technology-specific errors to an application failure before
|
||||
* constructing this value.
|
||||
* Compatibility re-export for application-side callers from older revisions.
|
||||
*
|
||||
* The type itself lives in `src/contracts` because both layers need it and
|
||||
* neither owns it: `src/contracts/server-state.ts` and
|
||||
* `src/contracts/cursor-pagination.ts` reached back into the application layer
|
||||
* for it, which made the ownership of the shared vocabulary ambiguous in both
|
||||
* directions. Contracts is the lower of the two, so the shared shape sits there
|
||||
* and this module re-exports it for every existing application-side importer.
|
||||
* The canonical Result definition is src/contracts/result.ts. New code should
|
||||
* import it from that module so the shared carrier has one public authority.
|
||||
*
|
||||
* @deprecated Import Result from ../contracts/result.ts.
|
||||
*/
|
||||
export type { Result } from "../contracts/result.ts";
|
||||
|
||||
Reference in New Issue
Block a user