chore: sync the frontend template from a0fbafb to 5434760
Carries eight template commits: the provider sandbox actually running, release
admission to a named environment, the product feature manifest with its runtime
kill switch, architecture and documentation rules that match what is enforced,
the removability fixtures, and the browser, visual and performance evidence.
Product identity is unchanged. `package.json` keeps `tech-log-frontend` and the
catalog keeps the Tech Log naming; the home page was not in the delta. The
visual baselines are this product's own — the template's were excluded from the
transplant and these were regenerated here, where the only difference is the
platform overview's new product-feature section.
What this repository gains operationally: `config/runtime/{local,development,
staging,production}.json` with `FE-GATE-027` refusing an artifact whose runtime
document does not match the environment it is being admitted to, and
`FEATURE_OVERRIDES` for taking an installed feature out of service without a
rebuild.
Verified here: eight gates green, build green, visual 5/5, and 1,858 of 1,859
tests in the suites that do not need a sandbox — the one failure passes in
isolation and is a jsdom lazy-chunk timeout under parallel load. The provider
suites cannot run on this machine at all: `kernel.apparmor_restrict_unprivileged
_userns=1` makes `bwrap --unshare-net` fail, reproducible without any code from
either repository.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
co-authored by
Claude Opus 5
parent
325a2a0843
commit
bdee07a93b
@@ -242,6 +242,42 @@ describe("presigned transfer", () => {
|
||||
);
|
||||
});
|
||||
|
||||
it("answers a refused capability envelope with a re-issuable recovery", async () => {
|
||||
// BT-PRE-04. A capability document the adapter will not accept is closed as
|
||||
// `POLICY_REJECTED`, and the caller's only way forward is a new capability.
|
||||
// `NONE` said there was nothing to be done, which contradicted both the
|
||||
// design record for an unsupported protocol and the vault, which already
|
||||
// answers `REISSUE_CAPABILITY` for the same class of refusal.
|
||||
for (const [label, overrides] of [
|
||||
["unknown protocol", { protocol: "PRESIGNED_TRANSFER_V2" }],
|
||||
["missing protocol", { protocol: undefined }],
|
||||
] as const) {
|
||||
const bytes = new Uint8Array([1, 2, 3]);
|
||||
const payload: Record<string, unknown> = {
|
||||
...downloadCapabilityPayload(bytes),
|
||||
...overrides,
|
||||
};
|
||||
if (overrides.protocol === undefined) delete payload["protocol"];
|
||||
const fetcher = vi.fn(async () => jsonResponse(payload)) as unknown as typeof fetch;
|
||||
const { provider } = createHarness({ fetcher });
|
||||
|
||||
expect(
|
||||
await provider.issueDownload({
|
||||
resourceId: "resource-1",
|
||||
signal: new AbortController().signal,
|
||||
}),
|
||||
label,
|
||||
).toMatchObject({
|
||||
ok: false,
|
||||
error: {
|
||||
code: "POLICY_REJECTED",
|
||||
retryable: false,
|
||||
recovery: "REISSUE_CAPABILITY",
|
||||
},
|
||||
});
|
||||
}
|
||||
});
|
||||
|
||||
it("keeps URL and headers adapter-private and streams bounded verified chunks", async () => {
|
||||
const bytes = new Uint8Array([1, 2, 3, 4, 5]);
|
||||
const payload = downloadCapabilityPayload(bytes);
|
||||
|
||||
Reference in New Issue
Block a user