chore(lattice): backfill pipe()/middleware()/staticSite() records#158
Merged
Conversation
Closes the lattice gap surfaced during the reconcile: the v4.1 Node convenience adapters (commit e395019, PR #129, closing #126/#127) had no requirement or implementation records. - REQ-CORE-008 — one requirement covering pipe()/middleware()/staticSite() as opt-in layers over the pure fetch() primitive. derives_from THX-PURE-FETCH, THX-CORE-VALUE, THX-TYPED-ERRORS; depends_on REQ-CORE-004; verified. - IMP-CORE-006 — implementation record (src/index.ts seams, examples, test/pipe.test.ts + test/static-site.test.ts, smoke gate). - Wired the fetchWeb records as siblings: REQ-CORE-007 extends REQ-CORE-008 and IMP-CORE-005 extends IMP-CORE-006 (fetchWeb is the Web analog of pipe()/middleware(), per its JSDoc). lattice lint/drift clean, health PASS. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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
1 participant
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.
Closes the lattice gap surfaced during the reconcile (#157): the v4.1 Node convenience adapters had no requirement or implementation records, even though
fetchWeb()'s JSDoc references them as its Node-side siblings.New nodes
pipe()/middleware()/staticSite()as opt-in layers over the purefetch()primitive (they shipped together in commite395019, PR feat: v4.1 usability layer over the pure fetch() core #129, closing Add pipe() / middleware() convenience adapter over fetch() #126/Add staticSite() — S3 static website hosting as an opt-in layer #127). Recovers v3's one-call ergonomics without the empty-200 lie, plus S3 static-website semantics.derives_fromTHX-PURE-FETCH, THX-CORE-VALUE, THX-TYPED-ERRORS;depends_onREQ-CORE-004; resolved verified.src/index.tsseams (fetchKey()/writeBody()/onHandlerError()),src/types.tsRequestHandler, both examples,test/pipe.test.ts+test/static-site.test.ts, and the smoke gate.Edges
Wired the fetchWeb records as siblings via
extends: REQ-CORE-007 → REQ-CORE-008 and IMP-CORE-005 → IMP-CORE-006 (fetchWeb extends the Node convenience-layer pattern to Web-standard runtimes).Verification
lattice lint0 issues,lattice drift0,lattice healthPASS. Now 17 requirements / 13 implementations, 0 orphaned.Judgment calls (confirm if you disagree)
fetchWeb()got a single REQ/IMP.extendsfrom the newer fetchWeb records → the earlier pipe/middleware records (no dedicated "sibling" edge type exists). Reversible if you'd prefer the other direction.🤖 Generated with Claude Code