Skip to content

compiler-parity: golden-snapshot test coverage for self-hosted dream.config.json - #9

Closed
jjohare wants to merge 1 commit into
mainfrom
dream/2026-08-15-compiler-parity
Closed

jjohare wants to merge 1 commit into
mainfrom
dream/2026-08-15-compiler-parity

Conversation

@jjohare

@jjohare jjohare commented Aug 16, 2026

Copy link
Copy Markdown
Contributor

Dreaming work preserved from the migration off ruvnet/dream-machine (was upstream PR #11). Recreated here as a draft. Adds golden-snapshot coverage — note this branch is the reason the Tier-B compiled-prompt rename was deferred (it would conflict).

🤖 Generated by Claude Code

…ig.json

Nightly Dream Cycle, 2026-08-15. DEEP=compiler-parity, SCAN=config-schema,golden-snapshots.
Issue #10.

Every existing @dream-machine/compile test exercised a synthetic metaharness
fixture; nothing validated or golden-snapshotted this repo's own real,
committed dream.config.json - the exact file this repo's own nightly
automation reads. Adds a test block that reads the real config, validates
it, asserts deterministic compilation, and snapshots the output.

npm test: 96 -> 100 passed (+4 new, 0 regressions). Lint clean.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Hbv1bXrjNeU3682gQf8XkS
@jjohare

jjohare commented Aug 16, 2026

Copy link
Copy Markdown
Contributor Author

Dreaming cycle integrated into main: test in 4ab5b10 (self-hosted golden snapshot, regenerated against main's current compiler), ledger row in e8088d9. Closing; work is on main.

@jjohare jjohare closed this Aug 16, 2026
@jjohare
jjohare deleted the dream/2026-08-15-compiler-parity branch August 16, 2026 09:34
jjohare added a commit that referenced this pull request Aug 28, 2026
Ledger: record terminal fates for #7/#9 and upstream-consolidated #11/#15
(judgment-broker queue on the agentbox console showed them pending forever);
rewrite Issue/PR cells as owner/repo#N where the artefact lives upstream.
Config: repo slug was still ruvnet/dream-machine — now DreamLab-AI/dream-engine;
autoMerge false to match the estate's human-merge-gate discipline.

Co-Authored-By: jjohare <github@thedreamlab.uk>
Claude-Session: https://claude.ai/code/session_01CYRHUhQ53eaVvgtCNyyEHW
jjohare added a commit that referenced this pull request Sep 7, 2026
An operator row, not a night: no hypothesis was tested and no evaluator ran,
so the verdict is INCONCLUSIVE and the witness is "operator" rather than a
computed triple — the same shape as the 2026-08-28 fate-reconciliation row.

The fate is recorded as #11:MERGED although GitHub shows the PR closed. The
ledger's fate vocabulary tracks whether the change landed, not the button
pressed: #11's content is on main, corrected. That follows the 08-28
precedent, which recorded #7/#9 as MERGED after they were consolidated by
other means.

The finding reads "guard in verify-entrypoint" rather than "wired into" only
because the latter is 84 characters and the row contract caps findings at 80.

npm test 149 of 149, row contract included.

Co-Authored-By: jjohare <github@thedreamlab.uk>
Claude-Session: https://claude.ai/code/session_01EzN6LxAjkxypXeZ3fTQhz8
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants