Skip to content

chore(scripts): route-envelope ledger note names the enveloped-refusal relay #28013

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
objectstack-fleet merged 1 commit into from
Oct 30, 2026
Merged

chore(scripts): route-envelope ledger note names the enveloped-refusal relay #28013

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 3 additions & 2 deletions scripts/check-route-envelope.mjs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -975,10 +975,11 @@ const DISPATCHER_DOMAINS = {
// carry the TARGET's credential-rotation headers (`Set-Cookie` lines,
// `set-auth-token`, `set-admin-session-token`) — neither `deps.success` nor
// `deps.error` takes headers, so each spreads the helper's own envelope and
// adds `headers`.
// adds `headers` (since #27738 an enveloped non-2xx refusal is built by
// `apiErrorResponse`, which takes none either, and is spread the same way).
'actions.ts': {
handBuilt: 3,
note: 'one 405 for every verb but POST, which must carry an `Allow:` header (`deps.error` takes none); and the two answers of the same-origin api forward — the 2xx relay (`deps.success` spread) and the non-2xx relay (`deps.error` spread) — which must carry the target\'s Set-Cookie / set-auth-token / set-admin-session-token headers (neither helper takes any); every body is the helper\'s own declared envelope',
note: 'one 405 for every verb but POST, which must carry an `Allow:` header (`deps.error` takes none); and the two answers of the same-origin api forward — the 2xx relay (`deps.success` spread) and the non-2xx relay (`apiErrorResponse` for an enveloped refusal, else `deps.error`, spread) — which must carry the target\'s Set-Cookie / set-auth-token / set-admin-session-token headers (neither helper takes any); every body is the helper\'s own declared envelope',
},
// [#12160] Not a domain either — the ADR-0126 §5 activation write-authority
// gates, shared by the `/automation` toggle door, the `/actions` activation
Expand Down
Loading