promote dev → stage: chain-of-custody repair #168

Merged

will.anderson merged 6 commits from dev into stage 2026-08-17 16:05:34 +00:00

Conversation 0 Commits 6 Files Changed 3

+144 -1

6 Commits

Author	SHA1	Message	Date
will.anderson	44e2e17973	Merge pull request 'repair a broken chain link: rerun cycle 18 rather than reconstruct it' (#167) from experiment/async-future-replication into dev	2026-08-17 16:05:02 +00:00
bigmerge	511db25230	rerun cycle 18 rather than reconstruct it ... The async/future measurements were produced by a C stub in /tmp, and that artifact was destroyed when the session worktrees were removed. The log then asserted results with nothing behind them -- a claim inside an evidence record, which is exactly what turns a chain of custody into a pile. Rerun, not reconstructed. Rebuilding the missing file would have been a fabrication with a fresh timestamp; rerunning produces new evidence with its own. lang/tests/integration/fixtures/future.c the future, as a tagged heap object lang/tests/integration/async_future.sh the harness, 6/6 ok unbound: synchronous, correct result ok unbound: el_await on a non-future passes through, no crash ok bound: does not crash ok bound: the awaited result is correct ok bound: the caller continues BEFORE the body finishes ok bound: wrap returns in <10ms while the body takes 50ms LABELLED AS A REPLICATION. The outcomes were already known when this harness was written, so its expectations are NOT predictions committed in advance. Its evidentiary value is that a third party can reproduce it, not that it was called ahead of time. Recording it as anything stronger would corrupt the record it is meant to repair. The fixture also carries the P5 defect and its fix in a comment: the first el_await dereferenced ->magic off an unvalidated slot and SIGSEGV'd on the unbound path, sixty seconds after the same defect was diagnosed elsewhere in the runtime.	2026-08-17 11:03:59 -05:00
will.anderson	e9eac46be1	Merge pull request 'promote stage → main: iteration-1 (the compiler stops adjudicating)' (#166) from stage into main	2026-08-17 15:57:06 +00:00
will.anderson	c23c5112a7	Merge pull request 'el: native @route dispatch + multi-decorator stacking in modular compiler' (#93) from feat/el-route-decorators into main	2026-08-15 23:23:23 +00:00
will.anderson	b40af4a5f3	Merge pull request 'promote stage -> main: transduce unification + HNSW + ggml adapter + reconciliation (2026-08-15)' (#120) from stage into main	2026-08-15 22:37:50 +00:00
will.anderson	8c94d92033	el: native @route dispatch + multi-decorator stacking in modular compiler ... Port the @route decorator from the bootstrap prototype into the production modular compiler (parser + streaming codegen), and generalize single decorators to a stacked list so a handler can be both @route and a VBD role (@manager/@engine/@accessor). The dispatcher is synthesized from a token pre-scan (survives the streaming backend's per-fn AST discard, works for library modules) and emitted specificity-sorted so overlapping prefixes never shadow by source order. Supports method lists ("GET|POST"), "ANY", and suffix/compound matchers. Inert on all non-@route code (byte-identical C).	2026-08-10 16:11:15 -05:00