CI / fmt + clippy + test (Linux x86_64) (push) Waiting to run
CI / schema instance validation + consumers (push) Waiting to run
CI / runtime contract (macos-latest) (push) Waiting to run
CI / runtime contract (windows-latest) (push) Waiting to run
ci/woodpecker/push/woodpecker Pipeline was successful
Capture the strict child through launch_strict_capture and classify the outcome before writing anything. In --json mode a control-plane failure now emits exactly one error document with a stable code instead of forwarding bubblewrap stderr and leaving stdout empty; a verified child's valid JSON is forwarded unchanged with its own exit code. Empty, partial or non-JSON child output becomes strict.child_invalid. Route the remaining run --json error paths (mode, grants, missing entry, trace) through the same contract, classify sandbox launch failures with StrictFailureKind so probe/spawn/timeout/resource failures stay distinguishable, and add deterministic routing tests plus forged-marker CLI coverage. Document the decision in ADR-0053 and spec/security.md 1.2. This is step 2 of the CI/security RFC (B02/B03).
36 lines
2.0 KiB
Markdown
36 lines
2.0 KiB
Markdown
# Architecture Decision Records (ADRs)
|
||
|
||
These files record decisions **at the date they were made**. They are not a
|
||
description of current language behavior, implementation state or current
|
||
architecture; read them as decision history.
|
||
|
||
- **Status is not a current-language claim.** A status such as "Accepted" means
|
||
the decision was accepted then, not that its syntax or behavior is still
|
||
active. Superseded ADRs keep their original decision text and date; they are
|
||
not rewritten.
|
||
- **Syntax-role decisions are superseded by
|
||
[ADR-0052](0052-unified-markdown-semantics.md).** The earlier mapping —
|
||
`Strong` executes, `Emph` returns, ordered list is a branch, bullet list is a
|
||
loop, block quote is a call, plus the associated `markdown.inert_executable` /
|
||
`markdown.invalid_construct` role diagnostics — is retired. The current
|
||
language contract is
|
||
[RFC-LANG-0002](../architecture/RFC-LANG-0002-unified-semantics.md), with its
|
||
normative summaries [`spec/mapping.md`](../../spec/mapping.md) and
|
||
[`spec/expression.ebnf`](../../spec/expression.ebnf): `@exec`/`@knowledge`
|
||
heading modes, `Strong`/`Emph`/inline `Code` as interchangeable
|
||
one-statement payload carriers, and `if`/`else`/`while`/`end`/`return`/
|
||
`params` keywords. The implementation is green at `ffd1cc9`; see
|
||
[`docs/STATUS.md`](../STATUS.md).
|
||
- **Infrastructure ADRs** (crates, ABI, capabilities, CLI/JSON contract,
|
||
packaging, security isolation) remain current unless a later ADR supersedes
|
||
them. ADRs with a historical banner keep the banner scoped to the superseded
|
||
part.
|
||
- This index is not a spec. For current architecture see
|
||
[`docs/architecture/CURRENT.md`](../architecture/CURRENT.md); for executed
|
||
status see [`docs/STATUS.md`](../STATUS.md).
|
||
|
||
Files: `0001`–`0050`, plus `0051-byte-exact-http-framing.md` (HTTP framing),
|
||
`0052-unified-markdown-semantics.md` (current language mapping) and
|
||
`0053-strict-child-inspection-and-json-failure-contract.md` (strict CI/JSON
|
||
failure contract).
|