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

2026-08-17T16:05:20Z

will.anderson commented

2026-08-17 16:05:20 +00:00

Carries PR #167 — the cycle 18 artifact rerun and committed to the repository.

will.anderson added 6 commits 2026-08-17 16:05:22 +00:00

el: native @route dispatch + multi-decorator stacking in modular compiler

El SDK Release / build-and-release (pull_request) Failing after 11m40s

Details

8c94d92033

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).

Merge pull request 'promote stage -> main: transduce unification + HNSW + ggml adapter + reconciliation (2026-08-15)' (#120 ) from stage into main

El SDK Release / build-and-release (push) Failing after 44s

Details

b40af4a5f3

Merge pull request 'el: native @route dispatch + multi-decorator stacking in modular compiler' (#93 ) from feat/el-route-decorators into main

El SDK Release / build-and-release (push) Failing after 14m37s

Details

c23c5112a7

Merge pull request 'promote stage → main: iteration-1 (the compiler stops adjudicating)' (#166 ) from stage into main

El SDK Release / build-and-release (push) Failing after 11m31s

Details

e9eac46be1

rerun cycle 18 rather than reconstruct it

El SDK CI - dev / build-and-test (pull_request) Failing after 14m31s

Details

511db25230

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.

Merge pull request 'repair a broken chain link: rerun cycle 18 rather than reconstruct it' (#167 ) from experiment/async-future-replication into dev

El SDK CI - stage / build-and-test (pull_request) Failing after 27s

Details

El SDK CI - dev / build-and-test (push) Failing after 14m1s

Details

44e2e17973

will.anderson merged commit 4aadd9300e into stage

2026-08-17 16:05:34 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: neuron-technologies/el#168