Skip to content

docs(corpus): meld-fused fixture prerequisites (v1.1.0 Track E, deferred)#136

Merged
avrabe merged 1 commit into
mainfrom
release/v1.1.0-pr-meld-fixture
May 19, 2026
Merged

docs(corpus): meld-fused fixture prerequisites (v1.1.0 Track E, deferred)#136
avrabe merged 1 commit into
mainfrom
release/v1.1.0-pr-meld-fixture

Conversation

@avrabe
Copy link
Copy Markdown
Contributor

@avrabe avrabe commented May 19, 2026

Track E agent honestly stopped: meld binary permission denied AND the existing component pair are independent (no cross-memory shape). Ships a README documenting prerequisites; the real fixture is deferred to v1.1.1.

🤖 Generated with Claude Code

….1.0 Track E)

Adds the `meld_fused` workload entry to `scripts/measure_corpus.sh` and a
`tests/corpus/MELD_FUSED_README.md` placeholder documenting exactly what
the v1.0.5 Track 3 byte-wins surface needs: a real `meld fuse` of two
**dependent** components (one importing the other) so the fused core
contains a cross-memory scalar adapter and at least one dedup target.

This is a doc-only PR because the authoring agent could not invoke
`meld` (environment permission restriction). Per CLAUDE.md
"Honesty > shipping something fake": the harness now lists the workload
(it reports `n/a` until the fixture lands), and the README spells out the
toolchain, input requirements, and verification commands so the next
operator can complete the work in minutes.

The existing single-component fixtures (`simple.component.wasm`,
`calc.component.wasm`) are independent (neither imports the other) and
therefore cannot produce the cross-memory adapter shape Track 3 Tier-1.1
targets — that's why Track 3 fired byte-neutral on the v1.0.5 corpus.

Implements: TASK-corpus-meld-fixture
Refs: #132 (Track 3 passes), 0424b7e (component-aware harness)

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
@avrabe avrabe merged commit d19e678 into main May 19, 2026
9 of 19 checks passed
@avrabe avrabe deleted the release/v1.1.0-pr-meld-fixture branch May 19, 2026 18:40
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.

1 participant