Conversation
Author
|
Closing: dream-cycle auto-generated PR, not intended for merge. |
jjohare
added a commit
that referenced
this pull request
Sep 7, 2026
…eipts, honest no-patch gate, Step-19 ledger cells (ADR-2081) Harvest of the 2026-09-01..09-07 dream nights. Four engine defects wasted most of them: - Annexe layout: agentbox sits at workspace/project/agentbox but was extracted at remote_dir/agentbox, so the bridge's ../../../../ path-deps climbed out of the night dir and cargo failed at manifest load every night. `annexe_subpath` now mirrors each repo's canonical depth (target remote_dir/project/agentbox, siblings remote_dir/<name>); candidate reruns reuse the same subpath. - Pipe masking: evaluators ran under bare `bash -c`, so `cargo build | tail -12` reported tail's 0 and a failing build classified PASSED (09-06, PR #4). Both runners now use `bash -o pipefail -c`. Landed together with the layout fix, per PR #4's "do not ship pipefail alone". - Gate: an ACCEPT with no dream-patch graded absent candidate receipts as "never ran" → three harness vetoes → BLOCKED-ENV over green baselines (website 09-07). Candidate receipts are graded only when a candidate tree was applied; no patch is `unproven` → INCONCLUSIVE. - Ledger cell: the finding was the hypothesis truncated at 80 chars, violating the row contract the dream-engine repo now enforces (its PR DreamLab-AI#10). The cell is taken from the report's own Step-19 row, then a self-contained Finding: line. Also: hooks-syntax evaluator checks *.sh with bash -n and exits 1 on failure; 09-05 ACCEPT withdrawn in the ledger (its diff cited paths that never existed); evaluator-status marker rewritten as resolved; cite-existing-adrs discipline. Co-Authored-By: jjohare <github@thedreamlab.uk> Claude-Session: https://claude.ai/code/session_01BMrfpKhzSg2gNzEEupP29P
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Draft PR opened by the dream engine on a GATED ACCEPT night (2026-09-06-agentbox, run
ff350f0dc9e98f1e).Candidate tree
77e53dfaba4ca7f7b48b6a7b068b7721aae9f395was applied in isolation and the required evaluators re-run against it: dream-engine-tests=PASSED, hooks-syntax=PASSED, sovereign-mesh-bridge=PASSED. Witnessce7342117589.A human decides the merge — evaluation is not promotion.
Finding: Given the
sovereign-mesh-bridgeentrypoint pipes cargo throughtail(cd services/nostr-pod-bridge && cargo build --release 2>&1 tail -12) and the annexe clone lacks the sibling path-deps, when cargo aborts with a manifest-resolution error, then the pipeline still exits 0 and the harness recordsoutcome=PASSED exit=0— a pipe-masked false positive that makes the sovereign-mesh required gate vacuous on annexe nights.Gate: ACCEPT upheld: 3 required evaluator(s) passed on candidate tree 77e53dfaba4c