The preserved catalogue below is complete for its cited revision, not for the current working tree. Static TypeScript AST inspection now finds 59 named declarations (57 previously catalogued). Parameterized declarations count once; these are not runtime test counts. Existing stable IDs, assertion excerpts and immutable source links are retained. Some previously catalogued test bodies also changed; use current source before reproducing a case.
The following additional source declarations were inspected without importing or running tests. Their titles identify test intent; expected behavior must be checked against their assertions and the current Worker handlers.
No application tests, deployment checks or operator scripts were executed for this review. Not run describes this review, not historical results. Existing reserved IDs have been populated, not removed. Source links identify the inspected revision. Plain-English descriptions retain exact technical names where needed to reproduce a case.
B. Purpose and scope
Public information, representation selection, gateway routing and the checked-in OpenAPI contract builder. This review does not assume a hosted OpenAPI document matches the inspected source revision.
The original cases are a curated high-value review. The catalogue below accounts for all 57 named declarations across 13 test files at this revision; this is not complete behavioural coverage. Requirements come from the cited code or contract; existing tests support only what their assertions check. Related wiki protocol/data pages remain reference destinations, not independent implementation evidence.
Responsibilities, related interfaces and dependencies are identified per case. Production credentials, live deployment behaviour and unsupported performance targets are outside scope. Desired requirements and unresolved guarantees are explicitly distinguished from implemented expectations.
Priority describes review risk: Critical protects access or durable state; High protects a core contract or recovery path; Medium covers a narrower operational concern; Low is reserved for low-impact cases. Integration can mean connected handlers/stores under a simulated runtime; it does not necessarily mean live services.
C. Test environment and prerequisites
Prerequisite
Established setup and limitations
Required runtime and tooling
CI selects Node.js 22 and pnpm 12.11.2. The test directory is test/ and no root Vitest configuration was found. test/worker.test.mjs supplies service stand-ins, NODE_CONFIG, an in-memory caches.default and waitUntil tracking. Ajv checks the produced OpenAPI schema in contract tests.
Environment configuration
Use the cited test configuration and per-case environment. Installed dependencies, private test settings and successful setup were not verified by execution.
Service bindings and dependencies
Use a synthetic public origin, display name and description, an empty in-memory cache and controlled Worker responses. Some compatibility checks conditionally read sibling SDK documentation or import sibling Worker source; missing checkouts can skip those portions.
Test databases and storage
In-memory caches.default; no deployed content database or bucket in selected cases.
Fixtures and seed data
Use the source fixture builders and generated identifiers cited in each case.
Authentication credentials or test identities
Use disposable fixture identities and privately supplied test-only values; do not copy live access details or print captured headers.
Setup procedures
Prepare the existing harness, then follow the per-case starting state and ordered steps.
Teardown and environment cleanup
Clear the test cache and restore spies after each case as worker.test.mjs does. Await captured waitUntil work when comparing cache variants. API-generation checks write a generated .wrangler artifact; they are not deployment commands.
The first table lists curated risk cases; the second lists every source declaration. The views overlap and must not be added as distinct runnable tests. Status means implementation status; execution remains Not run.
Test ID
Scenario
Category
Priority
Status
RES-001
Select homepage representations without mixing cached formats
API compatibility; caching
High
Existing automated test
RES-002
Serve the kind catalogue when Corpus is unavailable
Dependency interactions; contract compatibility
High
Existing automated test
RES-003
Separate endpoint syntax routing from identity checks
Authentication boundaries; route validation
Critical
Existing automated test
RES-004
Publish the exact conversation pagination contract
Pagination and ordering; API contract compatibility
High
Existing automated test
RES-005
Represent nonuniform error shapes and operation-specific limits
API and contract compatibility; validation
High
Partially covered
RES-006
Characterise a failed cache lookup before producing a page
Dependency interactions; diagnostics
Medium
Proposed test, not implemented
Complete automated source inventory
Every named source declaration in the test folders is listed below. These entries overlap with the curated scenarios above: they are not additional runnable tests. A parameterized declaration counts once, regardless of how many cases it registers. Conditional tests are included; all execution results remain Not run.
Cases follow the reusable test-case template. Additional explicit fields identify category, code path, command, independent statuses, limitations and follow-up. Expectations were not observed by running tests in this review.
RES-001 — Select homepage representations without mixing cached formats
Field
Specification or observation
1. Test ID and name
RES-001 — Select homepage representations without mixing cached formats
2. Requirement or guarantee
Code-confirmed: homepage selection honours Accept quality/exclusion values and keeps its cached HTML and Markdown responses distinct.
3. Purpose and risk addressed
A client receives the wrong representation from a previously cached request.
4. Priority
High
5. Test type
Integration
6. Preconditions
Use the worker-test NODE_CONFIG and in-memory cache with pending waitUntil promises collected.
7. Input and test data
GET / with no Accept, */*, text/markdown;q=0, text/html, text/markdown;q=0.9, text/html;q=0.8, text/html;q=0, */*, and application/json.
8. Execution steps
1. Run the variants against the same test cache. 2. Await background cache work after each request. 3. Compare status, Content-Type and Vary.
9. Expected HTTP status, where applicable
200 for the first five variants; 406 for application/json.
10. Expected response headers and body
First three successful variants are HTML; the next two are Markdown. The unacceptable case is text/plain. Each response’s Vary includes Accept.
11. Expected state changes
Only the in-memory response cache may be populated; no content persistence is involved.
12. Expected emitted events or downstream calls, where applicable
Static homepage creation and cache access; no downstream service needed.
13. Negative assertions: what must not happen
Do not serve the earlier format for an incompatible later Accept value.
14. Cleanup and postconditions
Clear the test cache and restore spies after each case as worker.test.mjs does. Await captured waitUntil work when comparing cache variants. API-generation checks write a generated .wrangler artifact; they are not deployment commands.
15. Actual result
Not run — no observed result or execution log from this review.
This checks the listed media combinations against a test cache, not every possible Accept header or production cache behaviour.
25. Follow-up actions
Retain shared-cache sequencing when adding representation cases.
RES-002 — Serve the kind catalogue when Corpus is unavailable
Field
Specification or observation
1. Test ID and name
RES-002 — Serve the kind catalogue when Corpus is unavailable
2. Requirement or guarantee
Code-confirmed: the static kind catalogue belongs to Resources and does not require a Corpus read.
3. Purpose and risk addressed
Static discovery fails during a content-service outage or advertises a different vocabulary.
4. Priority
High
5. Test type
Integration
6. Preconditions
Provide valid NODE_CONFIG and a Corpus spy that throws if called; use the in-memory cache.
7. Input and test data
GET, HEAD, POST and OPTIONS /kind; GET with Accept text/markdown; read the local OpenAPI and guide documents.
8. Execution steps
1. Run route variants. 2. Compare the successful body with KIND_CATALOGUE. 3. Check allowed methods/media types. 4. Confirm OpenAPI enum/examples and guide entries agree. 5. Assert Corpus was not contacted.
9. Expected HTTP status, where applicable
GET/HEAD 200; POST 405; unsupported representation 406; OPTIONS 204.
10. Expected response headers and body
GET JSON equals KIND_CATALOGUE, with Access-Control-Allow-Origin *; HEAD has no body; 405 has Allow GET, HEAD; OpenAPI declares public access via an empty security list.
11. Expected state changes
No Corpus state change; static documents may use the test cache.
12. Expected emitted events or downstream calls, where applicable
Zero Corpus calls.
13. Negative assertions: what must not happen
No content-service call or authentication requirement for this public static catalogue.
14. Cleanup and postconditions
Clear the test cache and restore spies after each case as worker.test.mjs does. Await captured waitUntil work when comparing cache variants. API-generation checks write a generated .wrangler artifact; they are not deployment commands.
15. Actual result
Not run — no observed result or execution log from this review.
Catalogue count and values come from the pinned source, not an assumed future vocabulary.
25. Follow-up actions
Update the shared contract tests when the vocabulary intentionally changes.
RES-003 — Separate endpoint syntax routing from identity checks
Field
Specification or observation
1. Test ID and name
RES-003 — Separate endpoint syntax routing from identity checks
2. Requirement or guarantee
Code-confirmed: supported endpoint UUID syntax routes to Ingress; the gateway must not treat syntax alone as successful identity verification.
3. Purpose and risk addressed
A route pattern is mistaken for authentication, or malformed paths reach the wrong component.
4. Priority
Critical
5. Test type
Security
6. Preconditions
Use worker.test.mjs NODE_CONFIG and an Ingress spy that returns a controlled unauthorised result.
7. Input and test data
GET /{candidate_endpoint}/operation-token for the source’s UUID versions/case variants, invalid variant, malformed length, nil UUID, URN and encoded-prefix cases.
8. Execution steps
1. Iterate the existing candidate matrix. 2. Count Ingress calls. 3. Compare response statuses for routed and unrouted candidates.
9. Expected HTTP status, where applicable
401 from the Ingress fixture for syntactically accepted versions 1–5/case variants; 404 for the rejected path forms, including version 7 in this endpoint-routing gate.
10. Expected response headers and body
Routed cases preserve the controlled error response; exact error-body details are fixture values, not a universal gateway error contract.
11. Expected state changes
No storage or registration is performed by this fixture.
12. Expected emitted events or downstream calls, where applicable
One Ingress call for accepted syntax, zero for invalid syntax.
13. Negative assertions: what must not happen
No successful authentication based only on the identifier’s format; do not generalise this endpoint gate to message UUID rules.
14. Cleanup and postconditions
Clear the test cache and restore spies after each case as worker.test.mjs does. Await captured waitUntil work when comparing cache variants. API-generation checks write a generated .wrangler artifact; they are not deployment commands.
15. Actual result
Not run — no observed result or execution log from this review.
Ingress is a stand-in. Registration’s actual stored mapping is tested separately; UUID gates deliberately differ by interface.
25. Follow-up actions
Keep routing and real credential-mapping tests separate.
RES-004 — Publish the exact conversation pagination contract
Field
Specification or observation
1. Test ID and name
RES-004 — Publish the exact conversation pagination contract
2. Requirement or guarantee
Checked-in contract: conversation reads retain an array body, an exclusive decimal safe-integer after value and a cursor on every nonempty page, including the last short page.
3. Purpose and risk addressed
Generated clients terminate early or reject valid empty-page responses.
4. Priority
High
5. Test type
Contract
6. Preconditions
Call the checked-in openapi(config) builder with synthetic public service details and use the existing Ajv validator.
7. Input and test data
Inspect the GET /conversations parameter and 200 response definitions; validate 0, the supplied example, MAX_SAFE_INTEGER and invalid negative/fractional/unsafe values.
8. Execution steps
1. Build the document. 2. Inspect response body/header definitions and prose. 3. Validate boundary examples against the after schema.
9. Expected HTTP status, where applicable
Not an executed route request: these tests inspect the document’s 200 response definition.
10. Expected response headers and body
200 JSON schema is an array. Cursor prose states highest returned created_sequence and omission on empty pages; it is not universally required. after schema is integer, minimum 0, maximum Number.MAX_SAFE_INTEGER.
11. Expected state changes
No content data change; an API document is built in memory.
12. Expected emitted events or downstream calls, where applicable
No downstream Worker request in the direct builder tests.
13. Negative assertions: what must not happen
No unconditional required cursor on empty responses; no count-based or contiguous-sequence cursor rule.
14. Cleanup and postconditions
Clear the test cache and restore spies after each case as worker.test.mjs does. Await captured waitUntil work when comparing cache variants. API-generation checks write a generated .wrangler artifact; they are not deployment commands.
15. Actual result
Not run — no observed result or execution log from this review.
This verifies the source-built contract, not the deployed API or runtime pagination. Corpus has separate behavioural cases.
25. Follow-up actions
Use COR-002 as complementary runtime evidence; do not count it as execution of these schema tests.
RES-005 — Represent nonuniform error shapes and operation-specific limits
Field
Specification or observation
1. Test ID and name
RES-005 — Represent nonuniform error shapes and operation-specific limits
2. Requirement or guarantee
The checked-in OpenAPI builder must describe the applicable flat/nested errors, byte limits and retry headers. Runtime agreement with downstream handlers still needs direct evidence.
3. Purpose and risk addressed
Clients cannot interpret a legitimate error or apply an incorrect universal error envelope.
4. Priority
High
5. Test type
Contract
6. Preconditions
Use the contract-gaps builder fixture and Ajv; obtain representative real handler responses only in a future connected test.
7. Input and test data
Inspect message-write 400/500/413/503 definitions, relationship-write request bytes/429/428 headers, stream 400 text/plain, read 406 and HEAD response definitions.
8. Execution steps
1. Build the document. 2. Validate the existing flat and nested example errors. 3. Inspect the listed per-operation limits/headers. 4. Proposed extension: compare real downstream responses with the corresponding schemas.
9. Expected HTTP status, where applicable
No runtime response executed in the existing test; the inspected document entries include 400, 500, 413, 503, 429, 428 and 406.
10. Expected response headers and body
Message event limit prose includes 102400 bytes; relationship-body prose includes 4096 raw bytes independent of Content-Length. Message 503 exposes Retry-After; relationship 429 exposes Retry-After and 428 exposes X-ToastMachine-Onboarding. HEAD definitions contain no response content.
11. Expected state changes
No database change; document-only assertions.
12. Expected emitted events or downstream calls, where applicable
Existing test uses the builder and schema validator, not downstream Workers.
13. Negative assertions: what must not happen
Do not force all errors into a fabricated single JSON envelope or place a body contract on HEAD.
14. Cleanup and postconditions
Clear the test cache and restore spies after each case as worker.test.mjs does. Await captured waitUntil work when comparing cache variants. API-generation checks write a generated .wrangler artifact; they are not deployment commands.
15. Actual result
Not run — no observed result or execution log from this review.
Examples and schema/prose checks exist. The broader runtime-contract parity assertion is not implemented by this test.
25. Follow-up actions
Add representative real-handler schema-validation cases rather than reporting sample validation as end-to-end compatibility.
RES-006 — Characterise a failed cache lookup before producing a page
Field
Specification or observation
1. Test ID and name
RES-006 — Characterise a failed cache lookup before producing a page
2. Requirement or guarantee
Code-confirmed current behaviour: createCache awaits cache.match before producing the response and has no catch/fallback for that rejection. Availability expectations beyond that behaviour are unresolved.
3. Purpose and risk addressed
Documentation promises graceful cache bypass that the code does not implement.
4. Priority
Medium
5. Test type
Resilience
6. Preconditions
Use the direct exported Worker with valid NODE_CONFIG, a caches.default.match spy rejecting with a synthetic error, and spies for cache.put and any downstream calls.
7. Input and test data
GET / selecting a normal HTML representation.
8. Execution steps
1. Replace the test cache with the rejecting stand-in. 2. Await the handler rejection. 3. Confirm no cache write or downstream call. 4. Restore globals.
9. Expected HTTP status, where applicable
Unknown at platform boundary: the direct handler promise rejects; do not invent an application-defined status code.
10. Expected response headers and body
No normal homepage response is produced by the rejected direct call. No dedicated cache-recovery log contract is established.
11. Expected state changes
No cache entry is written by this attempt.
12. Expected emitted events or downstream calls, where applicable
One cache lookup fails before the producer; no downstream Worker is needed for the homepage.
13. Negative assertions: what must not happen
Do not record a fabricated 200 fallback or claim the result was served from cache.
14. Cleanup and postconditions
Clear the test cache and restore spies after each case as worker.test.mjs does. Await captured waitUntil work when comparing cache variants. API-generation checks write a generated .wrangler artifact; they are not deployment commands.
15. Actual result
Not run — no observed result or execution log from this review.
Proposed location: test/cache-failure.test.mjs. No existing case is claimed. After implementation use the established pnpm test suite command; this case is not yet runnable.
22. Implementation status
Proposed test, not implemented
23. Execution status
Not run
24. Known limitations
This is a proposed characterization test, not a recommendation to preserve the failure forever. Graceful bypass is a product/operational decision not established here.
25. Follow-up actions
Implement the characterization and decide whether a fallback requirement should be added separately.
Complete automated source catalogue
Every named source declaration at this revision is documented below, including tests already referenced by curated cases. Catalogue entries have fresh stable IDs after the original IDs. Preserve them on future edits; append new entries rather than renumbering. Category and priority are provisional documentation triage labels.
Expected outcomes below come from actual source assertions. Symbolic fixture values are left symbolic; private test markers are omitted. Shared helpers, loops and parameter tables can add assertions or test instances at runtime. Static extraction does not establish branch execution, complete side-effect coverage or a broader approved guarantee. A declaration with no directly extracted assertion explicitly requires helper review.
test/contract-gaps.test.mjs
RES-007 — every operation has an explicit unique stable SDK-compatible identifier
Field
Source-backed specification or observation
1. Test ID and name
RES-007 — every operation has an explicit unique stable SDK-compatible identifier
2. Requirement or guarantee
Source test intent: every operation has an explicit unique stable SDK-compatible identifier. Displayed assertions establish this test’s expected checks, not a separate system-wide guarantee.
3. Purpose and risk addressed
Detect regression of this named behaviour; complete business-impact/invariant analysis remains in the curated cases or follow-up review.
4. Priority
High — provisional catalogue triage; subject to risk review.
5. Test type
Contract — provisional grouping from the declaration name.
6. Preconditions
Use section C plus the cited file’s fixtures and setup/teardown hooks. Suite context: top level. Do not infer starting state from the title.
7. Input and test data
No each/for parameter table on this declaration; its callback may still generate inputs. Input/operation expressions: No direct request/operation expression extracted; inspect the source fixture/helper… Use disposable fixture data only.
8. Execution steps
1. Prepare the existing source test harness from section C. 2. Run pnpm test. 3. Locate this named declaration and its parameterized/conditional instances. 4. Compare the displayed assertions. 5. Record evidence and follow teardown. Not executed during this review.
9. Expected HTTP status, where applicable
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
10. Expected response headers and body
See assertions A1, A5 below. Referenced variables remain symbolic; no universal response envelope is assumed.
11. Expected state changes
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
12. Expected emitted events or downstream calls, where applicable
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
13. Negative assertions: what must not happen
See assertions A3 below. Only the shown negative/rejection checks are claimed; other forbidden effects require review.
14. Cleanup and postconditions
Use the cited file’s hooks/finally blocks and section C. Restore mocks and remove only isolated test data.
15. Actual result
Not run — no execution evidence collected.
16. Evidence references
test/contract-gaps.test.mjs:12; assertion/input source links below. Source key: test/contract-gaps.test.mjs :: every operation has an explicit unique stable SDK-compatible identifier :: line 12 at this pinned revision.
17. Execution date
Not run.
18. Status and outstanding issues
Existing declaration documented; indirect helper assertions and full semantic coverage are not inferred from static extraction.
19. Category
Contract (provisional).
20. Handler, interface or code path
test/contract-gaps.test.mjs:12; expressions No direct request/operation expression extracted; inspect the source fixture/helper… Imported modules: vitest, node:crypto, ajv/dist/2020.js, ../src/resources/openapi.ts, ../src/operation-ids.ts.
21. Test implementation location and command
test/contract-gaps.test.mjs:12 — every operation has an explicit unique stable SDK-compatible identifier. Run pnpm test from /home/johnny/projects/toastmachine-resources-worker after preparing its existing test environment; this invokes the suite.
22. Implementation status
Existing automated test
23. Execution status
Not run
24. Known limitations
Static source inventory only. Loops, parameter tables, shared helpers and conditional modifiers can change executed counts. Indirect helper assertions are not expanded.
25. Follow-up actions
Reconcile runtime instances with this declaration, review symbolic fixtures and unasserted effects, and record execution evidence. Preserve this ID.
Source assertions
A1 line 14: expect(await openapi(config).text()).toBe(first)
A2 line 32: expect(operation.operationId).toMatch(/^[A-Za-z][A-Za-z0-9]*$/)
A3 line 33: expect(Object.values(found)).not.toContain(operation.operationId)
A6 line 55: expect(\n createHash("sha256").update(JSON.stringify(legacy)).digest("hex"),\n ).toBe("0d1e993334a20a78d2de4b28453c147bdc6754af65ba809bbe9125e2d796723d")
Source inputs and operations
Inputs are supplied indirectly through the cited fixture/helper; inspect it before reproduction.
RES-008 — approved lexical normalization is explicit for both agent scalars
Field
Source-backed specification or observation
1. Test ID and name
RES-008 — approved lexical normalization is explicit for both agent scalars
2. Requirement or guarantee
Source test intent: approved lexical normalization is explicit for both agent scalars. Displayed assertions establish this test’s expected checks, not a separate system-wide guarantee.
3. Purpose and risk addressed
Detect regression of this named behaviour; complete business-impact/invariant analysis remains in the curated cases or follow-up review.
4. Priority
High — provisional catalogue triage; subject to risk review.
5. Test type
Regression — provisional grouping from the declaration name.
6. Preconditions
Use section C plus the cited file’s fixtures and setup/teardown hooks. Suite context: top level. Do not infer starting state from the title.
7. Input and test data
No each/for parameter table on this declaration; its callback may still generate inputs. Input/operation expressions: No direct request/operation expression extracted; inspect the source fixture/helper… Use disposable fixture data only.
8. Execution steps
1. Prepare the existing source test harness from section C. 2. Run pnpm test. 3. Locate this named declaration and its parameterized/conditional instances. 4. Compare the displayed assertions. 5. Record evidence and follow teardown. Not executed during this review.
9. Expected HTTP status, where applicable
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
10. Expected response headers and body
See assertions A1 below. Referenced variables remain symbolic; no universal response envelope is assumed.
11. Expected state changes
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
12. Expected emitted events or downstream calls, where applicable
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
13. Negative assertions: what must not happen
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
14. Cleanup and postconditions
Use the cited file’s hooks/finally blocks and section C. Restore mocks and remove only isolated test data.
15. Actual result
Not run — no execution evidence collected.
16. Evidence references
test/contract-gaps.test.mjs:60; assertion/input source links below. Source key: test/contract-gaps.test.mjs :: approved lexical normalization is explicit for both agent scalars :: line 60 at this pinned revision.
17. Execution date
Not run.
18. Status and outstanding issues
Existing declaration documented; indirect helper assertions and full semantic coverage are not inferred from static extraction.
19. Category
Regression (provisional).
20. Handler, interface or code path
test/contract-gaps.test.mjs:60; expressions No direct request/operation expression extracted; inspect the source fixture/helper… Imported modules: vitest, node:crypto, ajv/dist/2020.js, ../src/resources/openapi.ts, ../src/operation-ids.ts.
21. Test implementation location and command
test/contract-gaps.test.mjs:60 — approved lexical normalization is explicit for both agent scalars. Run pnpm test from /home/johnny/projects/toastmachine-resources-worker after preparing its existing test environment; this invokes the suite.
22. Implementation status
Existing automated test
23. Execution status
Not run
24. Known limitations
Static source inventory only. Loops, parameter tables, shared helpers and conditional modifiers can change executed counts. Indirect helper assertions are not expanded.
25. Follow-up actions
Reconcile runtime instances with this declaration, review symbolic fixtures and unasserted effects, and record execution evidence. Preserve this ID.
Source assertions
A1 line 66: expect(parameter.schema.type).toEqual(["number", "string"])
A2 line 67: expect(parameter.allowEmptyValue).toBe(true)
A3 line 77: expect(parameter.description).toContain(text)
Source inputs and operations
Inputs are supplied indirectly through the cited fixture/helper; inspect it before reproduction.
RES-009 — string schemas distinguish the code-point upper bound from approved UTF-16 budgets
Field
Source-backed specification or observation
1. Test ID and name
RES-009 — string schemas distinguish the code-point upper bound from approved UTF-16 budgets
2. Requirement or guarantee
Source test intent: string schemas distinguish the code-point upper bound from approved UTF-16 budgets. Displayed assertions establish this test’s expected checks, not a separate system-wide guarantee.
3. Purpose and risk addressed
Detect regression of this named behaviour; complete business-impact/invariant analysis remains in the curated cases or follow-up review.
4. Priority
High — provisional catalogue triage; subject to risk review.
5. Test type
Contract — provisional grouping from the declaration name.
6. Preconditions
Use section C plus the cited file’s fixtures and setup/teardown hooks. Suite context: top level. Do not infer starting state from the title.
7. Input and test data
No each/for parameter table on this declaration; its callback may still generate inputs. Input/operation expressions: No direct request/operation expression extracted; inspect the source fixture/helper… Use disposable fixture data only.
8. Execution steps
1. Prepare the existing source test harness from section C. 2. Run pnpm test. 3. Locate this named declaration and its parameterized/conditional instances. 4. Compare the displayed assertions. 5. Record evidence and follow teardown. Not executed during this review.
9. Expected HTTP status, where applicable
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
10. Expected response headers and body
See assertions A4, A5, A6, A7, A8 below. Referenced variables remain symbolic; no universal response envelope is assumed.
11. Expected state changes
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
12. Expected emitted events or downstream calls, where applicable
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
13. Negative assertions: what must not happen
See assertions A1 below. Only the shown negative/rejection checks are claimed; other forbidden effects require review.
14. Cleanup and postconditions
Use the cited file’s hooks/finally blocks and section C. Restore mocks and remove only isolated test data.
15. Actual result
Not run — no execution evidence collected.
16. Evidence references
test/contract-gaps.test.mjs:81; assertion/input source links below. Source key: test/contract-gaps.test.mjs :: string schemas distinguish the code-point upper bound from approved UTF-16 budgets :: line 81 at this pinned revision.
17. Execution date
Not run.
18. Status and outstanding issues
Existing declaration documented; indirect helper assertions and full semantic coverage are not inferred from static extraction.
19. Category
Contract (provisional).
20. Handler, interface or code path
test/contract-gaps.test.mjs:81; expressions No direct request/operation expression extracted; inspect the source fixture/helper… Imported modules: vitest, node:crypto, ajv/dist/2020.js, ../src/resources/openapi.ts, ../src/operation-ids.ts.
21. Test implementation location and command
test/contract-gaps.test.mjs:81 — string schemas distinguish the code-point upper bound from approved UTF-16 budgets. Run pnpm test from /home/johnny/projects/toastmachine-resources-worker after preparing its existing test environment; this invokes the suite.
22. Implementation status
Existing automated test
23. Execution status
Not run
24. Known limitations
Static source inventory only. Loops, parameter tables, shared helpers and conditional modifiers can change executed counts. Indirect helper assertions are not expanded.
25. Follow-up actions
Reconcile runtime instances with this declaration, review symbolic fixtures and unasserted effects, and record execution evidence. Preserve this ID.
Source assertions
A1 line 88: expect(subject.maxLength).toBeUndefined()
A2 line 89: expect(subject["x-max-utf16-code-units"]).toBe(200)
A3 line 90: expect(subject.description).toContain("U+0000–U+001F and U+007F")
A5 line 93: expect(content["x-max-utf16-code-units"]).toBe(65536)
A6 line 94: expect(content.description).toContain("32,769")
A7 line 95: expect(content.description).toContain("preserved without trimming")
A8 line 96: expect(content.description).toContain("looser upper bound")
Source inputs and operations
Inputs are supplied indirectly through the cited fixture/helper; inspect it before reproduction.
RES-010 — byte limits, nonuniform error envelopes and Retry-After are described per operation
Field
Source-backed specification or observation
1. Test ID and name
RES-010 — byte limits, nonuniform error envelopes and Retry-After are described per operation
2. Requirement or guarantee
Source test intent: byte limits, nonuniform error envelopes and Retry-After are described per operation. Displayed assertions establish this test’s expected checks, not a separate system-wide guarantee.
3. Purpose and risk addressed
Detect regression of this named behaviour; complete business-impact/invariant analysis remains in the curated cases or follow-up review.
4. Priority
High — provisional catalogue triage; subject to risk review.
5. Test type
Resilience — provisional grouping from the declaration name.
6. Preconditions
Use section C plus the cited file’s fixtures and setup/teardown hooks. Suite context: top level. Do not infer starting state from the title.
7. Input and test data
No each/for parameter table on this declaration; its callback may still generate inputs. Input/operation expressions: No direct request/operation expression extracted; inspect the source fixture/helper… Use disposable fixture data only.
8. Execution steps
1. Prepare the existing source test harness from section C. 2. Run pnpm test. 3. Locate this named declaration and its parameterized/conditional instances. 4. Compare the displayed assertions. 5. Record evidence and follow teardown. Not executed during this review.
9. Expected HTTP status, where applicable
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
10. Expected response headers and body
See assertions A1, A2, A3, A4, A5, A6, A7, A8, A9, A10, A11, A12 below. Referenced variables remain symbolic; no universal response envelope is assumed.
11. Expected state changes
See assertions A11 below. Expression grouping does not prove complete before/after state coverage.
12. Expected emitted events or downstream calls, where applicable
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
13. Negative assertions: what must not happen
See assertions A12 below. Only the shown negative/rejection checks are claimed; other forbidden effects require review.
14. Cleanup and postconditions
Use the cited file’s hooks/finally blocks and section C. Restore mocks and remove only isolated test data.
15. Actual result
Not run — no execution evidence collected.
16. Evidence references
test/contract-gaps.test.mjs:99; assertion/input source links below. Source key: test/contract-gaps.test.mjs :: byte limits, nonuniform error envelopes and Retry-After are described per operation :: line 99 at this pinned revision.
17. Execution date
Not run.
18. Status and outstanding issues
Existing declaration documented; indirect helper assertions and full semantic coverage are not inferred from static extraction.
19. Category
Resilience (provisional).
20. Handler, interface or code path
test/contract-gaps.test.mjs:99; expressions No direct request/operation expression extracted; inspect the source fixture/helper… Imported modules: vitest, node:crypto, ajv/dist/2020.js, ../src/resources/openapi.ts, ../src/operation-ids.ts.
21. Test implementation location and command
test/contract-gaps.test.mjs:99 — byte limits, nonuniform error envelopes and Retry-After are described per operation. Run pnpm test from /home/johnny/projects/toastmachine-resources-worker after preparing its existing test environment; this invokes the suite.
22. Implementation status
Existing automated test
23. Execution status
Not run
24. Known limitations
Static source inventory only. Loops, parameter tables, shared helpers and conditional modifiers can change executed counts. Indirect helper assertions are not expanded.
25. Follow-up actions
Reconcile runtime instances with this declaration, review symbolic fixtures and unasserted effects, and record execution evidence. Preserve this ID.
Source assertions
A1 line 107: expect(op.responses["413"].description).toContain("102,400")
A2 line 108: expect(op.responses["413"].description).toContain("identity, timestamps")
A3 line 126: expect(\n ajv.compile(op.responses[status].content["application/json"].schema)(\n body,\n ),\n ).toBe(true)
A4 line 131: expect(op.responses["503"].headers["Retry-After"]).toBeDefined()
A5 line 138: expect(op.requestBody.description).toContain(\n "4,096 raw HTTP request-body bytes",\n )
A6 line 141: expect(op.requestBody.description).toContain(\n "Content-Length does not override",\n )
A7 line 144: expect(op.requestBody.description).toContain(\n "server-added request metadata",\n )
A8 line 147: expect(op.responses["429"].headers["Retry-After"]).toBeDefined()
A9 line 148: expect(\n op.responses["428"].headers["X-ToastMachine-Onboarding"],\n ).toBeDefined()
A10 line 152: expect(\n spec.paths["/corpus/stream"].get.responses["400"].content["text/plain"],\n ).toBeDefined()
A11 line 155: expect(\n spec.paths["/messages"].get.responses["406"].content["application/json"],\n ).toBeDefined()
A12 line 160: expect(response.content).toBeUndefined()
Source inputs and operations
Inputs are supplied indirectly through the cited fixture/helper; inspect it before reproduction.
RES-011 — identifier descriptions expose different gates without globally narrowing UUID schemas
Field
Source-backed specification or observation
1. Test ID and name
RES-011 — identifier descriptions expose different gates without globally narrowing UUID schemas
2. Requirement or guarantee
Source test intent: identifier descriptions expose different gates without globally narrowing UUID schemas. Displayed assertions establish this test’s expected checks, not a separate system-wide guarantee.
3. Purpose and risk addressed
Detect regression of this named behaviour; complete business-impact/invariant analysis remains in the curated cases or follow-up review.
4. Priority
High — provisional catalogue triage; subject to risk review.
5. Test type
Security — provisional grouping from the declaration name.
6. Preconditions
Use section C plus the cited file’s fixtures and setup/teardown hooks. Suite context: top level. Do not infer starting state from the title.
7. Input and test data
No each/for parameter table on this declaration; its callback may still generate inputs. Input/operation expressions: No direct request/operation expression extracted; inspect the source fixture/helper… Use disposable fixture data only.
8. Execution steps
1. Prepare the existing source test harness from section C. 2. Run pnpm test. 3. Locate this named declaration and its parameterized/conditional instances. 4. Compare the displayed assertions. 5. Record evidence and follow teardown. Not executed during this review.
9. Expected HTTP status, where applicable
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
10. Expected response headers and body
See assertions A1, A3, A11 below. Referenced variables remain symbolic; no universal response envelope is assumed.
11. Expected state changes
See assertions A3, A6, A7 below. Expression grouping does not prove complete before/after state coverage.
12. Expected emitted events or downstream calls, where applicable
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
13. Negative assertions: what must not happen
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
14. Cleanup and postconditions
Use the cited file’s hooks/finally blocks and section C. Restore mocks and remove only isolated test data.
15. Actual result
Not run — no execution evidence collected.
16. Evidence references
test/contract-gaps.test.mjs:163; assertion/input source links below. Source key: test/contract-gaps.test.mjs :: identifier descriptions expose different gates without globally narrowing UUID schemas :: line 163 at this pinned revision.
17. Execution date
Not run.
18. Status and outstanding issues
Existing declaration documented; indirect helper assertions and full semantic coverage are not inferred from static extraction.
19. Category
Security (provisional).
20. Handler, interface or code path
test/contract-gaps.test.mjs:163; expressions No direct request/operation expression extracted; inspect the source fixture/helper… Imported modules: vitest, node:crypto, ajv/dist/2020.js, ../src/resources/openapi.ts, ../src/operation-ids.ts.
21. Test implementation location and command
test/contract-gaps.test.mjs:163 — identifier descriptions expose different gates without globally narrowing UUID schemas. Run pnpm test from /home/johnny/projects/toastmachine-resources-worker after preparing its existing test environment; this invokes the suite.
22. Implementation status
Existing automated test
23. Execution status
Not run
24. Known limitations
Static source inventory only. Loops, parameter tables, shared helpers and conditional modifiers can change executed counts. Indirect helper assertions are not expanded.
25. Follow-up actions
Reconcile runtime instances with this declaration, review symbolic fixtures and unasserted effects, and record execution evidence. Preserve this ID.
A4 line 181: expect(endpoint.description).toContain("versions 1–5")
A5 line 182: expect(endpoint.description).toContain("registered endpoint/credential pair")
A6 line 183: expect(\n parameter("/agents/{author_id}", "get", "author_id").description,\n ).toContain("Public attribution")
A7 line 186: expect(\n parameter("/messages/{message_id}", "get", "message_id").description,\n ).toContain("without an endpoint-ID UUID-version gate")
A8 line 189: expect(\n parameter(\n "/relationship-retractions/{retraction_id}",\n "get",\n "retraction_id",\n ).description,\n ).toContain("without checking version or variant")
A10 line 203: expect(\n parameter("/{endpoint_id}/createRelationship", "post", "Operation-Token")\n .description,\n ).toContain("need not be UUIDs")
A11 line 207: expect(\n spec.components.schemas.CreateRelationshipRequest.description,\n ).toContain("trimmed and lowercased")
Source inputs and operations
Inputs are supplied indirectly through the cited fixture/helper; inspect it before reproduction.
RES-012 — static read templates do not invent input/missing-resource errors or a universal representation envelope
Field
Source-backed specification or observation
1. Test ID and name
RES-012 — static read templates do not invent input/missing-resource errors or a universal representation envelope
2. Requirement or guarantee
Source test intent: static read templates do not invent input/missing-resource errors or a universal representation envelope. Displayed assertions establish this test’s expected checks, not a separate system-wide guarantee.
3. Purpose and risk addressed
Detect regression of this named behaviour; complete business-impact/invariant analysis remains in the curated cases or follow-up review.
4. Priority
High — provisional catalogue triage; subject to risk review.
5. Test type
Regression — provisional grouping from the declaration name.
6. Preconditions
Use section C plus the cited file’s fixtures and setup/teardown hooks. Suite context: top level. Do not infer starting state from the title.
7. Input and test data
No each/for parameter table on this declaration; its callback may still generate inputs. Input/operation expressions: No direct request/operation expression extracted; inspect the source fixture/helper… Use disposable fixture data only.
8. Execution steps
1. Prepare the existing source test harness from section C. 2. Run pnpm test. 3. Locate this named declaration and its parameterized/conditional instances. 4. Compare the displayed assertions. 5. Record evidence and follow teardown. Not executed during this review.
9. Expected HTTP status, where applicable
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
10. Expected response headers and body
See assertions A1, A2, A3, A4, A5, A6 below. Referenced variables remain symbolic; no universal response envelope is assumed.
11. Expected state changes
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
12. Expected emitted events or downstream calls, where applicable
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
13. Negative assertions: what must not happen
See assertions A2, A3, A5 below. Only the shown negative/rejection checks are claimed; other forbidden effects require review.
14. Cleanup and postconditions
Use the cited file’s hooks/finally blocks and section C. Restore mocks and remove only isolated test data.
15. Actual result
Not run — no execution evidence collected.
16. Evidence references
test/contract-gaps.test.mjs:212; assertion/input source links below. Source key: test/contract-gaps.test.mjs :: static read templates do not invent input/missing-resource errors or a universal representation envelope :: line 212 at this pinned revision.
17. Execution date
Not run.
18. Status and outstanding issues
Existing declaration documented; indirect helper assertions and full semantic coverage are not inferred from static extraction.
19. Category
Regression (provisional).
20. Handler, interface or code path
test/contract-gaps.test.mjs:212; expressions No direct request/operation expression extracted; inspect the source fixture/helper… Imported modules: vitest, node:crypto, ajv/dist/2020.js, ../src/resources/openapi.ts, ../src/operation-ids.ts.
21. Test implementation location and command
test/contract-gaps.test.mjs:212 — static read templates do not invent input/missing-resource errors or a universal representation envelope. Run pnpm test from /home/johnny/projects/toastmachine-resources-worker after preparing its existing test environment; this invokes the suite.
22. Implementation status
Existing automated test
23. Execution status
Not run
24. Known limitations
Static source inventory only. Loops, parameter tables, shared helpers and conditional modifiers can change executed counts. Indirect helper assertions are not expanded.
25. Follow-up actions
Reconcile runtime instances with this declaration, review symbolic fixtures and unasserted effects, and record execution evidence. Preserve this ID.
Source assertions
A1 line 214: expect(\n spec.paths["/"].get.responses["406"].content["text/plain"],\n ).toBeDefined()
A2 line 223: expect(spec.paths[path][method].responses["400"]).toBeUndefined()
A3 line 224: expect(spec.paths[path][method].responses["404"]).toBeUndefined()
A4 line 225: expect(\n spec.paths[path][method].responses["405"].headers.Allow,\n ).toBeDefined()
A5 line 231: expect(spec.paths[path].get.responses["404"]).toBeUndefined()
A6 line 236: expect(spec.paths[path].post.responses["502"].description).toContain(\n "verify the supplied identity",\n )
Source inputs and operations
Inputs are supplied indirectly through the cited fixture/helper; inspect it before reproduction.
RES-013 — public contracts and rendered guides exclude service and storage implementation details
Field
Source-backed specification or observation
1. Test ID and name
RES-013 — public contracts and rendered guides exclude service and storage implementation details
2. Requirement or guarantee
Source test intent: public contracts and rendered guides exclude service and storage implementation details. Displayed assertions establish this test’s expected checks, not a separate system-wide guarantee.
3. Purpose and risk addressed
Detect regression of this named behaviour; complete business-impact/invariant analysis remains in the curated cases or follow-up review.
4. Priority
High — provisional catalogue triage; subject to risk review.
5. Test type
Contract — provisional grouping from the declaration name.
6. Preconditions
Use section C plus the cited file’s fixtures and setup/teardown hooks. Suite context: top level. Do not infer starting state from the title.
7. Input and test data
No each/for parameter table on this declaration; its callback may still generate inputs. Input/operation expressions: No direct request/operation expression extracted; inspect the source fixture/helper… Use disposable fixture data only.
8. Execution steps
1. Prepare the existing source test harness from section C. 2. Run pnpm test. 3. Locate this named declaration and its parameterized/conditional instances. 4. Compare the displayed assertions. 5. Record evidence and follow teardown. Not executed during this review.
9. Expected HTTP status, where applicable
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
10. Expected response headers and body
See assertions A1 below. Referenced variables remain symbolic; no universal response envelope is assumed.
11. Expected state changes
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
12. Expected emitted events or downstream calls, where applicable
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
13. Negative assertions: what must not happen
See assertions A1, A2 below. Only the shown negative/rejection checks are claimed; other forbidden effects require review.
14. Cleanup and postconditions
Use the cited file’s hooks/finally blocks and section C. Restore mocks and remove only isolated test data.
15. Actual result
Not run — no execution evidence collected.
16. Evidence references
test/contract-gaps.test.mjs:241; assertion/input source links below. Source key: test/contract-gaps.test.mjs :: public contracts and rendered guides exclude service and storage implementation details :: line 241 at this pinned revision.
17. Execution date
Not run.
18. Status and outstanding issues
Existing declaration documented; indirect helper assertions and full semantic coverage are not inferred from static extraction.
19. Category
Contract (provisional).
20. Handler, interface or code path
test/contract-gaps.test.mjs:241; expressions No direct request/operation expression extracted; inspect the source fixture/helper… Imported modules: vitest, node:crypto, ajv/dist/2020.js, ../src/resources/openapi.ts, ../src/operation-ids.ts.
21. Test implementation location and command
test/contract-gaps.test.mjs:241 — public contracts and rendered guides exclude service and storage implementation details. Run pnpm test from /home/johnny/projects/toastmachine-resources-worker after preparing its existing test environment; this invokes the suite.
22. Implementation status
Existing automated test
23. Execution status
Not run
24. Known limitations
Static source inventory only. Loops, parameter tables, shared helpers and conditional modifiers can change executed counts. Indirect helper assertions are not expanded.
25. Follow-up actions
Reconcile runtime instances with this declaration, review symbolic fixtures and unasserted effects, and record execution evidence. Preserve this ID.
Source assertions
A1 line 250: expect(await render(config).text()).not.toMatch(implementation)
A2 line 252: expect(HOW_TO_USE_GUIDE).not.toMatch(implementation)
Source inputs and operations
Inputs are supplied indirectly through the cited fixture/helper; inspect it before reproduction.
test/history-lineage.test.mjs
RES-014 — snapshot identity and canonical page identity are mandatory, public and fail closed
Field
Source-backed specification or observation
1. Test ID and name
RES-014 — snapshot identity and canonical page identity are mandatory, public and fail closed
2. Requirement or guarantee
Source test intent: snapshot identity and canonical page identity are mandatory, public and fail closed. Displayed assertions establish this test’s expected checks, not a separate system-wide guarantee.
3. Purpose and risk addressed
Detect regression of this named behaviour; complete business-impact/invariant analysis remains in the curated cases or follow-up review.
4. Priority
High — provisional catalogue triage; subject to risk review.
5. Test type
Resilience — provisional grouping from the declaration name.
6. Preconditions
Use section C plus the cited file’s fixtures and setup/teardown hooks. Suite context: top level. Do not infer starting state from the title.
7. Input and test data
No each/for parameter table on this declaration; its callback may still generate inputs. Input/operation expressions: No direct request/operation expression extracted; inspect the source fixture/helper… Use disposable fixture data only.
8. Execution steps
1. Prepare the existing source test harness from section C. 2. Run pnpm test. 3. Locate this named declaration and its parameterized/conditional instances. 4. Compare the displayed assertions. 5. Record evidence and follow teardown. Not executed during this review.
9. Expected HTTP status, where applicable
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
10. Expected response headers and body
See assertions A5, A6, A7, A8, A9 below. Referenced variables remain symbolic; no universal response envelope is assumed.
11. Expected state changes
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
12. Expected emitted events or downstream calls, where applicable
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
13. Negative assertions: what must not happen
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
14. Cleanup and postconditions
Use the cited file’s hooks/finally blocks and section C. Restore mocks and remove only isolated test data.
15. Actual result
Not run — no execution evidence collected.
16. Evidence references
test/history-lineage.test.mjs:5; assertion/input source links below. Source key: test/history-lineage.test.mjs :: snapshot identity and canonical page identity are mandatory, public and fail closed :: line 5 at this pinned revision.
17. Execution date
Not run.
18. Status and outstanding issues
Existing declaration documented; indirect helper assertions and full semantic coverage are not inferred from static extraction.
19. Category
Resilience (provisional).
20. Handler, interface or code path
test/history-lineage.test.mjs:5; expressions No direct request/operation expression extracted; inspect the source fixture/helper… Imported modules: vitest, ajv/dist/2020.js, ../scripts/generate-openapi.mjs.
21. Test implementation location and command
test/history-lineage.test.mjs:5 — snapshot identity and canonical page identity are mandatory, public and fail closed. Run pnpm test from /home/johnny/projects/toastmachine-resources-worker after preparing its existing test environment; this invokes the suite.
22. Implementation status
Existing automated test
23. Execution status
Not run
24. Known limitations
Static source inventory only. Loops, parameter tables, shared helpers and conditional modifiers can change executed counts. Indirect helper assertions are not expanded.
25. Follow-up actions
Reconcile runtime instances with this declaration, review symbolic fixtures and unasserted effects, and record execution evidence. Preserve this ID.
A5 line 56: expect(op.responses["200"].headers[header].required).toBe(true)
A6 line 57: expect(op.responses["200"].headers[header].schema.pattern).toBe(\n schema.properties.history_lineage.pattern,\n )
A7 line 61: expect(op.responses["503"].description).toContain("lineage_unavailable")
A8 line 62: expect(op.responses["503"].content["application/json"]).toBeDefined()
A9 line 63: expect(op.responses["503"].content["application/ld+json"]).toBeDefined()
Source inputs and operations
Inputs are supplied indirectly through the cited fixture/helper; inspect it before reproduction.
test/openapi-sdk.test.mjs
RES-015 — message pagination accepts URI references while other URLs remain absolute
Field
Source-backed specification or observation
1. Test ID and name
RES-015 — message pagination accepts URI references while other URLs remain absolute
2. Requirement or guarantee
Source test intent: message pagination accepts URI references while other URLs remain absolute. Displayed assertions establish this test’s expected checks, not a separate system-wide guarantee.
3. Purpose and risk addressed
Detect regression of this named behaviour; complete business-impact/invariant analysis remains in the curated cases or follow-up review.
4. Priority
High — provisional catalogue triage; subject to risk review.
5. Test type
Regression — provisional grouping from the declaration name.
6. Preconditions
Use section C plus the cited file’s fixtures and setup/teardown hooks. Suite context: top level. Do not infer starting state from the title.
7. Input and test data
No each/for parameter table on this declaration; its callback may still generate inputs. Input/operation expressions: No direct request/operation expression extracted; inspect the source fixture/helper… Use disposable fixture data only.
8. Execution steps
1. Prepare the existing source test harness from section C. 2. Run pnpm test. 3. Locate this named declaration and its parameterized/conditional instances. 4. Compare the displayed assertions. 5. Record evidence and follow teardown. Not executed during this review.
9. Expected HTTP status, where applicable
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
10. Expected response headers and body
See assertions A1, A2, A3, A6 below. Referenced variables remain symbolic; no universal response envelope is assumed.
11. Expected state changes
See assertions A4, A6 below. Expression grouping does not prove complete before/after state coverage.
12. Expected emitted events or downstream calls, where applicable
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
13. Negative assertions: what must not happen
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
14. Cleanup and postconditions
Use the cited file’s hooks/finally blocks and section C. Restore mocks and remove only isolated test data.
15. Actual result
Not run — no execution evidence collected.
16. Evidence references
test/openapi-sdk.test.mjs:17; assertion/input source links below. Source key: test/openapi-sdk.test.mjs :: message pagination accepts URI references while other URLs remain absolute :: line 17 at this pinned revision.
17. Execution date
Not run.
18. Status and outstanding issues
Existing declaration documented; indirect helper assertions and full semantic coverage are not inferred from static extraction.
19. Category
Regression (provisional).
20. Handler, interface or code path
test/openapi-sdk.test.mjs:17; expressions No direct request/operation expression extracted; inspect the source fixture/helper… Imported modules: vitest, node:module, ajv/dist/2020.js, ../src/resources/openapi.ts.
21. Test implementation location and command
test/openapi-sdk.test.mjs:17 — message pagination accepts URI references while other URLs remain absolute. Run pnpm test from /home/johnny/projects/toastmachine-resources-worker after preparing its existing test environment; this invokes the suite.
22. Implementation status
Existing automated test
23. Execution status
Not run
24. Known limitations
Static source inventory only. Loops, parameter tables, shared helpers and conditional modifiers can change executed counts. Indirect helper assertions are not expanded.
25. Follow-up actions
Reconcile runtime instances with this declaration, review symbolic fixtures and unasserted effects, and record execution evidence. Preserve this ID.
Source assertions
A1 line 25: expect(schema.format).toBe("uri-reference")
A2 line 26: expect(schema.description).toContain("against the URL of this response")
A3 line 35: expect(validate(link), JSON.stringify(validate.errors)).toBe(true)
A4 line 37: expect(validate("/messages?tag=invalid space")).toBe(false)
A6 line 40: expect(spec.components.schemas.Message.properties.url.format).toBe("uri")
A7 line 45: expect(search.properties[field].format).toBe("uri")
A8 line 46: expect(ajv.compile(search.properties[field])("/search?offset=1")).toBe(\n false,\n )
Source inputs and operations
Inputs are supplied indirectly through the cited fixture/helper; inspect it before reproduction.
RES-016 — registration advertises no request body
Field
Source-backed specification or observation
1. Test ID and name
RES-016 — registration advertises no request body
2. Requirement or guarantee
Source test intent: registration advertises no request body. Displayed assertions establish this test’s expected checks, not a separate system-wide guarantee.
3. Purpose and risk addressed
Detect regression of this named behaviour; complete business-impact/invariant analysis remains in the curated cases or follow-up review.
4. Priority
High — provisional catalogue triage; subject to risk review.
5. Test type
Contract — provisional grouping from the declaration name.
6. Preconditions
Use section C plus the cited file’s fixtures and setup/teardown hooks. Suite context: top level. Do not infer starting state from the title.
7. Input and test data
No each/for parameter table on this declaration; its callback may still generate inputs. Input/operation expressions: No direct request/operation expression extracted; inspect the source fixture/helper… Use disposable fixture data only.
8. Execution steps
1. Prepare the existing source test harness from section C. 2. Run pnpm test. 3. Locate this named declaration and its parameterized/conditional instances. 4. Compare the displayed assertions. 5. Record evidence and follow teardown. Not executed during this review.
9. Expected HTTP status, where applicable
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
10. Expected response headers and body
See assertions A1, A2 below. Referenced variables remain symbolic; no universal response envelope is assumed.
11. Expected state changes
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
12. Expected emitted events or downstream calls, where applicable
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
13. Negative assertions: what must not happen
See assertions A1 below. Only the shown negative/rejection checks are claimed; other forbidden effects require review.
14. Cleanup and postconditions
Use the cited file’s hooks/finally blocks and section C. Restore mocks and remove only isolated test data.
15. Actual result
Not run — no execution evidence collected.
16. Evidence references
test/openapi-sdk.test.mjs:52; assertion/input source links below. Source key: test/openapi-sdk.test.mjs :: registration advertises no request body :: line 52 at this pinned revision.
17. Execution date
Not run.
18. Status and outstanding issues
Existing declaration documented; indirect helper assertions and full semantic coverage are not inferred from static extraction.
19. Category
Contract (provisional).
20. Handler, interface or code path
test/openapi-sdk.test.mjs:52; expressions No direct request/operation expression extracted; inspect the source fixture/helper… Imported modules: vitest, node:module, ajv/dist/2020.js, ../src/resources/openapi.ts.
21. Test implementation location and command
test/openapi-sdk.test.mjs:52 — registration advertises no request body. Run pnpm test from /home/johnny/projects/toastmachine-resources-worker after preparing its existing test environment; this invokes the suite.
22. Implementation status
Existing automated test
23. Execution status
Not run
24. Known limitations
Static source inventory only. Loops, parameter tables, shared helpers and conditional modifiers can change executed counts. Indirect helper assertions are not expanded.
25. Follow-up actions
Reconcile runtime instances with this declaration, review symbolic fixtures and unasserted effects, and record execution evidence. Preserve this ID.
Source assertions
A1 line 54: expect(spec.paths["/register"].post.requestBody).toBeUndefined()
A2 line 55: expect(spec.paths["/register"].post.description).toContain("empty body")
Source inputs and operations
Inputs are supplied indirectly through the cited fixture/helper; inspect it before reproduction.
RES-017 — message writes document the actual first-write onboarding response
Field
Source-backed specification or observation
1. Test ID and name
RES-017 — message writes document the actual first-write onboarding response
2. Requirement or guarantee
Source test intent: message writes document the actual first-write onboarding response. Displayed assertions establish this test’s expected checks, not a separate system-wide guarantee.
3. Purpose and risk addressed
Detect regression of this named behaviour; complete business-impact/invariant analysis remains in the curated cases or follow-up review.
4. Priority
High — provisional catalogue triage; subject to risk review.
5. Test type
Regression — provisional grouping from the declaration name.
6. Preconditions
Use section C plus the cited file’s fixtures and setup/teardown hooks. Suite context: top level. Do not infer starting state from the title.
7. Input and test data
No each/for parameter table on this declaration; its callback may still generate inputs. Input/operation expressions: No direct request/operation expression extracted; inspect the source fixture/helper… Use disposable fixture data only.
8. Execution steps
1. Prepare the existing source test harness from section C. 2. Run pnpm test. 3. Locate this named declaration and its parameterized/conditional instances. 4. Compare the displayed assertions. 5. Record evidence and follow teardown. Not executed during this review.
9. Expected HTTP status, where applicable
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
10. Expected response headers and body
See assertions A1, A2, A3, A4 below. Referenced variables remain symbolic; no universal response envelope is assumed.
11. Expected state changes
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
12. Expected emitted events or downstream calls, where applicable
See assertions A1 below. No delivery guarantee beyond the checked expressions is inferred.
13. Negative assertions: what must not happen
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
14. Cleanup and postconditions
Use the cited file’s hooks/finally blocks and section C. Restore mocks and remove only isolated test data.
15. Actual result
Not run — no execution evidence collected.
16. Evidence references
test/openapi-sdk.test.mjs:58; assertion/input source links below. Source key: test/openapi-sdk.test.mjs :: message writes document the actual first-write onboarding response :: line 58 at this pinned revision.
17. Execution date
Not run.
18. Status and outstanding issues
Existing declaration documented; indirect helper assertions and full semantic coverage are not inferred from static extraction.
19. Category
Regression (provisional).
20. Handler, interface or code path
test/openapi-sdk.test.mjs:58; expressions No direct request/operation expression extracted; inspect the source fixture/helper… Imported modules: vitest, node:module, ajv/dist/2020.js, ../src/resources/openapi.ts.
21. Test implementation location and command
test/openapi-sdk.test.mjs:58 — message writes document the actual first-write onboarding response. Run pnpm test from /home/johnny/projects/toastmachine-resources-worker after preparing its existing test environment; this invokes the suite.
22. Implementation status
Existing automated test
23. Execution status
Not run
24. Known limitations
Static source inventory only. Loops, parameter tables, shared helpers and conditional modifiers can change executed counts. Indirect helper assertions are not expanded.
25. Follow-up actions
Reconcile runtime instances with this declaration, review symbolic fixtures and unasserted effects, and record execution evidence. Preserve this ID.
Source assertions
A1 line 66: expect(response.description).toContain("without publishing")
A2 line 67: expect(response.headers["X-ToastMachine-Onboarding"].schema.const).toBe(\n "required",\n )
A3 line 81: expect(validate({ error }), JSON.stringify(validate.errors)).toBe(true)
Inputs are supplied indirectly through the cited fixture/helper; inspect it before reproduction.
RES-018 — agent profile gap seconds allow the fractional values returned by Corpus
Field
Source-backed specification or observation
1. Test ID and name
RES-018 — agent profile gap seconds allow the fractional values returned by Corpus
2. Requirement or guarantee
Source test intent: agent profile gap seconds allow the fractional values returned by Corpus. Displayed assertions establish this test’s expected checks, not a separate system-wide guarantee.
3. Purpose and risk addressed
Detect regression of this named behaviour; complete business-impact/invariant analysis remains in the curated cases or follow-up review.
4. Priority
High — provisional catalogue triage; subject to risk review.
5. Test type
Regression — provisional grouping from the declaration name.
6. Preconditions
Use section C plus the cited file’s fixtures and setup/teardown hooks. Suite context: top level. Do not infer starting state from the title.
7. Input and test data
No each/for parameter table on this declaration; its callback may still generate inputs. Input/operation expressions: No direct request/operation expression extracted; inspect the source fixture/helper… Use disposable fixture data only.
8. Execution steps
1. Prepare the existing source test harness from section C. 2. Run pnpm test. 3. Locate this named declaration and its parameterized/conditional instances. 4. Compare the displayed assertions. 5. Record evidence and follow teardown. Not executed during this review.
9. Expected HTTP status, where applicable
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
10. Expected response headers and body
See assertions A1 below. Referenced variables remain symbolic; no universal response envelope is assumed.
11. Expected state changes
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
12. Expected emitted events or downstream calls, where applicable
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
13. Negative assertions: what must not happen
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
14. Cleanup and postconditions
Use the cited file’s hooks/finally blocks and section C. Restore mocks and remove only isolated test data.
15. Actual result
Not run — no execution evidence collected.
16. Evidence references
test/openapi-sdk.test.mjs:86; assertion/input source links below. Source key: test/openapi-sdk.test.mjs :: agent profile gap seconds allow the fractional values returned by Corpus :: line 86 at this pinned revision.
17. Execution date
Not run.
18. Status and outstanding issues
Existing declaration documented; indirect helper assertions and full semantic coverage are not inferred from static extraction.
19. Category
Regression (provisional).
20. Handler, interface or code path
test/openapi-sdk.test.mjs:86; expressions No direct request/operation expression extracted; inspect the source fixture/helper… Imported modules: vitest, node:module, ajv/dist/2020.js, ../src/resources/openapi.ts.
21. Test implementation location and command
test/openapi-sdk.test.mjs:86 — agent profile gap seconds allow the fractional values returned by Corpus. Run pnpm test from /home/johnny/projects/toastmachine-resources-worker after preparing its existing test environment; this invokes the suite.
22. Implementation status
Existing automated test
23. Execution status
Not run
24. Known limitations
Static source inventory only. Loops, parameter tables, shared helpers and conditional modifiers can change executed counts. Indirect helper assertions are not expanded.
25. Follow-up actions
Reconcile runtime instances with this declaration, review symbolic fixtures and unasserted effects, and record execution evidence. Preserve this ID.
Source assertions
A1 line 94: expect(validate(0.125), JSON.stringify(validate.errors)).toBe(true)
Inputs are supplied indirectly through the cited fixture/helper; inspect it before reproduction.
test/pagination-openapi.test.mjs
RES-019 — conversation pagination documents header presence and termination without changing its array response
Field
Source-backed specification or observation
1. Test ID and name
RES-019 — conversation pagination documents header presence and termination without changing its array response
2. Requirement or guarantee
Source test intent: conversation pagination documents header presence and termination without changing its array response. Displayed assertions establish this test’s expected checks, not a separate system-wide guarantee.
3. Purpose and risk addressed
Detect regression of this named behaviour; complete business-impact/invariant analysis remains in the curated cases or follow-up review.
4. Priority
High — provisional catalogue triage; subject to risk review.
5. Test type
Contract — provisional grouping from the declaration name.
6. Preconditions
Use section C plus the cited file’s fixtures and setup/teardown hooks. Suite context: top level. Do not infer starting state from the title.
7. Input and test data
No each/for parameter table on this declaration; its callback may still generate inputs. Input/operation expressions: No direct request/operation expression extracted; inspect the source fixture/helper… Use disposable fixture data only.
8. Execution steps
1. Prepare the existing source test harness from section C. 2. Run pnpm test. 3. Locate this named declaration and its parameterized/conditional instances. 4. Compare the displayed assertions. 5. Record evidence and follow teardown. Not executed during this review.
9. Expected HTTP status, where applicable
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
10. Expected response headers and body
See assertions A3, A8 below. Referenced variables remain symbolic; no universal response envelope is assumed.
11. Expected state changes
See assertions A1, A2, A5, A6, A9, A10, A11, A12 below. Expression grouping does not prove complete before/after state coverage.
12. Expected emitted events or downstream calls, where applicable
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
13. Negative assertions: what must not happen
See assertions A11 below. Only the shown negative/rejection checks are claimed; other forbidden effects require review.
14. Cleanup and postconditions
Use the cited file’s hooks/finally blocks and section C. Restore mocks and remove only isolated test data.
15. Actual result
Not run — no execution evidence collected.
16. Evidence references
test/pagination-openapi.test.mjs:11; assertion/input source links below. Source key: test/pagination-openapi.test.mjs :: conversation pagination documents header presence and termination without changing its array response :: line 11 at this pinned revision.
17. Execution date
Not run.
18. Status and outstanding issues
Existing declaration documented; indirect helper assertions and full semantic coverage are not inferred from static extraction.
19. Category
Contract (provisional).
20. Handler, interface or code path
test/pagination-openapi.test.mjs:11; expressions No direct request/operation expression extracted; inspect the source fixture/helper… Imported modules: vitest, ajv/dist/2020.js, ../src/resources/openapi.ts.
21. Test implementation location and command
test/pagination-openapi.test.mjs:11 — conversation pagination documents header presence and termination without changing its array response. Run pnpm test from /home/johnny/projects/toastmachine-resources-worker after preparing its existing test environment; this invokes the suite.
22. Implementation status
Existing automated test
23. Execution status
Not run
24. Known limitations
Static source inventory only. Loops, parameter tables, shared helpers and conditional modifiers can change executed counts. Indirect helper assertions are not expanded.
25. Follow-up actions
Reconcile runtime instances with this declaration, review symbolic fixtures and unasserted effects, and record execution evidence. Preserve this ID.
Source assertions
A1 line 14: expect(operation.description).toContain("created_sequence ascending")
A2 line 15: expect(operation.description).toContain("Sequence gaps are valid")
A3 line 16: expect(operation.description).toContain("Every nonempty response page")
A4 line 17: expect(operation.description).toContain("including the final nonempty page")
A5 line 18: expect(operation.description).toContain("exclusive after={cursor}")
A6 line 19: expect(operation.description).toContain("Empty pages omit X-Next-Cursor")
A7 line 20: expect(operation.description).toContain("A short page does not")
A8 line 22: expect(response.content["application/json"].schema.type).toBe("array")
A9 line 24: expect(cursor.description).toContain(\n "highest created_sequence actually returned",\n )
A10 line 27: expect(cursor.description).toContain("omitted on empty pages")
A11 line 30: expect(cursor.required).not.toBe(true)
A12 line 32: expect(validate(cursor.example)).toBe(true)
Inputs are supplied indirectly through the cited fixture/helper; inspect it before reproduction.
RES-020 — conversation after schema reflects safe-integer validation and its decimal wire encoding
Field
Source-backed specification or observation
1. Test ID and name
RES-020 — conversation after schema reflects safe-integer validation and its decimal wire encoding
2. Requirement or guarantee
Source test intent: conversation after schema reflects safe-integer validation and its decimal wire encoding. Displayed assertions establish this test’s expected checks, not a separate system-wide guarantee.
3. Purpose and risk addressed
Detect regression of this named behaviour; complete business-impact/invariant analysis remains in the curated cases or follow-up review.
4. Priority
High — provisional catalogue triage; subject to risk review.
5. Test type
Contract — provisional grouping from the declaration name.
6. Preconditions
Use section C plus the cited file’s fixtures and setup/teardown hooks. Suite context: top level. Do not infer starting state from the title.
7. Input and test data
No each/for parameter table on this declaration; its callback may still generate inputs. Input/operation expressions: No direct request/operation expression extracted; inspect the source fixture/helper… Use disposable fixture data only.
8. Execution steps
1. Prepare the existing source test harness from section C. 2. Run pnpm test. 3. Locate this named declaration and its parameterized/conditional instances. 4. Compare the displayed assertions. 5. Record evidence and follow teardown. Not executed during this review.
9. Expected HTTP status, where applicable
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
10. Expected response headers and body
See assertions A1 below. Referenced variables remain symbolic; no universal response envelope is assumed.
11. Expected state changes
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
12. Expected emitted events or downstream calls, where applicable
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
13. Negative assertions: what must not happen
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
14. Cleanup and postconditions
Use the cited file’s hooks/finally blocks and section C. Restore mocks and remove only isolated test data.
15. Actual result
Not run — no execution evidence collected.
16. Evidence references
test/pagination-openapi.test.mjs:37; assertion/input source links below. Source key: test/pagination-openapi.test.mjs :: conversation after schema reflects safe-integer validation and its decimal wire encoding :: line 37 at this pinned revision.
17. Execution date
Not run.
18. Status and outstanding issues
Existing declaration documented; indirect helper assertions and full semantic coverage are not inferred from static extraction.
19. Category
Contract (provisional).
20. Handler, interface or code path
test/pagination-openapi.test.mjs:37; expressions No direct request/operation expression extracted; inspect the source fixture/helper… Imported modules: vitest, ajv/dist/2020.js, ../src/resources/openapi.ts.
21. Test implementation location and command
test/pagination-openapi.test.mjs:37 — conversation after schema reflects safe-integer validation and its decimal wire encoding. Run pnpm test from /home/johnny/projects/toastmachine-resources-worker after preparing its existing test environment; this invokes the suite.
22. Implementation status
Existing automated test
23. Execution status
Not run
24. Known limitations
Static source inventory only. Loops, parameter tables, shared helpers and conditional modifiers can change executed counts. Indirect helper assertions are not expanded.
25. Follow-up actions
Reconcile runtime instances with this declaration, review symbolic fixtures and unasserted effects, and record execution evidence. Preserve this ID.
Source test intent: agents retain numeric normalization inputs and describe response-driven short-page continuation. Displayed assertions establish this test’s expected checks, not a separate system-wide guarantee.
3. Purpose and risk addressed
Detect regression of this named behaviour; complete business-impact/invariant analysis remains in the curated cases or follow-up review.
4. Priority
High — provisional catalogue triage; subject to risk review.
5. Test type
Contract — provisional grouping from the declaration name.
6. Preconditions
Use section C plus the cited file’s fixtures and setup/teardown hooks. Suite context: top level. Do not infer starting state from the title.
7. Input and test data
No each/for parameter table on this declaration; its callback may still generate inputs. Input/operation expressions: No direct request/operation expression extracted; inspect the source fixture/helper… Use disposable fixture data only.
8. Execution steps
1. Prepare the existing source test harness from section C. 2. Run pnpm test. 3. Locate this named declaration and its parameterized/conditional instances. 4. Compare the displayed assertions. 5. Record evidence and follow teardown. Not executed during this review.
9. Expected HTTP status, where applicable
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
10. Expected response headers and body
See assertions A2, A7, A8, A10, A11, A12 below. Referenced variables remain symbolic; no universal response envelope is assumed.
11. Expected state changes
See assertions A7, A12, A13, A14 below. Expression grouping does not prove complete before/after state coverage.
12. Expected emitted events or downstream calls, where applicable
See assertions A2, A5 below. No delivery guarantee beyond the checked expressions is inferred.
13. Negative assertions: what must not happen
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
14. Cleanup and postconditions
Use the cited file’s hooks/finally blocks and section C. Restore mocks and remove only isolated test data.
15. Actual result
Not run — no execution evidence collected.
16. Evidence references
test/pagination-openapi.test.mjs:56; assertion/input source links below. Source key: test/pagination-openapi.test.mjs :: agents retain numeric normalization inputs and describe response-driven short-page continuation :: line 56 at this pinned revision.
17. Execution date
Not run.
18. Status and outstanding issues
Existing declaration documented; indirect helper assertions and full semantic coverage are not inferred from static extraction.
19. Category
Contract (provisional).
20. Handler, interface or code path
test/pagination-openapi.test.mjs:56; expressions No direct request/operation expression extracted; inspect the source fixture/helper… Imported modules: vitest, ajv/dist/2020.js, ../src/resources/openapi.ts.
21. Test implementation location and command
test/pagination-openapi.test.mjs:56 — agents retain numeric normalization inputs and describe response-driven short-page continuation. Run pnpm test from /home/johnny/projects/toastmachine-resources-worker after preparing its existing test environment; this invokes the suite.
22. Implementation status
Existing automated test
23. Execution status
Not run
24. Known limitations
Static source inventory only. Loops, parameter tables, shared helpers and conditional modifiers can change executed counts. Indirect helper assertions are not expanded.
25. Follow-up actions
Reconcile runtime instances with this declaration, review symbolic fixtures and unasserted effects, and record execution evidence. Preserve this ID.
Inputs are supplied indirectly through the cited fixture/helper; inspect it before reproduction.
test/public-archive.test.mjs
RES-022 — public archive contract pins format, complete membership, lineage and bounded byte retrieval
Field
Source-backed specification or observation
1. Test ID and name
RES-022 — public archive contract pins format, complete membership, lineage and bounded byte retrieval
2. Requirement or guarantee
Source test intent: public archive contract pins format, complete membership, lineage and bounded byte retrieval. Displayed assertions establish this test’s expected checks, not a separate system-wide guarantee.
3. Purpose and risk addressed
Detect regression of this named behaviour; complete business-impact/invariant analysis remains in the curated cases or follow-up review.
4. Priority
High — provisional catalogue triage; subject to risk review.
5. Test type
Contract — provisional grouping from the declaration name.
6. Preconditions
Use section C plus the cited file’s fixtures and setup/teardown hooks. Suite context: top level. Do not infer starting state from the title.
7. Input and test data
No each/for parameter table on this declaration; its callback may still generate inputs. Input/operation expressions: No direct request/operation expression extracted; inspect the source fixture/helper… Use disposable fixture data only.
8. Execution steps
1. Prepare the existing source test harness from section C. 2. Run pnpm test. 3. Locate this named declaration and its parameterized/conditional instances. 4. Compare the displayed assertions. 5. Record evidence and follow teardown. Not executed during this review.
9. Expected HTTP status, where applicable
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
10. Expected response headers and body
See assertions A5, A6, A7, A8 below. Referenced variables remain symbolic; no universal response envelope is assumed.
11. Expected state changes
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
12. Expected emitted events or downstream calls, where applicable
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
13. Negative assertions: what must not happen
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
14. Cleanup and postconditions
Use the cited file’s hooks/finally blocks and section C. Restore mocks and remove only isolated test data.
15. Actual result
Not run — no execution evidence collected.
16. Evidence references
test/public-archive.test.mjs:5; assertion/input source links below. Source key: test/public-archive.test.mjs :: public archive contract pins format, complete membership, lineage and bounded byte retrieval :: line 5 at this pinned revision.
17. Execution date
Not run.
18. Status and outstanding issues
Existing declaration documented; indirect helper assertions and full semantic coverage are not inferred from static extraction.
19. Category
Contract (provisional).
20. Handler, interface or code path
test/public-archive.test.mjs:5; expressions No direct request/operation expression extracted; inspect the source fixture/helper… Imported modules: vitest, ajv/dist/2020.js, ../scripts/generate-openapi.mjs.
21. Test implementation location and command
test/public-archive.test.mjs:5 — public archive contract pins format, complete membership, lineage and bounded byte retrieval. Run pnpm test from /home/johnny/projects/toastmachine-resources-worker after preparing its existing test environment; this invokes the suite.
22. Implementation status
Existing automated test
23. Execution status
Not run
24. Known limitations
Static source inventory only. Loops, parameter tables, shared helpers and conditional modifiers can change executed counts. Indirect helper assertions are not expanded.
25. Follow-up actions
Reconcile runtime instances with this declaration, review symbolic fixtures and unasserted effects, and record execution evidence. Preserve this ID.
A3 line 42: expect(check({ ...empty, archive_tip: 5, manifest })).toBe(true)
A4 line 55: expect(check({ ...empty, archive_tip: 5, manifest: changed })).toBe(false)
A5 line 58: expect(\n object.responses["200"].content["application/octet-stream"].schema[\n "x-max-bytes"\n ],\n ).toBe(4194304)
A6 line 64: expect(op.responses["200"].headers["X-Corpus-Id"].required).toBe(true)
A7 line 65: expect(op.responses["200"].headers["X-Corpus-Lineage"].required).toBe(true)
A8 line 66: expect(op.responses["503"].description).toContain("lineage_unavailable")
A9 line 68: expect(object.description).toContain("CRC32")
A10 line 69: expect(operation.description).toContain("Private recovery data is excluded")
Source inputs and operations
Inputs are supplied indirectly through the cited fixture/helper; inspect it before reproduction.
test/record-schemas.test.mjs
RES-023 — custom record schemas remain in place for SDK consumers and resolve strictly
Field
Source-backed specification or observation
1. Test ID and name
RES-023 — custom record schemas remain in place for SDK consumers and resolve strictly
2. Requirement or guarantee
Source test intent: custom record schemas remain in place for SDK consumers and resolve strictly. Displayed assertions establish this test’s expected checks, not a separate system-wide guarantee.
3. Purpose and risk addressed
Detect regression of this named behaviour; complete business-impact/invariant analysis remains in the curated cases or follow-up review.
4. Priority
High — provisional catalogue triage; subject to risk review.
5. Test type
Contract — provisional grouping from the declaration name.
6. Preconditions
Use section C plus the cited file’s fixtures and setup/teardown hooks. Suite context: top level. Do not infer starting state from the title.
7. Input and test data
No each/for parameter table on this declaration; its callback may still generate inputs. Input/operation expressions: No direct request/operation expression extracted; inspect the source fixture/helper… Use disposable fixture data only.
8. Execution steps
1. Prepare the existing source test harness from section C. 2. Run pnpm test. 3. Locate this named declaration and its parameterized/conditional instances. 4. Compare the displayed assertions. 5. Record evidence and follow teardown. Not executed during this review.
9. Expected HTTP status, where applicable
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
10. Expected response headers and body
See assertions A1, A2, A3, A4 below. Referenced variables remain symbolic; no universal response envelope is assumed.
11. Expected state changes
See assertions A1, A2, A3, A4 below. Expression grouping does not prove complete before/after state coverage.
12. Expected emitted events or downstream calls, where applicable
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
13. Negative assertions: what must not happen
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
14. Cleanup and postconditions
Use the cited file’s hooks/finally blocks and section C. Restore mocks and remove only isolated test data.
15. Actual result
Not run — no execution evidence collected.
16. Evidence references
test/record-schemas.test.mjs:9; assertion/input source links below. Source key: test/record-schemas.test.mjs :: custom record schemas remain in place for SDK consumers and resolve strictly :: line 9 at this pinned revision.
17. Execution date
Not run.
18. Status and outstanding issues
Existing declaration documented; indirect helper assertions and full semantic coverage are not inferred from static extraction.
19. Category
Contract (provisional).
20. Handler, interface or code path
test/record-schemas.test.mjs:9; expressions No direct request/operation expression extracted; inspect the source fixture/helper… Imported modules: vitest, ../src/resources/openapi.ts, ../scripts/validate-record-schemas.mjs.
21. Test implementation location and command
test/record-schemas.test.mjs:9 — custom record schemas remain in place for SDK consumers and resolve strictly. Run pnpm test from /home/johnny/projects/toastmachine-resources-worker after preparing its existing test environment; this invokes the suite.
22. Implementation status
Existing automated test
23. Execution status
Not run
24. Known limitations
Static source inventory only. Loops, parameter tables, shared helpers and conditional modifiers can change executed counts. Indirect helper assertions are not expanded.
25. Follow-up actions
Reconcile runtime instances with this declaration, review symbolic fixtures and unasserted effects, and record execution evidence. Preserve this ID.
Source assertions
A1 line 11: expect(validateRecordSchemas(spec)).toBe(5)
A2 line 20: expect(schema["x-record-schema"]).toEqual({\n $ref: `#/components/schemas/${name}`,\n })
A3 line 25: expect(() => validateRecordSchemas(broken)).toThrow(/resolve reference/)
A4 line 31: expect(() => validateRecordSchemas(malformed)).toThrow(/schema is invalid/)
Source inputs and operations
Inputs are supplied indirectly through the cited fixture/helper; inspect it before reproduction.
RES-024 — strict-ref exceptions do not suppress unrelated extension reference locations
Field
Source-backed specification or observation
1. Test ID and name
RES-024 — strict-ref exceptions do not suppress unrelated extension reference locations
2. Requirement or guarantee
Source test intent: strict-ref exceptions do not suppress unrelated extension reference locations. Displayed assertions establish this test’s expected checks, not a separate system-wide guarantee.
3. Purpose and risk addressed
Detect regression of this named behaviour; complete business-impact/invariant analysis remains in the curated cases or follow-up review.
4. Priority
High — provisional catalogue triage; subject to risk review.
5. Test type
Regression — provisional grouping from the declaration name.
6. Preconditions
Use section C plus the cited file’s fixtures and setup/teardown hooks. Suite context: top level. Do not infer starting state from the title.
7. Input and test data
No each/for parameter table on this declaration; its callback may still generate inputs. Input/operation expressions: No direct request/operation expression extracted; inspect the source fixture/helper… Use disposable fixture data only.
8. Execution steps
1. Prepare the existing source test harness from section C. 2. Run pnpm test. 3. Locate this named declaration and its parameterized/conditional instances. 4. Compare the displayed assertions. 5. Record evidence and follow teardown. Not executed during this review.
9. Expected HTTP status, where applicable
See assertions A2 below. A numeric schema/helper expectation is not automatically an HTTP response contract.
10. Expected response headers and body
See assertions A1, A2, A3, A4 below. Referenced variables remain symbolic; no universal response envelope is assumed.
11. Expected state changes
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
12. Expected emitted events or downstream calls, where applicable
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
13. Negative assertions: what must not happen
See assertions A1 below. Only the shown negative/rejection checks are claimed; other forbidden effects require review.
14. Cleanup and postconditions
Use the cited file’s hooks/finally blocks and section C. Restore mocks and remove only isolated test data.
15. Actual result
Not run — no execution evidence collected.
16. Evidence references
test/record-schemas.test.mjs:34; assertion/input source links below. Source key: test/record-schemas.test.mjs :: strict-ref exceptions do not suppress unrelated extension reference locations :: line 34 at this pinned revision.
17. Execution date
Not run.
18. Status and outstanding issues
Existing declaration documented; indirect helper assertions and full semantic coverage are not inferred from static extraction.
19. Category
Regression (provisional).
20. Handler, interface or code path
test/record-schemas.test.mjs:34; expressions No direct request/operation expression extracted; inspect the source fixture/helper… Imported modules: vitest, ../src/resources/openapi.ts, ../scripts/validate-record-schemas.mjs.
21. Test implementation location and command
test/record-schemas.test.mjs:34 — strict-ref exceptions do not suppress unrelated extension reference locations. Run pnpm test from /home/johnny/projects/toastmachine-resources-worker after preparing its existing test environment; this invokes the suite.
22. Implementation status
Existing automated test
23. Execution status
Not run
24. Known limitations
Static source inventory only. Loops, parameter tables, shared helpers and conditional modifiers can change executed counts. Indirect helper assertions are not expanded.
25. Follow-up actions
Reconcile runtime instances with this declaration, review symbolic fixtures and unasserted effects, and record execution evidence. Preserve this ID.
A3 line 65: expect(resultText).toContain("spec-strict-refs")
A4 line 66: expect(resultText).toContain("x-unreviewed")
Source inputs and operations
Inputs are supplied indirectly through the cited fixture/helper; inspect it before reproduction.
test/relationship-openapi.test.mjs
RES-025 — documents verification targets and rejection codes on applicable write paths
Field
Source-backed specification or observation
1. Test ID and name
RES-025 — documents verification targets and rejection codes on applicable write paths
2. Requirement or guarantee
Source test intent: documents verification targets and rejection codes on applicable write paths. Displayed assertions establish this test’s expected checks, not a separate system-wide guarantee.
3. Purpose and risk addressed
Detect regression of this named behaviour; complete business-impact/invariant analysis remains in the curated cases or follow-up review.
4. Priority
High — provisional catalogue triage; subject to risk review.
5. Test type
Contract — provisional grouping from the declaration name.
6. Preconditions
Use section C plus the cited file’s fixtures and setup/teardown hooks. Suite context: top level. Do not infer starting state from the title.
7. Input and test data
No each/for parameter table on this declaration; its callback may still generate inputs. Input/operation expressions: No direct request/operation expression extracted; inspect the source fixture/helper… Use disposable fixture data only.
8. Execution steps
1. Prepare the existing source test harness from section C. 2. Run pnpm test. 3. Locate this named declaration and its parameterized/conditional instances. 4. Compare the displayed assertions. 5. Record evidence and follow teardown. Not executed during this review.
9. Expected HTTP status, where applicable
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
10. Expected response headers and body
See assertions A1, A5, A7 below. Referenced variables remain symbolic; no universal response envelope is assumed.
11. Expected state changes
See assertions A4, A6 below. Expression grouping does not prove complete before/after state coverage.
12. Expected emitted events or downstream calls, where applicable
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
13. Negative assertions: what must not happen
See assertions A7 below. Only the shown negative/rejection checks are claimed; other forbidden effects require review.
14. Cleanup and postconditions
Use the cited file’s hooks/finally blocks and section C. Restore mocks and remove only isolated test data.
15. Actual result
Not run — no execution evidence collected.
16. Evidence references
test/relationship-openapi.test.mjs:37; assertion/input source links below. Source key: test/relationship-openapi.test.mjs :: documents verification targets and rejection codes on applicable write paths :: line 37 at this pinned revision.
17. Execution date
Not run.
18. Status and outstanding issues
Existing declaration documented; indirect helper assertions and full semantic coverage are not inferred from static extraction.
19. Category
Contract (provisional).
20. Handler, interface or code path
test/relationship-openapi.test.mjs:37; expressions No direct request/operation expression extracted; inspect the source fixture/helper… Imported modules: node:module, node:fs, vitest, ../src/resources/openapi.ts, ../src/resources/relationships.ts, ../src/protocol.ts.
21. Test implementation location and command
test/relationship-openapi.test.mjs:37 — documents verification targets and rejection codes on applicable write paths. Run pnpm test from /home/johnny/projects/toastmachine-resources-worker after preparing its existing test environment; this invokes the suite.
22. Implementation status
Existing automated test
23. Execution status
Not run
24. Known limitations
Static source inventory only. Loops, parameter tables, shared helpers and conditional modifiers can change executed counts. Indirect helper assertions are not expanded.
25. Follow-up actions
Reconcile runtime instances with this declaration, review symbolic fixtures and unasserted effects, and record execution evidence. Preserve this ID.
Source assertions
A1 line 42: expect(response.description).toContain(code)
A2 line 51: expect(create.description).toContain("authenticated asserting author")
A3 line 52: expect(create.description).toContain("must include kind claim")
A4 line 53: expect(create.description).toContain("Message creation")
A5 line 54: expect(\n spec.components.schemas.CreateRelationshipRequest.description,\n ).toContain("422 self_verification")
A6 line 61: expect(spec.paths[path].post.description).toContain("Message creation")
A7 line 62: expect(\n spec.paths["/{endpoint_id}/retractRelationship/{relationship_id}"].post\n .responses["422"],\n ).toBeUndefined()
Source inputs and operations
Inputs are supplied indirectly through the cited fixture/helper; inspect it before reproduction.
RES-026 — documents message withdrawal authority and read-derived supersession attribution
Field
Source-backed specification or observation
1. Test ID and name
RES-026 — documents message withdrawal authority and read-derived supersession attribution
2. Requirement or guarantee
Source test intent: documents message withdrawal authority and read-derived supersession attribution. Displayed assertions establish this test’s expected checks, not a separate system-wide guarantee.
3. Purpose and risk addressed
Detect regression of this named behaviour; complete business-impact/invariant analysis remains in the curated cases or follow-up review.
4. Priority
High — provisional catalogue triage; subject to risk review.
5. Test type
Security — provisional grouping from the declaration name.
6. Preconditions
Use section C plus the cited file’s fixtures and setup/teardown hooks. Suite context: top level. Do not infer starting state from the title.
7. Input and test data
No each/for parameter table on this declaration; its callback may still generate inputs. Input/operation expressions: I1, I2. Use disposable fixture data only.
8. Execution steps
1. Prepare the existing source test harness from section C. 2. Run pnpm test. 3. Locate this named declaration and its parameterized/conditional instances. 4. Compare the displayed assertions. 5. Record evidence and follow teardown. Not executed during this review.
9. Expected HTTP status, where applicable
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
10. Expected response headers and body
See assertions A1, A4, A7, A8, A9, A10 below. Referenced variables remain symbolic; no universal response envelope is assumed.
11. Expected state changes
See assertions A2 below. Expression grouping does not prove complete before/after state coverage.
12. Expected emitted events or downstream calls, where applicable
See assertions A3 below. No delivery guarantee beyond the checked expressions is inferred.
13. Negative assertions: what must not happen
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
14. Cleanup and postconditions
Use the cited file’s hooks/finally blocks and section C. Restore mocks and remove only isolated test data.
15. Actual result
Not run — no execution evidence collected.
16. Evidence references
test/relationship-openapi.test.mjs:68; assertion/input source links below. Source key: test/relationship-openapi.test.mjs :: documents message withdrawal authority and read-derived supersession attribution :: line 68 at this pinned revision.
17. Execution date
Not run.
18. Status and outstanding issues
Existing declaration documented; indirect helper assertions and full semantic coverage are not inferred from static extraction.
test/relationship-openapi.test.mjs:68 — documents message withdrawal authority and read-derived supersession attribution. Run pnpm test from /home/johnny/projects/toastmachine-resources-worker after preparing its existing test environment; this invokes the suite.
22. Implementation status
Existing automated test
23. Execution status
Not run
24. Known limitations
Static source inventory only. Loops, parameter tables, shared helpers and conditional modifiers can change executed counts. Indirect helper assertions are not expanded.
25. Follow-up actions
Reconcile runtime instances with this declaration, review symbolic fixtures and unasserted effects, and record execution evidence. Preserve this ID.
Source assertions
A1 line 71: expect(operation.responses["403"].description).toContain(\n "retraction_author_mismatch",\n )
A2 line 74: expect(operation.description).toContain(\n "Only the target message's original author may assert retracts",\n )
A3 line 77: expect(operation.description).toContain("Canonical change events")
A4 line 78: expect(spec.components.schemas.RelationshipTypeName.enum).toContain(\n "retracts",\n )
A6 line 95: expect(check({ ...supersedes, author_is_target_author: "true" })).toBe(false)
A7 line 106: expect(write({ ...body, author_is_target_author: true })).toBe(false)
A8 line 107: expect(write({ ...body, target_author_id: supersedes.author_id })).toBe(\n false,\n )
A9 line 110: expect(\n spec.components.schemas.RelationshipView.properties.relationship,\n ).toEqual(presentation)
A10 line 113: expect(\n spec.components.schemas.CreateRelationshipResponse.properties.relationship,\n ).toEqual(presentation)
Source inputs and operations
I1 line 106: write({ ...body, author_is_target_author: true })
I2 line 107: write({ ...body, target_author_id: supersedes.author_id })
RES-027 — publishes reusable relationship schemas and resolvable references throughout the public contract
Field
Source-backed specification or observation
1. Test ID and name
RES-027 — publishes reusable relationship schemas and resolvable references throughout the public contract
2. Requirement or guarantee
Source test intent: publishes reusable relationship schemas and resolvable references throughout the public contract. Displayed assertions establish this test’s expected checks, not a separate system-wide guarantee.
3. Purpose and risk addressed
Detect regression of this named behaviour; complete business-impact/invariant analysis remains in the curated cases or follow-up review.
4. Priority
High — provisional catalogue triage; subject to risk review.
5. Test type
Contract — provisional grouping from the declaration name.
6. Preconditions
Use section C plus the cited file’s fixtures and setup/teardown hooks. Suite context: top level. Do not infer starting state from the title.
7. Input and test data
No each/for parameter table on this declaration; its callback may still generate inputs. Input/operation expressions: No direct request/operation expression extracted; inspect the source fixture/helper… Use disposable fixture data only.
8. Execution steps
1. Prepare the existing source test harness from section C. 2. Run pnpm test. 3. Locate this named declaration and its parameterized/conditional instances. 4. Compare the displayed assertions. 5. Record evidence and follow teardown. Not executed during this review.
9. Expected HTTP status, where applicable
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
10. Expected response headers and body
See assertions A1, A3, A4, A7, A8, A9, A10, A11, A12, A13, A14, A18, A19 below. Referenced variables remain symbolic; no universal response envelope is assumed.
11. Expected state changes
See assertions A19 below. Expression grouping does not prove complete before/after state coverage.
12. Expected emitted events or downstream calls, where applicable
See assertions A20, A21 below. No delivery guarantee beyond the checked expressions is inferred.
13. Negative assertions: what must not happen
See assertions A2, A7 below. Only the shown negative/rejection checks are claimed; other forbidden effects require review.
14. Cleanup and postconditions
Use the cited file’s hooks/finally blocks and section C. Restore mocks and remove only isolated test data.
15. Actual result
Not run — no execution evidence collected.
16. Evidence references
test/relationship-openapi.test.mjs:118; assertion/input source links below. Source key: test/relationship-openapi.test.mjs :: publishes reusable relationship schemas and resolvable references throughout the public contract :: line 118 at this pinned revision.
17. Execution date
Not run.
18. Status and outstanding issues
Existing declaration documented; indirect helper assertions and full semantic coverage are not inferred from static extraction.
19. Category
Contract (provisional).
20. Handler, interface or code path
test/relationship-openapi.test.mjs:118; expressions No direct request/operation expression extracted; inspect the source fixture/helper… Imported modules: node:module, node:fs, vitest, ../src/resources/openapi.ts, ../src/resources/relationships.ts, ../src/protocol.ts.
21. Test implementation location and command
test/relationship-openapi.test.mjs:118 — publishes reusable relationship schemas and resolvable references throughout the public contract. Run pnpm test from /home/johnny/projects/toastmachine-resources-worker after preparing its existing test environment; this invokes the suite.
22. Implementation status
Existing automated test
23. Execution status
Not run
24. Known limitations
Static source inventory only. Loops, parameter tables, shared helpers and conditional modifiers can change executed counts. Indirect helper assertions are not expanded.
25. Follow-up actions
Reconcile runtime instances with this declaration, review symbolic fixtures and unasserted effects, and record execution evidence. Preserve this ID.
Source assertions
A1 line 135: expect(spec.components.schemas[name]).toBeDefined()
Inputs are supplied indirectly through the cited fixture/helper; inspect it before reproduction.
RES-028 — catalogue schemas match every runtime representation and current request validation
Field
Source-backed specification or observation
1. Test ID and name
RES-028 — catalogue schemas match every runtime representation and current request validation
2. Requirement or guarantee
Source test intent: catalogue schemas match every runtime representation and current request validation. Displayed assertions establish this test’s expected checks, not a separate system-wide guarantee.
3. Purpose and risk addressed
Detect regression of this named behaviour; complete business-impact/invariant analysis remains in the curated cases or follow-up review.
4. Priority
High — provisional catalogue triage; subject to risk review.
5. Test type
Contract — provisional grouping from the declaration name.
6. Preconditions
Use section C plus the cited file’s fixtures and setup/teardown hooks. Suite context: top level. Do not infer starting state from the title.
7. Input and test data
No each/for parameter table on this declaration; its callback may still generate inputs. Input/operation expressions: I1. Use disposable fixture data only.
8. Execution steps
1. Prepare the existing source test harness from section C. 2. Run pnpm test. 3. Locate this named declaration and its parameterized/conditional instances. 4. Compare the displayed assertions. 5. Record evidence and follow teardown. Not executed during this review.
9. Expected HTTP status, where applicable
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
10. Expected response headers and body
See assertions A2, A3 below. Referenced variables remain symbolic; no universal response envelope is assumed.
11. Expected state changes
See assertions A2 below. Expression grouping does not prove complete before/after state coverage.
12. Expected emitted events or downstream calls, where applicable
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
13. Negative assertions: what must not happen
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
14. Cleanup and postconditions
Use the cited file’s hooks/finally blocks and section C. Restore mocks and remove only isolated test data.
15. Actual result
Not run — no execution evidence collected.
16. Evidence references
test/relationship-openapi.test.mjs:225; assertion/input source links below. Source key: test/relationship-openapi.test.mjs :: catalogue schemas match every runtime representation and current request validation :: line 225 at this pinned revision.
17. Execution date
Not run.
18. Status and outstanding issues
Existing declaration documented; indirect helper assertions and full semantic coverage are not inferred from static extraction.
test/relationship-openapi.test.mjs:225 — catalogue schemas match every runtime representation and current request validation. Run pnpm test from /home/johnny/projects/toastmachine-resources-worker after preparing its existing test environment; this invokes the suite.
22. Implementation status
Existing automated test
23. Execution status
Not run
24. Known limitations
Static source inventory only. Loops, parameter tables, shared helpers and conditional modifiers can change executed counts. Indirect helper assertions are not expanded.
25. Follow-up actions
Reconcile runtime instances with this declaration, review symbolic fixtures and unasserted effects, and record execution evidence. Preserve this ID.
Source assertions
A1 line 237: expect(payload.relationship_types).toEqual(\n RELATIONSHIP_CATALOGUE.relationship_types,\n )
A2 line 240: expect(Object.keys(payload).filter((k) => !k.startsWith("@"))).toEqual([\n ...spec.components.schemas.RelationshipCatalogue.required,\n ])
A3 line 244: expect(spec.components.schemas.RelationshipTypeName.enum).toEqual(\n RELATIONSHIP_CATALOGUE.relationship_types.map((t) => t.relationship_type),\n )
I1 line 229: new Request(`${config.base_url}/relationships`, {\n headers: { Accept: media },\n })
RES-029 — canonical schemas match Corpus reads, query envelopes, JSON-LD, errors and serialized JSONL records
Field
Source-backed specification or observation
1. Test ID and name
RES-029 — canonical schemas match Corpus reads, query envelopes, JSON-LD, errors and serialized JSONL records
2. Requirement or guarantee
Source test intent: canonical schemas match Corpus reads, query envelopes, JSON-LD, errors and serialized JSONL records. Displayed assertions establish this test’s expected checks, not a separate system-wide guarantee.
3. Purpose and risk addressed
Detect regression of this named behaviour; complete business-impact/invariant analysis remains in the curated cases or follow-up review.
4. Priority
High — provisional catalogue triage; subject to risk review.
5. Test type
Contract — provisional grouping from the declaration name.
6. Preconditions
Use section C plus the cited file’s fixtures and setup/teardown hooks. Suite context: top level. Do not infer starting state from the title.
7. Input and test data
skipIf: !existsSync(new URL("routes/relationships.ts", corpusRoot)) Input/operation expressions: I1, I2, I3, I4, I5, I6. Use disposable fixture data only.
8. Execution steps
1. Prepare the existing source test harness from section C. 2. Run pnpm test. 3. Locate this named declaration and its parameterized/conditional instances. 4. Compare the displayed assertions. 5. Record evidence and follow teardown. Not executed during this review.
9. Expected HTTP status, where applicable
See assertions A1, A5, A8 below. A numeric schema/helper expectation is not automatically an HTTP response contract.
10. Expected response headers and body
See assertions A1, A3, A5, A6 below. Referenced variables remain symbolic; no universal response envelope is assumed.
11. Expected state changes
See assertions A3, A4, A7, A10 below. Expression grouping does not prove complete before/after state coverage.
12. Expected emitted events or downstream calls, where applicable
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
13. Negative assertions: what must not happen
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
14. Cleanup and postconditions
Use the cited file’s hooks/finally blocks and section C. Restore mocks and remove only isolated test data.
15. Actual result
Not run — no execution evidence collected.
16. Evidence references
test/relationship-openapi.test.mjs:283; assertion/input source links below. Source key: test/relationship-openapi.test.mjs :: canonical schemas match Corpus reads, query envelopes, JSON-LD, errors and serialized JSONL records :: line 283 at this pinned revision.
17. Execution date
Not run.
18. Status and outstanding issues
Existing declaration documented; indirect helper assertions and full semantic coverage are not inferred from static extraction.
test/relationship-openapi.test.mjs:283 — canonical schemas match Corpus reads, query envelopes, JSON-LD, errors and serialized JSONL records. Run pnpm test from /home/johnny/projects/toastmachine-resources-worker after preparing its existing test environment; this invokes the suite.
22. Implementation status
Existing automated test
23. Execution status
Not run
24. Known limitations
Static source inventory only. Loops, parameter tables, shared helpers and conditional modifiers can change executed counts. Conditional/skip modifier present. Indirect helper assertions are not expanded.
25. Follow-up actions
Reconcile runtime instances with this declaration, review symbolic fixtures and unasserted effects, and record execution evidence. Preserve this ID.
I6 line 448: new Request(\n `${config.base_url}/relationship-assertions?direction=invalid`,\n )
RES-030 — public retraction operations identify different targets and authorities
Field
Source-backed specification or observation
1. Test ID and name
RES-030 — public retraction operations identify different targets and authorities
2. Requirement or guarantee
Source test intent: public retraction operations identify different targets and authorities. Displayed assertions establish this test’s expected checks, not a separate system-wide guarantee.
3. Purpose and risk addressed
Detect regression of this named behaviour; complete business-impact/invariant analysis remains in the curated cases or follow-up review.
4. Priority
High — provisional catalogue triage; subject to risk review.
5. Test type
Security — provisional grouping from the declaration name.
6. Preconditions
Use section C plus the cited file’s fixtures and setup/teardown hooks. Suite context: top level. Do not infer starting state from the title.
7. Input and test data
No each/for parameter table on this declaration; its callback may still generate inputs. Input/operation expressions: I1. Use disposable fixture data only.
8. Execution steps
1. Prepare the existing source test harness from section C. 2. Run pnpm test. 3. Locate this named declaration and its parameterized/conditional instances. 4. Compare the displayed assertions. 5. Record evidence and follow teardown. Not executed during this review.
9. Expected HTTP status, where applicable
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
10. Expected response headers and body
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
11. Expected state changes
See assertions A3, A4, A6 below. Expression grouping does not prove complete before/after state coverage.
12. Expected emitted events or downstream calls, where applicable
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
13. Negative assertions: what must not happen
See assertions A1 below. Only the shown negative/rejection checks are claimed; other forbidden effects require review.
14. Cleanup and postconditions
Use the cited file’s hooks/finally blocks and section C. Restore mocks and remove only isolated test data.
15. Actual result
Not run — no execution evidence collected.
16. Evidence references
test/relationship-openapi.test.mjs:472; assertion/input source links below. Source key: test/relationship-openapi.test.mjs :: public retraction operations identify different targets and authorities :: line 472 at this pinned revision.
17. Execution date
Not run.
18. Status and outstanding issues
Existing declaration documented; indirect helper assertions and full semantic coverage are not inferred from static extraction.
test/relationship-openapi.test.mjs:472 — public retraction operations identify different targets and authorities. Run pnpm test from /home/johnny/projects/toastmachine-resources-worker after preparing its existing test environment; this invokes the suite.
22. Implementation status
Existing automated test
23. Execution status
Not run
24. Known limitations
Static source inventory only. Loops, parameter tables, shared helpers and conditional modifiers can change executed counts. Indirect helper assertions are not expanded.
25. Follow-up actions
Reconcile runtime instances with this declaration, review symbolic fixtures and unasserted effects, and record execution evidence. Preserve this ID.
Source assertions
A1 line 477: expect(create.summary).not.toBe(retract.summary)
A2 line 478: expect(create.description).toContain("A --retracts--> B")
A3 line 479: expect(create.description).toContain("target message's original author")
A4 line 480: expect(retract.description).toContain(\n "Targets relationship_id, not a message",\n )
A5 line 483: expect(retract.description).toContain(\n "Only the authenticated asserting author",\n )
A6 line 486: expect(retract.description).toContain(\n "preserves the assertion, both messages and their history",\n )
A7 line 489: expect(retract.description).toContain("This does not create a retracts")
A8 line 495: expect(catalogue).toContain(\n "distinct from withdrawing a relationship assertion via retractRelationship",\n )
A9 line 498: expect(catalogue).toContain("false does not authorize editing the target")
A10 line 499: expect(catalogue).toContain(\n "Consumers must evaluate the assertion and its provenance themselves",\n )
Source inputs and operations
I1 line 491: new Request(`${config.base_url}/relationships`, {\n headers: { Accept: "text/markdown" },\n })
RES-031 — OpenAPI and packaged MCP guidance agree on relationship-based replies and authority
Field
Source-backed specification or observation
1. Test ID and name
RES-031 — OpenAPI and packaged MCP guidance agree on relationship-based replies and authority
2. Requirement or guarantee
Source test intent: OpenAPI and packaged MCP guidance agree on relationship-based replies and authority. Displayed assertions establish this test’s expected checks, not a separate system-wide guarantee.
3. Purpose and risk addressed
Detect regression of this named behaviour; complete business-impact/invariant analysis remains in the curated cases or follow-up review.
4. Priority
High — provisional catalogue triage; subject to risk review.
5. Test type
Security — provisional grouping from the declaration name.
6. Preconditions
Use section C plus the cited file’s fixtures and setup/teardown hooks. Suite context: top level. Do not infer starting state from the title.
7. Input and test data
skipIf: !existsSync(new URL("guide.ts", mcpRoot)) Input/operation expressions: No direct request/operation expression extracted; inspect the source fixture/helper… Use disposable fixture data only.
8. Execution steps
1. Prepare the existing source test harness from section C. 2. Run pnpm test. 3. Locate this named declaration and its parameterized/conditional instances. 4. Compare the displayed assertions. 5. Record evidence and follow teardown. Not executed during this review.
9. Expected HTTP status, where applicable
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
10. Expected response headers and body
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
11. Expected state changes
See assertions A5 below. Expression grouping does not prove complete before/after state coverage.
12. Expected emitted events or downstream calls, where applicable
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
13. Negative assertions: what must not happen
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
14. Cleanup and postconditions
Use the cited file’s hooks/finally blocks and section C. Restore mocks and remove only isolated test data.
15. Actual result
Not run — no execution evidence collected.
16. Evidence references
test/relationship-openapi.test.mjs:505; assertion/input source links below. Source key: test/relationship-openapi.test.mjs :: OpenAPI and packaged MCP guidance agree on relationship-based replies and authority :: line 505 at this pinned revision.
17. Execution date
Not run.
18. Status and outstanding issues
Existing declaration documented; indirect helper assertions and full semantic coverage are not inferred from static extraction.
19. Category
Security (provisional).
20. Handler, interface or code path
test/relationship-openapi.test.mjs:505; expressions No direct request/operation expression extracted; inspect the source fixture/helper… Imported modules: node:module, node:fs, vitest, ../src/resources/openapi.ts, ../src/resources/relationships.ts, ../src/protocol.ts.
21. Test implementation location and command
test/relationship-openapi.test.mjs:505 — OpenAPI and packaged MCP guidance agree on relationship-based replies and authority. Run pnpm test from /home/johnny/projects/toastmachine-resources-worker after preparing its existing test environment; this invokes the suite.
22. Implementation status
Existing automated test
23. Execution status
Not run
24. Known limitations
Static source inventory only. Loops, parameter tables, shared helpers and conditional modifiers can change executed counts. Conditional/skip modifier present. Indirect helper assertions are not expanded.
25. Follow-up actions
Reconcile runtime instances with this declaration, review symbolic fixtures and unasserted effects, and record execution evidence. Preserve this ID.
Source assertions
A1 line 516: expect(description).toContain(RELATIONSHIP_GUIDANCE)
A2 line 517: expect(HOW_TO_USE_GUIDE).toContain(RELATIONSHIP_GUIDANCE)
A3 line 518: expect(HOW_TO_USE_GUIDE).toContain('relationship_type = "replies-to"')
A4 line 519: expect(HOW_TO_USE_GUIDE).toContain(\n "separate saved relationship operation token",\n )
A5 line 526: expect(spec.paths[path].post.description).toContain(\n "Create a message and its replies-to assertion separately",\n )
Source inputs and operations
Inputs are supplied indirectly through the cited fixture/helper; inspect it before reproduction.
RES-032 — agent-profile error bodies conform to the generated OpenAPI structured contract
Field
Source-backed specification or observation
1. Test ID and name
RES-032 — agent-profile error bodies conform to the generated OpenAPI structured contract
2. Requirement or guarantee
Source test intent: agent-profile error bodies conform to the generated OpenAPI structured contract. Displayed assertions establish this test’s expected checks, not a separate system-wide guarantee.
3. Purpose and risk addressed
Detect regression of this named behaviour; complete business-impact/invariant analysis remains in the curated cases or follow-up review.
4. Priority
High — provisional catalogue triage; subject to risk review.
5. Test type
Contract — provisional grouping from the declaration name.
6. Preconditions
Use section C plus the cited file’s fixtures and setup/teardown hooks. Suite context: top level. Do not infer starting state from the title.
7. Input and test data
skipIf: !existsSync(new URL("routes/agents.ts", corpusRoot)) Input/operation expressions: I1. Use disposable fixture data only.
8. Execution steps
1. Prepare the existing source test harness from section C. 2. Run pnpm test. 3. Locate this named declaration and its parameterized/conditional instances. 4. Compare the displayed assertions. 5. Record evidence and follow teardown. Not executed during this review.
9. Expected HTTP status, where applicable
See assertions A1 below. A numeric schema/helper expectation is not automatically an HTTP response contract.
10. Expected response headers and body
See assertions A1, A2, A3, A4, A5, A6 below. Referenced variables remain symbolic; no universal response envelope is assumed.
11. Expected state changes
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
12. Expected emitted events or downstream calls, where applicable
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
13. Negative assertions: what must not happen
See assertions A6 below. Only the shown negative/rejection checks are claimed; other forbidden effects require review.
14. Cleanup and postconditions
Use the cited file’s hooks/finally blocks and section C. Restore mocks and remove only isolated test data.
15. Actual result
Not run — no execution evidence collected.
16. Evidence references
test/relationship-openapi.test.mjs:532; assertion/input source links below. Source key: test/relationship-openapi.test.mjs :: agent-profile error bodies conform to the generated OpenAPI structured contract :: line 532 at this pinned revision.
17. Execution date
Not run.
18. Status and outstanding issues
Existing declaration documented; indirect helper assertions and full semantic coverage are not inferred from static extraction.
test/relationship-openapi.test.mjs:532 — agent-profile error bodies conform to the generated OpenAPI structured contract. Run pnpm test from /home/johnny/projects/toastmachine-resources-worker after preparing its existing test environment; this invokes the suite.
22. Implementation status
Existing automated test
23. Execution status
Not run
24. Known limitations
Static source inventory only. Loops, parameter tables, shared helpers and conditional modifiers can change executed counts. Conditional/skip modifier present. Indirect helper assertions are not expanded.
25. Follow-up actions
Reconcile runtime instances with this declaration, review symbolic fixtures and unasserted effects, and record execution evidence. Preserve this ID.
Source test intent: documents MCP-only response estimates without changing native HTTP message contracts. Displayed assertions establish this test’s expected checks, not a separate system-wide guarantee.
3. Purpose and risk addressed
Detect regression of this named behaviour; complete business-impact/invariant analysis remains in the curated cases or follow-up review.
4. Priority
High — provisional catalogue triage; subject to risk review.
5. Test type
Contract — provisional grouping from the declaration name.
6. Preconditions
Use section C plus the cited file’s fixtures and setup/teardown hooks. Suite context: top level. Do not infer starting state from the title.
7. Input and test data
No each/for parameter table on this declaration; its callback may still generate inputs. Input/operation expressions: No direct request/operation expression extracted; inspect the source fixture/helper… Use disposable fixture data only.
8. Execution steps
1. Prepare the existing source test harness from section C. 2. Run pnpm test. 3. Locate this named declaration and its parameterized/conditional instances. 4. Compare the displayed assertions. 5. Record evidence and follow teardown. Not executed during this review.
9. Expected HTTP status, where applicable
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
10. Expected response headers and body
See assertions A6, A9, A12 below. Referenced variables remain symbolic; no universal response envelope is assumed.
11. Expected state changes
See assertions A5, A10, A12 below. Expression grouping does not prove complete before/after state coverage.
12. Expected emitted events or downstream calls, where applicable
See assertions A5 below. No delivery guarantee beyond the checked expressions is inferred.
13. Negative assertions: what must not happen
See assertions A6 below. Only the shown negative/rejection checks are claimed; other forbidden effects require review.
14. Cleanup and postconditions
Use the cited file’s hooks/finally blocks and section C. Restore mocks and remove only isolated test data.
15. Actual result
Not run — no execution evidence collected.
16. Evidence references
test/retrieval-size.test.mjs:37; assertion/input source links below. Source key: test/retrieval-size.test.mjs :: documents MCP-only response estimates without changing native HTTP message contracts :: line 37 at this pinned revision.
17. Execution date
Not run.
18. Status and outstanding issues
Existing declaration documented; indirect helper assertions and full semantic coverage are not inferred from static extraction.
19. Category
Contract (provisional).
20. Handler, interface or code path
test/retrieval-size.test.mjs:37; expressions No direct request/operation expression extracted; inspect the source fixture/helper… Imported modules: node:fs, vitest, ajv/dist/2020.js, ../src/resources/openapi.ts, ../src/guide.ts, ../src/resources/llms.ts, ../src/resources/llms-full.ts.
21. Test implementation location and command
test/retrieval-size.test.mjs:37 — documents MCP-only response estimates without changing native HTTP message contracts. Run pnpm test from /home/johnny/projects/toastmachine-resources-worker after preparing its existing test environment; this invokes the suite.
22. Implementation status
Existing automated test
23. Execution status
Not run
24. Known limitations
Static source inventory only. Loops, parameter tables, shared helpers and conditional modifiers can change executed counts. Indirect helper assertions are not expanded.
25. Follow-up actions
Reconcile runtime instances with this declaration, review symbolic fixtures and unasserted effects, and record execution evidence. Preserve this ID.
A2 line 41: expect(contract.estimation_method).toBe(method)
A3 line 42: expect(contract.description).toContain("excluding retrieval_size")
A4 line 43: expect(contract.description).toContain("ceil(serialized_bytes/4)")
A5 line 44: expect(contract.description).toContain(\n "HTTP resource bodies and stored messages/events are unchanged",\n )
A6 line 48: expect(schema.properties ?? {}).not.toHaveProperty("retrieval_size")
A7 line 49: expect(HOW_TO_USE_GUIDE).toContain(`\`${name}\``)
A8 line 50: expect(HOW_TO_USE_GUIDE).toContain(method)
A9 line 51: expect(HOW_TO_USE_GUIDE).toContain("omitted on errors")
A10 line 52: expect(HOW_TO_USE_GUIDE).toContain("not a model-tokenizer count")
A11 line 53: expect(HOW_TO_USE_GUIDE).toContain("Estimates do not trigger truncation")
A12 line 54: expect(\n spec.components.schemas.Message.properties.payload[\n "x-max-canonical-utf8-bytes"\n ],\n ).toBe(65536)
Source inputs and operations
Inputs are supplied indirectly through the cited fixture/helper; inspect it before reproduction.
RES-034 — both generated machine guides publish the same typed MCP-only contract as the usage guide
Field
Source-backed specification or observation
1. Test ID and name
RES-034 — both generated machine guides publish the same typed MCP-only contract as the usage guide
2. Requirement or guarantee
Source test intent: both generated machine guides publish the same typed MCP-only contract as the usage guide. Displayed assertions establish this test’s expected checks, not a separate system-wide guarantee.
3. Purpose and risk addressed
Detect regression of this named behaviour; complete business-impact/invariant analysis remains in the curated cases or follow-up review.
4. Priority
High — provisional catalogue triage; subject to risk review.
5. Test type
Contract — provisional grouping from the declaration name.
6. Preconditions
Use section C plus the cited file’s fixtures and setup/teardown hooks. Suite context: top level. Do not infer starting state from the title.
7. Input and test data
No each/for parameter table on this declaration; its callback may still generate inputs. Input/operation expressions: No direct request/operation expression extracted; inspect the source fixture/helper… Use disposable fixture data only.
8. Execution steps
1. Prepare the existing source test harness from section C. 2. Run pnpm test. 3. Locate this named declaration and its parameterized/conditional instances. 4. Compare the displayed assertions. 5. Record evidence and follow teardown. Not executed during this review.
9. Expected HTTP status, where applicable
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
10. Expected response headers and body
See assertions A1 below. Referenced variables remain symbolic; no universal response envelope is assumed.
11. Expected state changes
See assertions A8 below. Expression grouping does not prove complete before/after state coverage.
12. Expected emitted events or downstream calls, where applicable
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
13. Negative assertions: what must not happen
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
14. Cleanup and postconditions
Use the cited file’s hooks/finally blocks and section C. Restore mocks and remove only isolated test data.
15. Actual result
Not run — no execution evidence collected.
16. Evidence references
test/retrieval-size.test.mjs:61; assertion/input source links below. Source key: test/retrieval-size.test.mjs :: both generated machine guides publish the same typed MCP-only contract as the usage guide :: line 61 at this pinned revision.
17. Execution date
Not run.
18. Status and outstanding issues
Existing declaration documented; indirect helper assertions and full semantic coverage are not inferred from static extraction.
19. Category
Contract (provisional).
20. Handler, interface or code path
test/retrieval-size.test.mjs:61; expressions No direct request/operation expression extracted; inspect the source fixture/helper… Imported modules: node:fs, vitest, ajv/dist/2020.js, ../src/resources/openapi.ts, ../src/guide.ts, ../src/resources/llms.ts, ../src/resources/llms-full.ts.
21. Test implementation location and command
test/retrieval-size.test.mjs:61 — both generated machine guides publish the same typed MCP-only contract as the usage guide. Run pnpm test from /home/johnny/projects/toastmachine-resources-worker after preparing its existing test environment; this invokes the suite.
22. Implementation status
Existing automated test
23. Execution status
Not run
24. Known limitations
Static source inventory only. Loops, parameter tables, shared helpers and conditional modifiers can change executed counts. Indirect helper assertions are not expanded.
25. Follow-up actions
Reconcile runtime instances with this declaration, review symbolic fixtures and unasserted effects, and record execution evidence. Preserve this ID.
Source assertions
A1 line 63: expect(response.headers.get("Content-Type")).toContain("text/plain")
A2 line 65: expect(text).toContain(MCP_RETRIEVAL_SIZE_DOCUMENTATION)
A4 line 68: expect(text).toContain(`\`${field}\` (non-negative integer)`)
A5 line 69: expect(text).toContain("compact JSON serialization")
A6 line 70: expect(text).toContain("top-level `retrieval_size` field omitted")
A7 line 71: expect(text).toContain("ceil(serialized_bytes / 4)")
A8 line 72: expect(text).toContain("not a model-tokenizer count")
A9 line 73: expect(text).toContain(\n "duplicate text/structured copy, MCP/HTTP envelopes",\n )
A10 line 76: expect(text).toContain(\n "Other tools and raw HTTP resource bodies do not expose it",\n )
A11 line 80: expect(HOW_TO_USE_GUIDE).toContain(MCP_RETRIEVAL_SIZE_DOCUMENTATION)
A12 line 81: expect(MCP_RETRIEVAL_SIZE_DOCUMENTATION).toContain(\n "this documentation does not verify a deployment",\n )
Source inputs and operations
Inputs are supplied indirectly through the cited fixture/helper; inspect it before reproduction.
RES-035 — MCP output schemas, OpenAPI extension and both guides agree on the estimate contract
Field
Source-backed specification or observation
1. Test ID and name
RES-035 — MCP output schemas, OpenAPI extension and both guides agree on the estimate contract
2. Requirement or guarantee
Source test intent: MCP output schemas, OpenAPI extension and both guides agree on the estimate contract. Displayed assertions establish this test’s expected checks, not a separate system-wide guarantee.
3. Purpose and risk addressed
Detect regression of this named behaviour; complete business-impact/invariant analysis remains in the curated cases or follow-up review.
4. Priority
High — provisional catalogue triage; subject to risk review.
5. Test type
Contract — provisional grouping from the declaration name.
6. Preconditions
Use section C plus the cited file’s fixtures and setup/teardown hooks. Suite context: top level. Do not infer starting state from the title.
7. Input and test data
skipIf: !existsSync(new URL("retrieval-size.ts", mcpRoot)) Input/operation expressions: No direct request/operation expression extracted; inspect the source fixture/helper… Use disposable fixture data only.
8. Execution steps
1. Prepare the existing source test harness from section C. 2. Run pnpm test. 3. Locate this named declaration and its parameterized/conditional instances. 4. Compare the displayed assertions. 5. Record evidence and follow teardown. Not executed during this review.
9. Expected HTTP status, where applicable
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
10. Expected response headers and body
See assertions A4, A7, A10, A11 below. Referenced variables remain symbolic; no universal response envelope is assumed.
11. Expected state changes
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
12. Expected emitted events or downstream calls, where applicable
See assertions A6 below. No delivery guarantee beyond the checked expressions is inferred.
13. Negative assertions: what must not happen
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
14. Cleanup and postconditions
Use the cited file’s hooks/finally blocks and section C. Restore mocks and remove only isolated test data.
15. Actual result
Not run — no execution evidence collected.
16. Evidence references
test/retrieval-size.test.mjs:87; assertion/input source links below. Source key: test/retrieval-size.test.mjs :: MCP output schemas, OpenAPI extension and both guides agree on the estimate contract :: line 87 at this pinned revision.
17. Execution date
Not run.
18. Status and outstanding issues
Existing declaration documented; indirect helper assertions and full semantic coverage are not inferred from static extraction.
19. Category
Contract (provisional).
20. Handler, interface or code path
test/retrieval-size.test.mjs:87; expressions No direct request/operation expression extracted; inspect the source fixture/helper… Imported modules: node:fs, vitest, ajv/dist/2020.js, ../src/resources/openapi.ts, ../src/guide.ts, ../src/resources/llms.ts, ../src/resources/llms-full.ts.
21. Test implementation location and command
test/retrieval-size.test.mjs:87 — MCP output schemas, OpenAPI extension and both guides agree on the estimate contract. Run pnpm test from /home/johnny/projects/toastmachine-resources-worker after preparing its existing test environment; this invokes the suite.
22. Implementation status
Existing automated test
23. Execution status
Not run
24. Known limitations
Static source inventory only. Loops, parameter tables, shared helpers and conditional modifiers can change executed counts. Conditional/skip modifier present. Indirect helper assertions are not expanded.
25. Follow-up actions
Reconcile runtime instances with this declaration, review symbolic fixtures and unasserted effects, and record execution evidence. Preserve this ID.
Source assertions
A1 line 100: expect(mcpGuide).toBe(HOW_TO_USE_GUIDE)
A2 line 116: expect(reporting.map(({ name }) => name).sort()).toEqual([...tools].sort())
A3 line 117: expect(spec["x-toastmachine-mcp"].retrieval_size.estimation_method).toBe(\n RETRIEVAL_SIZE_METHOD,\n )
A4 line 193: expect(\n check(withRetrievalSize(bases[name])),\n `${name}: ${JSON.stringify(check.errors)}`,\n ).toBe(true)
A5 line 197: expect(check(bases[name]), name).toBe(false)
A6 line 201: expect(withoutDescriptions(actual)).toEqual(\n withoutDescriptions(published),\n )
A7 line 208: expect(\n validateMetadata(reported.retrieval_size),\n JSON.stringify(validateMetadata.errors),\n ).toBe(true)
A8 line 215: expect(reported.retrieval_size.serialized_bytes).toBe(serialized)
A9 line 216: expect(reported.retrieval_size.estimated_tokens).toBe(\n Math.ceil(serialized / 4),\n )
A10 line 221: expect(validate(reported), JSON.stringify(validate.errors)).toBe(true)
A12 line 229: expect(validate({ ...reported, retrieval_size: invalid })).toBe(false)
Source inputs and operations
Inputs are supplied indirectly through the cited fixture/helper; inspect it before reproduction.
test/review-findings.test.mjs
RES-036 — canonical discovery enumerates all immutable payload versions with complete schemas
Field
Source-backed specification or observation
1. Test ID and name
RES-036 — canonical discovery enumerates all immutable payload versions with complete schemas
2. Requirement or guarantee
Source test intent: canonical discovery enumerates all immutable payload versions with complete schemas. Displayed assertions establish this test’s expected checks, not a separate system-wide guarantee.
3. Purpose and risk addressed
Detect regression of this named behaviour; complete business-impact/invariant analysis remains in the curated cases or follow-up review.
4. Priority
High — provisional catalogue triage; subject to risk review.
5. Test type
Contract — provisional grouping from the declaration name.
6. Preconditions
Use section C plus the cited file’s fixtures and setup/teardown hooks. Suite context: top level. Do not infer starting state from the title.
7. Input and test data
No each/for parameter table on this declaration; its callback may still generate inputs. Input/operation expressions: No direct request/operation expression extracted; inspect the source fixture/helper… Use disposable fixture data only.
8. Execution steps
1. Prepare the existing source test harness from section C. 2. Run pnpm test. 3. Locate this named declaration and its parameterized/conditional instances. 4. Compare the displayed assertions. 5. Record evidence and follow teardown. Not executed during this review.
9. Expected HTTP status, where applicable
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
10. Expected response headers and body
See assertions A1, A5, A6 below. Referenced variables remain symbolic; no universal response envelope is assumed.
11. Expected state changes
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
12. Expected emitted events or downstream calls, where applicable
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
13. Negative assertions: what must not happen
See assertions A5 below. Only the shown negative/rejection checks are claimed; other forbidden effects require review.
14. Cleanup and postconditions
Use the cited file’s hooks/finally blocks and section C. Restore mocks and remove only isolated test data.
15. Actual result
Not run — no execution evidence collected.
16. Evidence references
test/review-findings.test.mjs:13; assertion/input source links below. Source key: test/review-findings.test.mjs :: canonical discovery enumerates all immutable payload versions with complete schemas :: line 13 at this pinned revision.
17. Execution date
Not run.
18. Status and outstanding issues
Existing declaration documented; indirect helper assertions and full semantic coverage are not inferred from static extraction.
19. Category
Contract (provisional).
20. Handler, interface or code path
test/review-findings.test.mjs:13; expressions No direct request/operation expression extracted; inspect the source fixture/helper… Imported modules: node:fs, vitest, ../src/schema-catalogue.json, ../src/resources/service.ts, ../src/resources/openapi.ts, ../src/guide.ts.
21. Test implementation location and command
test/review-findings.test.mjs:13 — canonical discovery enumerates all immutable payload versions with complete schemas. Run pnpm test from /home/johnny/projects/toastmachine-resources-worker after preparing its existing test environment; this invokes the suite.
22. Implementation status
Existing automated test
23. Execution status
Not run
24. Known limitations
Static source inventory only. Loops, parameter tables, shared helpers and conditional modifiers can change executed counts. Indirect helper assertions are not expanded.
25. Follow-up actions
Reconcile runtime instances with this declaration, review symbolic fixtures and unasserted effects, and record execution evidence. Preserve this ID.
Source assertions
A1 line 15: expect((await render(config).json()).schemaCatalogue).toEqual(catalogue)
A2 line 17: expect(HOW_TO_USE_GUIDE).toContain(JSON.stringify(catalogue, null, 2))
A3 line 23: expect(catalogue).toEqual(JSON.parse(readFileSync(source, "utf8")))
A4 line 29: expect(catalogue).toEqual(JSON.parse(readFileSync(mcp, "utf8")))
A5 line 31: expect(api.paths).not.toHaveProperty("/schemas")
A6 line 36: expect(\n api.paths[path].get.responses["200"].content[mime].schema.properties\n .schemaCatalogue.items.required,\n ).toEqual(["schema_name", "schema_version", "schema"])
Source inputs and operations
Inputs are supplied indirectly through the cited fixture/helper; inspect it before reproduction.
RES-037 — public contract links normative conventions and states search limitations
Field
Source-backed specification or observation
1. Test ID and name
RES-037 — public contract links normative conventions and states search limitations
2. Requirement or guarantee
Source test intent: public contract links normative conventions and states search limitations. Displayed assertions establish this test’s expected checks, not a separate system-wide guarantee.
3. Purpose and risk addressed
Detect regression of this named behaviour; complete business-impact/invariant analysis remains in the curated cases or follow-up review.
4. Priority
High — provisional catalogue triage; subject to risk review.
5. Test type
Contract — provisional grouping from the declaration name.
6. Preconditions
Use section C plus the cited file’s fixtures and setup/teardown hooks. Suite context: top level. Do not infer starting state from the title.
7. Input and test data
No each/for parameter table on this declaration; its callback may still generate inputs. Input/operation expressions: No direct request/operation expression extracted; inspect the source fixture/helper… Use disposable fixture data only.
8. Execution steps
1. Prepare the existing source test harness from section C. 2. Run pnpm test. 3. Locate this named declaration and its parameterized/conditional instances. 4. Compare the displayed assertions. 5. Record evidence and follow teardown. Not executed during this review.
9. Expected HTTP status, where applicable
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
10. Expected response headers and body
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
11. Expected state changes
See assertions A3 below. Expression grouping does not prove complete before/after state coverage.
12. Expected emitted events or downstream calls, where applicable
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
13. Negative assertions: what must not happen
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
14. Cleanup and postconditions
Use the cited file’s hooks/finally blocks and section C. Restore mocks and remove only isolated test data.
15. Actual result
Not run — no execution evidence collected.
16. Evidence references
test/review-findings.test.mjs:42; assertion/input source links below. Source key: test/review-findings.test.mjs :: public contract links normative conventions and states search limitations :: line 42 at this pinned revision.
17. Execution date
Not run.
18. Status and outstanding issues
Existing declaration documented; indirect helper assertions and full semantic coverage are not inferred from static extraction.
19. Category
Contract (provisional).
20. Handler, interface or code path
test/review-findings.test.mjs:42; expressions No direct request/operation expression extracted; inspect the source fixture/helper… Imported modules: node:fs, vitest, ../src/schema-catalogue.json, ../src/resources/service.ts, ../src/resources/openapi.ts, ../src/guide.ts.
21. Test implementation location and command
test/review-findings.test.mjs:42 — public contract links normative conventions and states search limitations. Run pnpm test from /home/johnny/projects/toastmachine-resources-worker after preparing its existing test environment; this invokes the suite.
22. Implementation status
Existing automated test
23. Execution status
Not run
24. Known limitations
Static source inventory only. Loops, parameter tables, shared helpers and conditional modifiers can change executed counts. Indirect helper assertions are not expanded.
25. Follow-up actions
Reconcile runtime instances with this declaration, review symbolic fixtures and unasserted effects, and record execution evidence. Preserve this ID.
Source assertions
A1 line 44: expect(api.info.description).toContain("/how-to-use#verification-convention")
A3 line 53: expect(HOW_TO_USE_GUIDE).toContain(\n "verification message --supports--> claim message",\n )
A4 line 56: expect(HOW_TO_USE_GUIDE).toContain("assertion author versus claim author")
Source inputs and operations
Inputs are supplied indirectly through the cited fixture/helper; inspect it before reproduction.
test/security-errors-uuid.test.mjs
RES-038 — HTTP bearer requirements use the registered scheme exactly and never secure public reads
Field
Source-backed specification or observation
1. Test ID and name
RES-038 — HTTP bearer requirements use the registered scheme exactly and never secure public reads
2. Requirement or guarantee
Source test intent: HTTP bearer requirements use the registered scheme exactly and never secure public reads. Displayed assertions establish this test’s expected checks, not a separate system-wide guarantee.
3. Purpose and risk addressed
Detect regression of this named behaviour; complete business-impact/invariant analysis remains in the curated cases or follow-up review.
4. Priority
High — provisional catalogue triage; subject to risk review.
5. Test type
Regression — provisional grouping from the declaration name.
6. Preconditions
Use section C plus the cited file’s fixtures and setup/teardown hooks. Suite context: top level. Do not infer starting state from the title.
7. Input and test data
No each/for parameter table on this declaration; its callback may still generate inputs. Input/operation expressions: No direct request/operation expression extracted; inspect the source fixture/helper… Use disposable fixture data only.
8. Execution steps
1. Prepare the existing source test harness from section C. 2. Run pnpm test. 3. Locate this named declaration and its parameterized/conditional instances. 4. Compare the displayed assertions. 5. Record evidence and follow teardown. Not executed during this review.
9. Expected HTTP status, where applicable
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
10. Expected response headers and body
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
11. Expected state changes
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
12. Expected emitted events or downstream calls, where applicable
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
13. Negative assertions: what must not happen
See assertions A2, A5 below. Only the shown negative/rejection checks are claimed; other forbidden effects require review.
14. Cleanup and postconditions
Use the cited file’s hooks/finally blocks and section C. Restore mocks and remove only isolated test data.
15. Actual result
Not run — no execution evidence collected.
16. Evidence references
test/security-errors-uuid.test.mjs:24; assertion/input source links below. Source key: test/security-errors-uuid.test.mjs :: HTTP bearer requirements use the registered scheme exactly and never secure public reads :: line 24 at this pinned revision.
17. Execution date
Not run.
18. Status and outstanding issues
Existing declaration documented; indirect helper assertions and full semantic coverage are not inferred from static extraction.
19. Category
Regression (provisional).
20. Handler, interface or code path
test/security-errors-uuid.test.mjs:24; expressions No direct request/operation expression extracted; inspect the source fixture/helper… Imported modules: node:fs, vitest, ajv/dist/2020.js, ../src/resources/openapi.ts, ../src/index.ts.
21. Test implementation location and command
test/security-errors-uuid.test.mjs:24 — HTTP bearer requirements use the registered scheme exactly and never secure public reads. Run pnpm test from /home/johnny/projects/toastmachine-resources-worker after preparing its existing test environment; this invokes the suite.
22. Implementation status
Existing automated test
23. Execution status
Not run
24. Known limitations
Static source inventory only. Loops, parameter tables, shared helpers and conditional modifiers can change executed counts. Indirect helper assertions are not expanded.
25. Follow-up actions
Reconcile runtime instances with this declaration, review symbolic fixtures and unasserted effects, and record execution evidence. Preserve this ID.
Source assertions
A1 line 26: expect(spec.components.securitySchemes.bearerAuth).toMatchObject({\n type: "http",\n scheme: "bearer",\n })
Inputs are supplied indirectly through the cited fixture/helper; inspect it before reproduction.
RES-039 — public reads need no bearer while token and write routes enforce authentication
Field
Source-backed specification or observation
1. Test ID and name
RES-039 — public reads need no bearer while token and write routes enforce authentication
2. Requirement or guarantee
Source test intent: public reads need no bearer while token and write routes enforce authentication. Displayed assertions establish this test’s expected checks, not a separate system-wide guarantee.
3. Purpose and risk addressed
Detect regression of this named behaviour; complete business-impact/invariant analysis remains in the curated cases or follow-up review.
4. Priority
High — provisional catalogue triage; subject to risk review.
5. Test type
Security — provisional grouping from the declaration name.
6. Preconditions
Use section C plus the cited file’s fixtures and setup/teardown hooks. Suite context: top level. Do not infer starting state from the title.
7. Input and test data
skipIf: !existsSync(ingressSource) Input/operation expressions: I1, I2, I3, I4, I5. Use disposable fixture data only.
8. Execution steps
1. Prepare the existing source test harness from section C. 2. Run pnpm test. 3. Locate this named declaration and its parameterized/conditional instances. 4. Compare the displayed assertions. 5. Record evidence and follow teardown. Not executed during this review.
9. Expected HTTP status, where applicable
See assertions A1, A2 below. A numeric schema/helper expectation is not automatically an HTTP response contract.
10. Expected response headers and body
See assertions A1, A2, A3, A4, A5 below. Referenced variables remain symbolic; no universal response envelope is assumed.
11. Expected state changes
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
12. Expected emitted events or downstream calls, where applicable
See assertions A6 below. No delivery guarantee beyond the checked expressions is inferred.
13. Negative assertions: what must not happen
See assertions A6 below. Only the shown negative/rejection checks are claimed; other forbidden effects require review.
14. Cleanup and postconditions
Use the cited file’s hooks/finally blocks and section C. Restore mocks and remove only isolated test data.
15. Actual result
Not run — no execution evidence collected.
16. Evidence references
test/security-errors-uuid.test.mjs:72; assertion/input source links below. Source key: test/security-errors-uuid.test.mjs :: public reads need no bearer while token and write routes enforce authentication :: line 72 at this pinned revision.
17. Execution date
Not run.
18. Status and outstanding issues
Existing declaration documented; indirect helper assertions and full semantic coverage are not inferred from static extraction.
test/security-errors-uuid.test.mjs:72 — public reads need no bearer while token and write routes enforce authentication. Run pnpm test from /home/johnny/projects/toastmachine-resources-worker after preparing its existing test environment; this invokes the suite.
22. Implementation status
Existing automated test
23. Execution status
Not run
24. Known limitations
Static source inventory only. Loops, parameter tables, shared helpers and conditional modifiers can change executed counts. Conditional/skip modifier present. Indirect helper assertions are not expanded.
25. Follow-up actions
Reconcile runtime instances with this declaration, review symbolic fixtures and unasserted effects, and record execution evidence. Preserve this ID.
RES-040 — operation-token schema matches the version, variant and case syntax gates
Field
Source-backed specification or observation
1. Test ID and name
RES-040 — operation-token schema matches the version, variant and case syntax gates
2. Requirement or guarantee
Source test intent: operation-token schema matches the version, variant and case syntax gates. Displayed assertions establish this test’s expected checks, not a separate system-wide guarantee.
3. Purpose and risk addressed
Detect regression of this named behaviour; complete business-impact/invariant analysis remains in the curated cases or follow-up review.
4. Priority
High — provisional catalogue triage; subject to risk review.
5. Test type
Contract — provisional grouping from the declaration name.
6. Preconditions
Use section C plus the cited file’s fixtures and setup/teardown hooks. Suite context: top level. Do not infer starting state from the title.
7. Input and test data
No each/for parameter table on this declaration; its callback may still generate inputs. Input/operation expressions: No direct request/operation expression extracted; inspect the source fixture/helper… Use disposable fixture data only.
8. Execution steps
1. Prepare the existing source test harness from section C. 2. Run pnpm test. 3. Locate this named declaration and its parameterized/conditional instances. 4. Compare the displayed assertions. 5. Record evidence and follow teardown. Not executed during this review.
9. Expected HTTP status, where applicable
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
10. Expected response headers and body
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
11. Expected state changes
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
12. Expected emitted events or downstream calls, where applicable
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
13. Negative assertions: what must not happen
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
14. Cleanup and postconditions
Use the cited file’s hooks/finally blocks and section C. Restore mocks and remove only isolated test data.
15. Actual result
Not run — no execution evidence collected.
16. Evidence references
test/security-errors-uuid.test.mjs:124; assertion/input source links below. Source key: test/security-errors-uuid.test.mjs :: operation-token schema matches the version, variant and case syntax gates :: line 124 at this pinned revision.
17. Execution date
Not run.
18. Status and outstanding issues
Existing declaration documented; indirect helper assertions and full semantic coverage are not inferred from static extraction.
19. Category
Contract (provisional).
20. Handler, interface or code path
test/security-errors-uuid.test.mjs:124; expressions No direct request/operation expression extracted; inspect the source fixture/helper… Imported modules: node:fs, vitest, ajv/dist/2020.js, ../src/resources/openapi.ts, ../src/index.ts.
21. Test implementation location and command
test/security-errors-uuid.test.mjs:124 — operation-token schema matches the version, variant and case syntax gates. Run pnpm test from /home/johnny/projects/toastmachine-resources-worker after preparing its existing test environment; this invokes the suite.
22. Implementation status
Existing automated test
23. Execution status
Not run
24. Known limitations
Static source inventory only. Loops, parameter tables, shared helpers and conditional modifiers can change executed counts. Indirect helper assertions are not expanded.
25. Follow-up actions
Reconcile runtime instances with this declaration, review symbolic fixtures and unasserted effects, and record execution evidence. Preserve this ID.
Source assertions
A1 line 141: expect(validate(value), value).toBe(true)
A2 line 153: expect(validate(value), value).toBe(false)
Source inputs and operations
Inputs are supplied indirectly through the cited fixture/helper; inspect it before reproduction.
RES-041 — conversation errors match their negotiated status, Content-Type and OpenAPI schema
Field
Source-backed specification or observation
1. Test ID and name
RES-041 — conversation errors match their negotiated status, Content-Type and OpenAPI schema
2. Requirement or guarantee
Source test intent: conversation errors match their negotiated status, Content-Type and OpenAPI schema. Displayed assertions establish this test’s expected checks, not a separate system-wide guarantee.
3. Purpose and risk addressed
Detect regression of this named behaviour; complete business-impact/invariant analysis remains in the curated cases or follow-up review.
4. Priority
High — provisional catalogue triage; subject to risk review.
5. Test type
Contract — provisional grouping from the declaration name.
6. Preconditions
Use section C plus the cited file’s fixtures and setup/teardown hooks. Suite context: top level. Do not infer starting state from the title.
7. Input and test data
skipIf: !existsSync(corpusSource) Input/operation expressions: I1, I2, I3, I4, I5. Use disposable fixture data only.
8. Execution steps
1. Prepare the existing source test harness from section C. 2. Run pnpm test. 3. Locate this named declaration and its parameterized/conditional instances. 4. Compare the displayed assertions. 5. Record evidence and follow teardown. Not executed during this review.
9. Expected HTTP status, where applicable
See assertions A1, A8 below. A numeric schema/helper expectation is not automatically an HTTP response contract.
10. Expected response headers and body
See assertions A1, A2, A3, A4, A5, A9, A10, A11, A12, A13 below. Referenced variables remain symbolic; no universal response envelope is assumed.
11. Expected state changes
See assertions A5, A11, A12 below. Expression grouping does not prove complete before/after state coverage.
12. Expected emitted events or downstream calls, where applicable
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
13. Negative assertions: what must not happen
See assertions A11, A13 below. Only the shown negative/rejection checks are claimed; other forbidden effects require review.
14. Cleanup and postconditions
Use the cited file’s hooks/finally blocks and section C. Restore mocks and remove only isolated test data.
15. Actual result
Not run — no execution evidence collected.
16. Evidence references
test/security-errors-uuid.test.mjs:156; assertion/input source links below. Source key: test/security-errors-uuid.test.mjs :: conversation errors match their negotiated status, Content-Type and OpenAPI schema :: line 156 at this pinned revision.
17. Execution date
Not run.
18. Status and outstanding issues
Existing declaration documented; indirect helper assertions and full semantic coverage are not inferred from static extraction.
test/security-errors-uuid.test.mjs:156 — conversation errors match their negotiated status, Content-Type and OpenAPI schema. Run pnpm test from /home/johnny/projects/toastmachine-resources-worker after preparing its existing test environment; this invokes the suite.
22. Implementation status
Existing automated test
23. Execution status
Not run
24. Known limitations
Static source inventory only. Loops, parameter tables, shared helpers and conditional modifiers can change executed counts. Conditional/skip modifier present. Indirect helper assertions are not expanded.
25. Follow-up actions
Reconcile runtime instances with this declaration, review symbolic fixtures and unasserted effects, and record execution evidence. Preserve this ID.
Source assertions
A1 line 273: expect(response.status, `${path}?${query} ${accept}`).toBe(status)
A2 line 274: expect(response.headers.get("Content-Type").split(";")[0]).toBe(mime)
A3 line 282: expect(check(body), JSON.stringify(check.errors)).toBe(true)
A4 line 284: expect(body.replaceAll("\\", "")).toContain(code)
I1 line 184: corpus.fetch(request, corpusEnv, ctx)
I2 line 268: gateway.fetch(\n new Request(`${config.base_url}${path}?${query}`, { headers }),\n env,\n ctx,\n )
I3 line 269: new Request(`${config.base_url}${path}?${query}`, { headers })
I4 line 293: gateway.fetch(\n new Request(`${config.base_url}${path}?${query}`, {\n method: "HEAD",\n headers,\n }),\n env,\n ctx,\n )
I5 line 294: new Request(`${config.base_url}${path}?${query}`, {\n method: "HEAD",\n headers,\n })
RES-042 — OpenAPI, SDK and MCP already describe the implemented search scope
Field
Source-backed specification or observation
1. Test ID and name
RES-042 — OpenAPI, SDK and MCP already describe the implemented search scope
2. Requirement or guarantee
Source test intent: OpenAPI, SDK and MCP already describe the implemented search scope. Displayed assertions establish this test’s expected checks, not a separate system-wide guarantee.
3. Purpose and risk addressed
Detect regression of this named behaviour; complete business-impact/invariant analysis remains in the curated cases or follow-up review.
4. Priority
High — provisional catalogue triage; subject to risk review.
5. Test type
Security — provisional grouping from the declaration name.
6. Preconditions
Use section C plus the cited file’s fixtures and setup/teardown hooks. Suite context: top level. Do not infer starting state from the title.
7. Input and test data
No each/for parameter table on this declaration; its callback may still generate inputs. Input/operation expressions: No direct request/operation expression extracted; inspect the source fixture/helper… Use disposable fixture data only.
8. Execution steps
1. Prepare the existing source test harness from section C. 2. Run pnpm test. 3. Locate this named declaration and its parameterized/conditional instances. 4. Compare the displayed assertions. 5. Record evidence and follow teardown. Not executed during this review.
9. Expected HTTP status, where applicable
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
10. Expected response headers and body
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
11. Expected state changes
See assertions A5 below. Expression grouping does not prove complete before/after state coverage.
12. Expected emitted events or downstream calls, where applicable
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
13. Negative assertions: what must not happen
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
14. Cleanup and postconditions
Use the cited file’s hooks/finally blocks and section C. Restore mocks and remove only isolated test data.
15. Actual result
Not run — no execution evidence collected.
16. Evidence references
test/security-errors-uuid.test.mjs:319; assertion/input source links below. Source key: test/security-errors-uuid.test.mjs :: OpenAPI, SDK and MCP already describe the implemented search scope :: line 319 at this pinned revision.
17. Execution date
Not run.
18. Status and outstanding issues
Existing declaration documented; indirect helper assertions and full semantic coverage are not inferred from static extraction.
19. Category
Security (provisional).
20. Handler, interface or code path
test/security-errors-uuid.test.mjs:319; expressions No direct request/operation expression extracted; inspect the source fixture/helper… Imported modules: node:fs, vitest, ajv/dist/2020.js, ../src/resources/openapi.ts, ../src/index.ts.
21. Test implementation location and command
test/security-errors-uuid.test.mjs:319 — OpenAPI, SDK and MCP already describe the implemented search scope. Run pnpm test from /home/johnny/projects/toastmachine-resources-worker after preparing its existing test environment; this invokes the suite.
22. Implementation status
Existing automated test
23. Execution status
Not run
24. Known limitations
Static source inventory only. Loops, parameter tables, shared helpers and conditional modifiers can change executed counts. Indirect helper assertions are not expanded.
25. Follow-up actions
Reconcile runtime instances with this declaration, review symbolic fixtures and unasserted effects, and record execution evidence. Preserve this ID.
Source assertions
A1 line 322: expect(description).toContain("FTS5/BM25")
A2 line 328: expect(description).toContain(phrase)
A3 line 329: expect(description).toContain("No payload search")
Inputs are supplied indirectly through the cited fixture/helper; inspect it before reproduction.
test/standalone.test.mjs
RES-043 — typechecks as an isolated checkout without sibling Worker repositories
Field
Source-backed specification or observation
1. Test ID and name
RES-043 — typechecks as an isolated checkout without sibling Worker repositories
2. Requirement or guarantee
Source test intent: typechecks as an isolated checkout without sibling Worker repositories. Displayed assertions establish this test’s expected checks, not a separate system-wide guarantee.
3. Purpose and risk addressed
Detect regression of this named behaviour; complete business-impact/invariant analysis remains in the curated cases or follow-up review.
4. Priority
High — provisional catalogue triage; subject to risk review.
5. Test type
Regression — provisional grouping from the declaration name.
6. Preconditions
Use section C plus the cited file’s fixtures and setup/teardown hooks. Suite context: top level. Do not infer starting state from the title.
7. Input and test data
No each/for parameter table on this declaration; its callback may still generate inputs. Input/operation expressions: No direct request/operation expression extracted; inspect the source fixture/helper… Use disposable fixture data only.
8. Execution steps
1. Prepare the existing source test harness from section C. 2. Run pnpm test. 3. Locate this named declaration and its parameterized/conditional instances. 4. Compare the displayed assertions. 5. Record evidence and follow teardown. Not executed during this review.
9. Expected HTTP status, where applicable
See assertions A2 below. A numeric schema/helper expectation is not automatically an HTTP response contract.
10. Expected response headers and body
See assertions A1, A2 below. Referenced variables remain symbolic; no universal response envelope is assumed.
11. Expected state changes
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
12. Expected emitted events or downstream calls, where applicable
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
13. Negative assertions: what must not happen
See assertions A1 below. Only the shown negative/rejection checks are claimed; other forbidden effects require review.
14. Cleanup and postconditions
Use the cited file’s hooks/finally blocks and section C. Restore mocks and remove only isolated test data.
15. Actual result
Not run — no execution evidence collected.
16. Evidence references
test/standalone.test.mjs:12; assertion/input source links below. Source key: test/standalone.test.mjs :: typechecks as an isolated checkout without sibling Worker repositories :: line 12 at this pinned revision.
17. Execution date
Not run.
18. Status and outstanding issues
Existing declaration documented; indirect helper assertions and full semantic coverage are not inferred from static extraction.
19. Category
Regression (provisional).
20. Handler, interface or code path
test/standalone.test.mjs:12; expressions No direct request/operation expression extracted; inspect the source fixture/helper… Imported modules: node:fs, node:os, node:path, node:module, node:child_process, node:url, vitest.
21. Test implementation location and command
test/standalone.test.mjs:12 — typechecks as an isolated checkout without sibling Worker repositories. Run pnpm test from /home/johnny/projects/toastmachine-resources-worker after preparing its existing test environment; this invokes the suite.
22. Implementation status
Existing automated test
23. Execution status
Not run
24. Known limitations
Static source inventory only. Loops, parameter tables, shared helpers and conditional modifiers can change executed counts. Indirect helper assertions are not expanded.
25. Follow-up actions
Reconcile runtime instances with this declaration, review symbolic fixtures and unasserted effects, and record execution evidence. Preserve this ID.
A2 line 30: expect(result.status, result.stdout + result.stderr).toBe(0)
Source inputs and operations
Inputs are supplied indirectly through the cited fixture/helper; inspect it before reproduction.
RES-044 — packaged HTTP and MCP guides remain identical when both repositories are available
Field
Source-backed specification or observation
1. Test ID and name
RES-044 — packaged HTTP and MCP guides remain identical when both repositories are available
2. Requirement or guarantee
Source test intent: packaged HTTP and MCP guides remain identical when both repositories are available. Displayed assertions establish this test’s expected checks, not a separate system-wide guarantee.
3. Purpose and risk addressed
Detect regression of this named behaviour; complete business-impact/invariant analysis remains in the curated cases or follow-up review.
4. Priority
High — provisional catalogue triage; subject to risk review.
5. Test type
Regression — provisional grouping from the declaration name.
6. Preconditions
Use section C plus the cited file’s fixtures and setup/teardown hooks. Suite context: top level. Do not infer starting state from the title.
7. Input and test data
No each/for parameter table on this declaration; its callback may still generate inputs. Input/operation expressions: No direct request/operation expression extracted; inspect the source fixture/helper… Use disposable fixture data only.
8. Execution steps
1. Prepare the existing source test harness from section C. 2. Run pnpm test. 3. Locate this named declaration and its parameterized/conditional instances. 4. Compare the displayed assertions. 5. Record evidence and follow teardown. Not executed during this review.
9. Expected HTTP status, where applicable
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
10. Expected response headers and body
See assertions A1 below. Referenced variables remain symbolic; no universal response envelope is assumed.
11. Expected state changes
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
12. Expected emitted events or downstream calls, where applicable
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
13. Negative assertions: what must not happen
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
14. Cleanup and postconditions
Use the cited file’s hooks/finally blocks and section C. Restore mocks and remove only isolated test data.
15. Actual result
Not run — no execution evidence collected.
16. Evidence references
test/standalone.test.mjs:36; assertion/input source links below. Source key: test/standalone.test.mjs :: packaged HTTP and MCP guides remain identical when both repositories are available :: line 36 at this pinned revision.
17. Execution date
Not run.
18. Status and outstanding issues
Existing declaration documented; indirect helper assertions and full semantic coverage are not inferred from static extraction.
19. Category
Regression (provisional).
20. Handler, interface or code path
test/standalone.test.mjs:36; expressions No direct request/operation expression extracted; inspect the source fixture/helper… Imported modules: node:fs, node:os, node:path, node:module, node:child_process, node:url, vitest.
21. Test implementation location and command
test/standalone.test.mjs:36 — packaged HTTP and MCP guides remain identical when both repositories are available. Run pnpm test from /home/johnny/projects/toastmachine-resources-worker after preparing its existing test environment; this invokes the suite.
22. Implementation status
Existing automated test
23. Execution status
Not run
24. Known limitations
Static source inventory only. Loops, parameter tables, shared helpers and conditional modifiers can change executed counts. Indirect helper assertions are not expanded.
25. Follow-up actions
Reconcile runtime instances with this declaration, review symbolic fixtures and unasserted effects, and record execution evidence. Preserve this ID.
Source assertions
A1 line 42: expect(guideBody(join(root, "src/guide.ts"))).toBe(guideBody(sibling))
Source inputs and operations
Inputs are supplied indirectly through the cited fixture/helper; inspect it before reproduction.
test/structured-payload.test.mjs
RES-045 — OpenAPI validates payload-only, all JSON types, metadata pairing and service fields
Field
Source-backed specification or observation
1. Test ID and name
RES-045 — OpenAPI validates payload-only, all JSON types, metadata pairing and service fields
2. Requirement or guarantee
Source test intent: OpenAPI validates payload-only, all JSON types, metadata pairing and service fields. Displayed assertions establish this test’s expected checks, not a separate system-wide guarantee.
3. Purpose and risk addressed
Detect regression of this named behaviour; complete business-impact/invariant analysis remains in the curated cases or follow-up review.
4. Priority
High — provisional catalogue triage; subject to risk review.
5. Test type
Contract — provisional grouping from the declaration name.
6. Preconditions
Use section C plus the cited file’s fixtures and setup/teardown hooks. Suite context: top level. Do not infer starting state from the title.
7. Input and test data
No each/for parameter table on this declaration; its callback may still generate inputs. Input/operation expressions: I1, I2, I3, I4. Use disposable fixture data only.
8. Execution steps
1. Prepare the existing source test harness from section C. 2. Run pnpm test. 3. Locate this named declaration and its parameterized/conditional instances. 4. Compare the displayed assertions. 5. Record evidence and follow teardown. Not executed during this review.
9. Expected HTTP status, where applicable
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
10. Expected response headers and body
See assertions A1, A2, A3, A4, A5, A6, A7, A8, A9, A10 below. Referenced variables remain symbolic; no universal response envelope is assumed.
11. Expected state changes
See assertions A1, A2, A11 below. Expression grouping does not prove complete before/after state coverage.
12. Expected emitted events or downstream calls, where applicable
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
13. Negative assertions: what must not happen
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
14. Cleanup and postconditions
Use the cited file’s hooks/finally blocks and section C. Restore mocks and remove only isolated test data.
15. Actual result
Not run — no execution evidence collected.
16. Evidence references
test/structured-payload.test.mjs:32; assertion/input source links below. Source key: test/structured-payload.test.mjs :: OpenAPI validates payload-only, all JSON types, metadata pairing and service fields :: line 32 at this pinned revision.
17. Execution date
Not run.
18. Status and outstanding issues
Existing declaration documented; indirect helper assertions and full semantic coverage are not inferred from static extraction.
test/structured-payload.test.mjs:32 — OpenAPI validates payload-only, all JSON types, metadata pairing and service fields. Run pnpm test from /home/johnny/projects/toastmachine-resources-worker after preparing its existing test environment; this invokes the suite.
22. Implementation status
Existing automated test
23. Execution status
Not run
24. Known limitations
Static source inventory only. Loops, parameter tables, shared helpers and conditional modifiers can change executed counts. Indirect helper assertions are not expanded.
25. Follow-up actions
Reconcile runtime instances with this declaration, review symbolic fixtures and unasserted effects, and record execution evidence. Preserve this ID.
RES-046 — RSS and Atom render payload-only JSON without losing null or nested values
Field
Source-backed specification or observation
1. Test ID and name
RES-046 — RSS and Atom render payload-only JSON without losing null or nested values
2. Requirement or guarantee
Source test intent: RSS and Atom render payload-only JSON without losing null or nested values. Displayed assertions establish this test’s expected checks, not a separate system-wide guarantee.
3. Purpose and risk addressed
Detect regression of this named behaviour; complete business-impact/invariant analysis remains in the curated cases or follow-up review.
4. Priority
High — provisional catalogue triage; subject to risk review.
5. Test type
Regression — provisional grouping from the declaration name.
6. Preconditions
Use section C plus the cited file’s fixtures and setup/teardown hooks. Suite context: top level. Do not infer starting state from the title.
7. Input and test data
No each/for parameter table on this declaration; its callback may still generate inputs. Input/operation expressions: No direct request/operation expression extracted; inspect the source fixture/helper… Use disposable fixture data only.
8. Execution steps
1. Prepare the existing source test harness from section C. 2. Run pnpm test. 3. Locate this named declaration and its parameterized/conditional instances. 4. Compare the displayed assertions. 5. Record evidence and follow teardown. Not executed during this review.
9. Expected HTTP status, where applicable
See assertions A1 below. A numeric schema/helper expectation is not automatically an HTTP response contract.
10. Expected response headers and body
See assertions A1, A2 below. Referenced variables remain symbolic; no universal response envelope is assumed.
11. Expected state changes
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
12. Expected emitted events or downstream calls, where applicable
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
13. Negative assertions: what must not happen
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
14. Cleanup and postconditions
Use the cited file’s hooks/finally blocks and section C. Restore mocks and remove only isolated test data.
15. Actual result
Not run — no execution evidence collected.
16. Evidence references
test/structured-payload.test.mjs:142; assertion/input source links below. Source key: test/structured-payload.test.mjs :: RSS and Atom render payload-only JSON without losing null or nested values :: line 142 at this pinned revision.
17. Execution date
Not run.
18. Status and outstanding issues
Existing declaration documented; indirect helper assertions and full semantic coverage are not inferred from static extraction.
19. Category
Regression (provisional).
20. Handler, interface or code path
test/structured-payload.test.mjs:142; expressions No direct request/operation expression extracted; inspect the source fixture/helper… Imported modules: vitest, ajv/dist/2020.js, ../src/resources/openapi.ts, ../src/relationship-openapi.ts, ../src/resources/rss.ts, ../src/resources/atom.ts.
21. Test implementation location and command
test/structured-payload.test.mjs:142 — RSS and Atom render payload-only JSON without losing null or nested values. Run pnpm test from /home/johnny/projects/toastmachine-resources-worker after preparing its existing test environment; this invokes the suite.
22. Implementation status
Existing automated test
23. Execution status
Not run
24. Known limitations
Static source inventory only. Loops, parameter tables, shared helpers and conditional modifiers can change executed counts. Indirect helper assertions are not expanded.
25. Follow-up actions
Reconcile runtime instances with this declaration, review symbolic fixtures and unasserted effects, and record execution evidence. Preserve this ID.
Inputs are supplied indirectly through the cited fixture/helper; inspect it before reproduction.
test/worker.test.mjs
RES-047 — publishes the tag catalogue contract and forwards public tag reads through Corpus
Field
Source-backed specification or observation
1. Test ID and name
RES-047 — publishes the tag catalogue contract and forwards public tag reads through Corpus
2. Requirement or guarantee
Source test intent: publishes the tag catalogue contract and forwards public tag reads through Corpus. Displayed assertions establish this test’s expected checks, not a separate system-wide guarantee.
3. Purpose and risk addressed
Detect regression of this named behaviour; complete business-impact/invariant analysis remains in the curated cases or follow-up review.
4. Priority
High — provisional catalogue triage; subject to risk review.
5. Test type
Contract — provisional grouping from the declaration name.
6. Preconditions
Use section C plus the cited file’s fixtures and setup/teardown hooks. Suite context: top level. Do not infer starting state from the title.
7. Input and test data
No each/for parameter table on this declaration; its callback may still generate inputs. Input/operation expressions: I1, I2, I3, I4. Use disposable fixture data only.
8. Execution steps
1. Prepare the existing source test harness from section C. 2. Run pnpm test. 3. Locate this named declaration and its parameterized/conditional instances. 4. Compare the displayed assertions. 5. Record evidence and follow teardown. Not executed during this review.
9. Expected HTTP status, where applicable
See assertions A1 below. A numeric schema/helper expectation is not automatically an HTTP response contract.
10. Expected response headers and body
See assertions A1, A2, A6, A7, A8 below. Referenced variables remain symbolic; no universal response envelope is assumed.
11. Expected state changes
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
12. Expected emitted events or downstream calls, where applicable
See assertions A3, A4 below. No delivery guarantee beyond the checked expressions is inferred.
13. Negative assertions: what must not happen
See assertions A2 below. Only the shown negative/rejection checks are claimed; other forbidden effects require review.
14. Cleanup and postconditions
Use the cited file’s hooks/finally blocks and section C. Restore mocks and remove only isolated test data.
15. Actual result
Not run — no execution evidence collected.
16. Evidence references
test/worker.test.mjs:24; assertion/input source links below. Source key: test/worker.test.mjs :: publishes the tag catalogue contract and forwards public tag reads through Corpus :: line 24 at this pinned revision.
17. Execution date
Not run.
18. Status and outstanding issues
Existing declaration documented; indirect helper assertions and full semantic coverage are not inferred from static extraction.
test/worker.test.mjs:24 — publishes the tag catalogue contract and forwards public tag reads through Corpus. Run pnpm test from /home/johnny/projects/toastmachine-resources-worker after preparing its existing test environment; this invokes the suite.
22. Implementation status
Existing automated test
23. Execution status
Not run
24. Known limitations
Static source inventory only. Loops, parameter tables, shared helpers and conditional modifiers can change executed counts. Indirect helper assertions are not expanded.
25. Follow-up actions
Reconcile runtime instances with this declaration, review symbolic fixtures and unasserted effects, and record execution evidence. Preserve this ID.
A4 line 51: expect(fetch.mock.calls[0][0].url).toBe(\n "https://example.com/tags?limit=1&offset=2",\n )
A5 line 62: expect(get.description).toContain("Values omit !")
A6 line 63: expect(\n get.responses["200"].content["application/json"].schema.required,\n ).toEqual(["tags", "total", "limit", "offset", "has_more"])
A7 line 66: expect(get.responses["200"].content["text/markdown"]).toBeDefined()
A8 line 67: expect(get.responses["406"]).toBeDefined()
Source inputs and operations
I1 line 43: worker.fetch(\n new Request("https://example.com/tags?limit=1&offset=2"),\n env,\n context,\n )
I2 line 44: new Request("https://example.com/tags?limit=1&offset=2")
I3 line 55: worker.fetch(\n new Request("https://example.com/openapi.json"),\n env,\n context,\n )
I4 line 56: new Request("https://example.com/openapi.json")
RES-048 — documents registered agent discovery and nullable zero-activity boundaries
Field
Source-backed specification or observation
1. Test ID and name
RES-048 — documents registered agent discovery and nullable zero-activity boundaries
2. Requirement or guarantee
Source test intent: documents registered agent discovery and nullable zero-activity boundaries. Displayed assertions establish this test’s expected checks, not a separate system-wide guarantee.
3. Purpose and risk addressed
Detect regression of this named behaviour; complete business-impact/invariant analysis remains in the curated cases or follow-up review.
4. Priority
High — provisional catalogue triage; subject to risk review.
5. Test type
Contract — provisional grouping from the declaration name.
6. Preconditions
Use section C plus the cited file’s fixtures and setup/teardown hooks. Suite context: top level. Do not infer starting state from the title.
7. Input and test data
No each/for parameter table on this declaration; its callback may still generate inputs. Input/operation expressions: I1, I2. Use disposable fixture data only.
8. Execution steps
1. Prepare the existing source test harness from section C. 2. Run pnpm test. 3. Locate this named declaration and its parameterized/conditional instances. 4. Compare the displayed assertions. 5. Record evidence and follow teardown. Not executed during this review.
9. Expected HTTP status, where applicable
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
10. Expected response headers and body
See assertions A2, A3, A4 below. Referenced variables remain symbolic; no universal response envelope is assumed.
11. Expected state changes
See assertions A5, A6 below. Expression grouping does not prove complete before/after state coverage.
12. Expected emitted events or downstream calls, where applicable
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
13. Negative assertions: what must not happen
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
14. Cleanup and postconditions
Use the cited file’s hooks/finally blocks and section C. Restore mocks and remove only isolated test data.
15. Actual result
Not run — no execution evidence collected.
16. Evidence references
test/worker.test.mjs:70; assertion/input source links below. Source key: test/worker.test.mjs :: documents registered agent discovery and nullable zero-activity boundaries :: line 70 at this pinned revision.
17. Execution date
Not run.
18. Status and outstanding issues
Existing declaration documented; indirect helper assertions and full semantic coverage are not inferred from static extraction.
test/worker.test.mjs:70 — documents registered agent discovery and nullable zero-activity boundaries. Run pnpm test from /home/johnny/projects/toastmachine-resources-worker after preparing its existing test environment; this invokes the suite.
22. Implementation status
Existing automated test
23. Execution status
Not run
24. Known limitations
Static source inventory only. Loops, parameter tables, shared helpers and conditional modifiers can change executed counts. Indirect helper assertions are not expanded.
25. Follow-up actions
Reconcile runtime instances with this declaration, review symbolic fixtures and unasserted effects, and record execution evidence. Preserve this ID.
Source assertions
A1 line 86: expect(directory.description).toContain("no corpus activity")
A2 line 87: expect(profile.responses["404"].description).toContain("not_found")
A3 line 88: expect(profile.responses["404"].description).toContain("registered agent")
A4 line 89: expect(profile.responses["404"].content["application/json"].schema).toEqual(\n api.components.schemas.ErrorResponse,\n )
A5 line 97: expect(item.properties.first_seen_sequence.type).toEqual([\n "integer",\n "null",\n ])
A6 line 101: expect(item.properties.last_seen_sequence.type).toEqual([\n "integer",\n "null",\n ])
A7 line 106: expect(summary.properties.last_active.type).toEqual(["string", "null"])
Source inputs and operations
I1 line 78: worker.fetch(\n new Request("https://example.com/openapi.json"),\n env,\n { waitUntil: vi.fn() },\n )
I2 line 79: new Request("https://example.com/openapi.json")
RES-049 — serves the configured homepage
Field
Source-backed specification or observation
1. Test ID and name
RES-049 — serves the configured homepage
2. Requirement or guarantee
Source test intent: serves the configured homepage. Displayed assertions establish this test’s expected checks, not a separate system-wide guarantee.
3. Purpose and risk addressed
Detect regression of this named behaviour; complete business-impact/invariant analysis remains in the curated cases or follow-up review.
4. Priority
High — provisional catalogue triage; subject to risk review.
5. Test type
Regression — provisional grouping from the declaration name.
6. Preconditions
Use section C plus the cited file’s fixtures and setup/teardown hooks. Suite context: top level. Do not infer starting state from the title.
7. Input and test data
No each/for parameter table on this declaration; its callback may still generate inputs. Input/operation expressions: I1, I2. Use disposable fixture data only.
8. Execution steps
1. Prepare the existing source test harness from section C. 2. Run pnpm test. 3. Locate this named declaration and its parameterized/conditional instances. 4. Compare the displayed assertions. 5. Record evidence and follow teardown. Not executed during this review.
9. Expected HTTP status, where applicable
See assertions A1 below. A numeric schema/helper expectation is not automatically an HTTP response contract.
10. Expected response headers and body
See assertions A1, A2, A3, A4, A5 below. Referenced variables remain symbolic; no universal response envelope is assumed.
11. Expected state changes
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
12. Expected emitted events or downstream calls, where applicable
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
13. Negative assertions: what must not happen
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
14. Cleanup and postconditions
Use the cited file’s hooks/finally blocks and section C. Restore mocks and remove only isolated test data.
15. Actual result
Not run — no execution evidence collected.
16. Evidence references
test/worker.test.mjs:109; assertion/input source links below. Source key: test/worker.test.mjs :: serves the configured homepage :: line 109 at this pinned revision.
17. Execution date
Not run.
18. Status and outstanding issues
Existing declaration documented; indirect helper assertions and full semantic coverage are not inferred from static extraction.
test/worker.test.mjs:109 — serves the configured homepage. Run pnpm test from /home/johnny/projects/toastmachine-resources-worker after preparing its existing test environment; this invokes the suite.
22. Implementation status
Existing automated test
23. Execution status
Not run
24. Known limitations
Static source inventory only. Loops, parameter tables, shared helpers and conditional modifiers can change executed counts. Indirect helper assertions are not expanded.
25. Follow-up actions
Reconcile runtime instances with this declaration, review symbolic fixtures and unasserted effects, and record execution evidence. Preserve this ID.
RES-050 — publishes the kind contract in discovery, protocol docs, and OpenAPI
Field
Source-backed specification or observation
1. Test ID and name
RES-050 — publishes the kind contract in discovery, protocol docs, and OpenAPI
2. Requirement or guarantee
Source test intent: publishes the kind contract in discovery, protocol docs, and OpenAPI. Displayed assertions establish this test’s expected checks, not a separate system-wide guarantee.
3. Purpose and risk addressed
Detect regression of this named behaviour; complete business-impact/invariant analysis remains in the curated cases or follow-up review.
4. Priority
High — provisional catalogue triage; subject to risk review.
5. Test type
Contract — provisional grouping from the declaration name.
6. Preconditions
Use section C plus the cited file’s fixtures and setup/teardown hooks. Suite context: top level. Do not infer starting state from the title.
7. Input and test data
No each/for parameter table on this declaration; its callback may still generate inputs. Input/operation expressions: I1, I2, I3, I4, I5, I6. Use disposable fixture data only.
8. Execution steps
1. Prepare the existing source test harness from section C. 2. Run pnpm test. 3. Locate this named declaration and its parameterized/conditional instances. 4. Compare the displayed assertions. 5. Record evidence and follow teardown. Not executed during this review.
9. Expected HTTP status, where applicable
See assertions A1 below. A numeric schema/helper expectation is not automatically an HTTP response contract.
10. Expected response headers and body
See assertions A1, A2, A13 below. Referenced variables remain symbolic; no universal response envelope is assumed.
11. Expected state changes
See assertions A7, A8, A12 below. Expression grouping does not prove complete before/after state coverage.
12. Expected emitted events or downstream calls, where applicable
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
13. Negative assertions: what must not happen
See assertions A10, A11 below. Only the shown negative/rejection checks are claimed; other forbidden effects require review.
14. Cleanup and postconditions
Use the cited file’s hooks/finally blocks and section C. Restore mocks and remove only isolated test data.
15. Actual result
Not run — no execution evidence collected.
16. Evidence references
test/worker.test.mjs:135; assertion/input source links below. Source key: test/worker.test.mjs :: publishes the kind contract in discovery, protocol docs, and OpenAPI :: line 135 at this pinned revision.
17. Execution date
Not run.
18. Status and outstanding issues
Existing declaration documented; indirect helper assertions and full semantic coverage are not inferred from static extraction.
test/worker.test.mjs:135 — publishes the kind contract in discovery, protocol docs, and OpenAPI. Run pnpm test from /home/johnny/projects/toastmachine-resources-worker after preparing its existing test environment; this invokes the suite.
22. Implementation status
Existing automated test
23. Execution status
Not run
24. Known limitations
Static source inventory only. Loops, parameter tables, shared helpers and conditional modifiers can change executed counts. Indirect helper assertions are not expanded.
25. Follow-up actions
Reconcile runtime instances with this declaration, review symbolic fixtures and unasserted effects, and record execution evidence. Preserve this ID.
A7 line 171: expect(definition).toContain("conversation_id")
A8 line 172: expect(definition).toContain("root_message_id")
A9 line 173: expect(definition).toContain("subject")
A10 line 174: expect(definition).not.toContain("topic_id")
A11 line 175: expect(definition).not.toContain("topic_name")
A12 line 176: expect(definition).toContain("/conversations/{conversation_id}")
A13 line 183: expect(await vocabResponse.text()).toContain("kind")
Source inputs and operations
I1 line 151: worker.fetch(\n new Request(`https://example.com${path}`),\n env,\n context,\n )
I2 line 152: new Request(`https://example.com${path}`)
I3 line 160: worker.fetch(\n new Request("https://example.com/openapi.json"),\n env,\n context,\n )
I4 line 161: new Request("https://example.com/openapi.json")
I5 line 178: worker.fetch(\n new Request("https://example.com/vocab.jsonld"),\n env,\n context,\n )
I6 line 179: new Request("https://example.com/vocab.jsonld")
RES-051 — publishes the canonical MCP endpoint and implemented OAuth contract consistently
Field
Source-backed specification or observation
1. Test ID and name
RES-051 — publishes the canonical MCP endpoint and implemented OAuth contract consistently
2. Requirement or guarantee
Source test intent: publishes the canonical MCP endpoint and implemented OAuth contract consistently. Displayed assertions establish this test’s expected checks, not a separate system-wide guarantee.
3. Purpose and risk addressed
Detect regression of this named behaviour; complete business-impact/invariant analysis remains in the curated cases or follow-up review.
4. Priority
High — provisional catalogue triage; subject to risk review.
5. Test type
Security — provisional grouping from the declaration name.
6. Preconditions
Use section C plus the cited file’s fixtures and setup/teardown hooks. Suite context: top level. Do not infer starting state from the title.
7. Input and test data
No each/for parameter table on this declaration; its callback may still generate inputs. Input/operation expressions: I1, I2, I3, I4, I5, I6, I7, I8, I9, I10, I11, I12. Use disposable fixture data only.
8. Execution steps
1. Prepare the existing source test harness from section C. 2. Run pnpm test. 3. Locate this named declaration and its parameterized/conditional instances. 4. Compare the displayed assertions. 5. Record evidence and follow teardown. Not executed during this review.
9. Expected HTTP status, where applicable
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
10. Expected response headers and body
See assertions A3, A4, A24, A25, A28 below. Referenced variables remain symbolic; no universal response envelope is assumed.
11. Expected state changes
See assertions A27 below. Expression grouping does not prove complete before/after state coverage.
12. Expected emitted events or downstream calls, where applicable
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
13. Negative assertions: what must not happen
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
14. Cleanup and postconditions
Use the cited file’s hooks/finally blocks and section C. Restore mocks and remove only isolated test data.
15. Actual result
Not run — no execution evidence collected.
16. Evidence references
test/worker.test.mjs:186; assertion/input source links below. Source key: test/worker.test.mjs :: publishes the canonical MCP endpoint and implemented OAuth contract consistently :: line 186 at this pinned revision.
17. Execution date
Not run.
18. Status and outstanding issues
Existing declaration documented; indirect helper assertions and full semantic coverage are not inferred from static extraction.
test/worker.test.mjs:186 — publishes the canonical MCP endpoint and implemented OAuth contract consistently. Run pnpm test from /home/johnny/projects/toastmachine-resources-worker after preparing its existing test environment; this invokes the suite.
22. Implementation status
Existing automated test
23. Execution status
Not run
24. Known limitations
Static source inventory only. Loops, parameter tables, shared helpers and conditional modifiers can change executed counts. Indirect helper assertions are not expanded.
25. Follow-up actions
Reconcile runtime instances with this declaration, review symbolic fixtures and unasserted effects, and record execution evidence. Preserve this ID.
I5 line 217: worker.fetch(\n new Request("https://example.com/llms.txt"),\n env,\n context,\n )
I6 line 218: new Request("https://example.com/llms.txt")
I7 line 234: worker.fetch(\n new Request("https://example.com/auth.md"),\n env,\n context,\n )
I8 line 235: new Request("https://example.com/auth.md")
I9 line 249: worker.fetch(\n new Request("https://example.com/.well-known/api-catalog"),\n env,\n context,\n )
I10 line 250: new Request("https://example.com/.well-known/api-catalog")
I11 line 260: worker.fetch(\n new Request("https://example.com/openapi.json"),\n env,\n context,\n )
I12 line 261: new Request("https://example.com/openapi.json")
RES-052 — homepage negotiates quality weights and exclusions without mixing cache entries
Field
Source-backed specification or observation
1. Test ID and name
RES-052 — homepage negotiates quality weights and exclusions without mixing cache entries
2. Requirement or guarantee
Source test intent: homepage negotiates quality weights and exclusions without mixing cache entries. Displayed assertions establish this test’s expected checks, not a separate system-wide guarantee.
3. Purpose and risk addressed
Detect regression of this named behaviour; complete business-impact/invariant analysis remains in the curated cases or follow-up review.
4. Priority
High — provisional catalogue triage; subject to risk review.
5. Test type
Regression — provisional grouping from the declaration name.
6. Preconditions
Use section C plus the cited file’s fixtures and setup/teardown hooks. Suite context: top level. Do not infer starting state from the title.
7. Input and test data
No each/for parameter table on this declaration; its callback may still generate inputs. Input/operation expressions: I1, I2. Use disposable fixture data only.
8. Execution steps
1. Prepare the existing source test harness from section C. 2. Run pnpm test. 3. Locate this named declaration and its parameterized/conditional instances. 4. Compare the displayed assertions. 5. Record evidence and follow teardown. Not executed during this review.
9. Expected HTTP status, where applicable
See assertions A1 below. A numeric schema/helper expectation is not automatically an HTTP response contract.
10. Expected response headers and body
See assertions A1, A2, A3 below. Referenced variables remain symbolic; no universal response envelope is assumed.
11. Expected state changes
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
12. Expected emitted events or downstream calls, where applicable
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
13. Negative assertions: what must not happen
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
14. Cleanup and postconditions
Use the cited file’s hooks/finally blocks and section C. Restore mocks and remove only isolated test data.
15. Actual result
Not run — no execution evidence collected.
16. Evidence references
test/worker.test.mjs:318; assertion/input source links below. Source key: test/worker.test.mjs :: homepage negotiates quality weights and exclusions without mixing cache entries :: line 318 at this pinned revision.
17. Execution date
Not run.
18. Status and outstanding issues
Existing declaration documented; indirect helper assertions and full semantic coverage are not inferred from static extraction.
test/worker.test.mjs:318 — homepage negotiates quality weights and exclusions without mixing cache entries. Run pnpm test from /home/johnny/projects/toastmachine-resources-worker after preparing its existing test environment; this invokes the suite.
22. Implementation status
Existing automated test
23. Execution status
Not run
24. Known limitations
Static source inventory only. Loops, parameter tables, shared helpers and conditional modifiers can change executed counts. Indirect helper assertions are not expanded.
25. Follow-up actions
Reconcile runtime instances with this declaration, review symbolic fixtures and unasserted effects, and record execution evidence. Preserve this ID.
A2 line 345: expect(response.headers.get("content-type")).toContain(media)
A3 line 346: expect(response.headers.get("vary")).toContain("Accept")
Source inputs and operations
I1 line 336: worker.fetch(\n new Request("https://example.com/", {\n headers: accept ? { Accept: accept } : {},\n }),\n env,\n context,\n )
I2 line 337: new Request("https://example.com/", {\n headers: accept ? { Accept: accept } : {},\n })
RES-053 — documents corpus formats and serves the advertised shared guide
Field
Source-backed specification or observation
1. Test ID and name
RES-053 — documents corpus formats and serves the advertised shared guide
2. Requirement or guarantee
Source test intent: documents corpus formats and serves the advertised shared guide. Displayed assertions establish this test’s expected checks, not a separate system-wide guarantee.
3. Purpose and risk addressed
Detect regression of this named behaviour; complete business-impact/invariant analysis remains in the curated cases or follow-up review.
4. Priority
High — provisional catalogue triage; subject to risk review.
5. Test type
Contract — provisional grouping from the declaration name.
6. Preconditions
Use section C plus the cited file’s fixtures and setup/teardown hooks. Suite context: top level. Do not infer starting state from the title.
7. Input and test data
No each/for parameter table on this declaration; its callback may still generate inputs. Input/operation expressions: I1, I2, I3, I4, I5, I6, I7, I8, I9, I10. Use disposable fixture data only.
8. Execution steps
1. Prepare the existing source test harness from section C. 2. Run pnpm test. 3. Locate this named declaration and its parameterized/conditional instances. 4. Compare the displayed assertions. 5. Record evidence and follow teardown. Not executed during this review.
9. Expected HTTP status, where applicable
See assertions A1, A6, A7 below. A numeric schema/helper expectation is not automatically an HTTP response contract.
10. Expected response headers and body
See assertions A2, A3, A4, A5, A6, A8 below. Referenced variables remain symbolic; no universal response envelope is assumed.
11. Expected state changes
See assertions A11, A12 below. Expression grouping does not prove complete before/after state coverage.
12. Expected emitted events or downstream calls, where applicable
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
13. Negative assertions: what must not happen
See assertions A11 below. Only the shown negative/rejection checks are claimed; other forbidden effects require review.
14. Cleanup and postconditions
Use the cited file’s hooks/finally blocks and section C. Restore mocks and remove only isolated test data.
15. Actual result
Not run — no execution evidence collected.
16. Evidence references
test/worker.test.mjs:350; assertion/input source links below. Source key: test/worker.test.mjs :: documents corpus formats and serves the advertised shared guide :: line 350 at this pinned revision.
17. Execution date
Not run.
18. Status and outstanding issues
Existing declaration documented; indirect helper assertions and full semantic coverage are not inferred from static extraction.
test/worker.test.mjs:350 — documents corpus formats and serves the advertised shared guide. Run pnpm test from /home/johnny/projects/toastmachine-resources-worker after preparing its existing test environment; this invokes the suite.
22. Implementation status
Existing automated test
23. Execution status
Not run
24. Known limitations
Static source inventory only. Loops, parameter tables, shared helpers and conditional modifiers can change executed counts. Indirect helper assertions are not expanded.
25. Follow-up actions
Reconcile runtime instances with this declaration, review symbolic fixtures and unasserted effects, and record execution evidence. Preserve this ID.
A9 line 422: expect(text).toContain("Quality weights")
A10 line 423: expect(text).toContain("Accept: text/markdown")
A11 line 424: expect(text).not.toContain("sequence <= 1000")
A12 line 426: expect(text).toContain("messages.jsonl?before=901")
Source inputs and operations
I1 line 359: worker.fetch(\n new Request("https://example.com/how-to-use", {\n headers: { Accept: "text/markdown" },\n }),\n env,\n context,\n )
I2 line 360: new Request("https://example.com/how-to-use", {\n headers: { Accept: "text/markdown" },\n })
I3 line 369: worker.fetch(\n new Request("https://example.com/openapi.json"),\n env,\n context,\n )
I4 line 370: new Request("https://example.com/openapi.json")
I5 line 396: worker.fetch(\n new Request("https://example.com" + path, {\n headers: { Accept: "image/png" },\n }),\n env,\n context,\n )
I6 line 397: new Request("https://example.com" + path, {\n headers: { Accept: "image/png" },\n })
I7 line 404: worker.fetch(\n new Request("https://example.com" + path, {\n method: "HEAD",\n headers: { Accept: "image/png" },\n }),\n env,\n context,\n )
I8 line 405: new Request("https://example.com" + path, {\n method: "HEAD",\n headers: { Accept: "image/png" },\n })
I9 line 416: worker.fetch(\n new Request("https://example.com" + path),\n env,\n context,\n )
I10 line 417: new Request("https://example.com" + path)
RES-054 — honors the OpenAPI MIME type advertised in the API catalogue
Field
Source-backed specification or observation
1. Test ID and name
RES-054 — honors the OpenAPI MIME type advertised in the API catalogue
2. Requirement or guarantee
Source test intent: honors the OpenAPI MIME type advertised in the API catalogue. Displayed assertions establish this test’s expected checks, not a separate system-wide guarantee.
3. Purpose and risk addressed
Detect regression of this named behaviour; complete business-impact/invariant analysis remains in the curated cases or follow-up review.
4. Priority
High — provisional catalogue triage; subject to risk review.
5. Test type
Contract — provisional grouping from the declaration name.
6. Preconditions
Use section C plus the cited file’s fixtures and setup/teardown hooks. Suite context: top level. Do not infer starting state from the title.
7. Input and test data
No each/for parameter table on this declaration; its callback may still generate inputs. Input/operation expressions: I1, I2, I3, I4. Use disposable fixture data only.
8. Execution steps
1. Prepare the existing source test harness from section C. 2. Run pnpm test. 3. Locate this named declaration and its parameterized/conditional instances. 4. Compare the displayed assertions. 5. Record evidence and follow teardown. Not executed during this review.
9. Expected HTTP status, where applicable
See assertions A1 below. A numeric schema/helper expectation is not automatically an HTTP response contract.
10. Expected response headers and body
See assertions A1, A2, A3, A4 below. Referenced variables remain symbolic; no universal response envelope is assumed.
11. Expected state changes
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
12. Expected emitted events or downstream calls, where applicable
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
13. Negative assertions: what must not happen
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
14. Cleanup and postconditions
Use the cited file’s hooks/finally blocks and section C. Restore mocks and remove only isolated test data.
15. Actual result
Not run — no execution evidence collected.
16. Evidence references
test/worker.test.mjs:430; assertion/input source links below. Source key: test/worker.test.mjs :: honors the OpenAPI MIME type advertised in the API catalogue :: line 430 at this pinned revision.
17. Execution date
Not run.
18. Status and outstanding issues
Existing declaration documented; indirect helper assertions and full semantic coverage are not inferred from static extraction.
test/worker.test.mjs:430 — honors the OpenAPI MIME type advertised in the API catalogue. Run pnpm test from /home/johnny/projects/toastmachine-resources-worker after preparing its existing test environment; this invokes the suite.
22. Implementation status
Existing automated test
23. Execution status
Not run
24. Known limitations
Static source inventory only. Loops, parameter tables, shared helpers and conditional modifiers can change executed counts. Indirect helper assertions are not expanded.
25. Follow-up actions
Reconcile runtime instances with this declaration, review symbolic fixtures and unasserted effects, and record execution evidence. Preserve this ID.
I1 line 439: worker.fetch(\n new Request("https://example.com/openapi.json", {\n headers: { Accept: "application/vnd.oai.openapi+json" },\n }),\n env,\n context,\n )
I2 line 440: new Request("https://example.com/openapi.json", {\n headers: { Accept: "application/vnd.oai.openapi+json" },\n })
I3 line 451: worker.fetch(\n new Request("https://example.com/.well-known/api-catalog"),\n env,\n context,\n )
I4 line 452: new Request("https://example.com/.well-known/api-catalog")
RES-055 — serves the static kind catalogue without Corpus and agrees with OpenAPI and all agent docs
Field
Source-backed specification or observation
1. Test ID and name
RES-055 — serves the static kind catalogue without Corpus and agrees with OpenAPI and all agent docs
2. Requirement or guarantee
Source test intent: serves the static kind catalogue without Corpus and agrees with OpenAPI and all agent docs. Displayed assertions establish this test’s expected checks, not a separate system-wide guarantee.
3. Purpose and risk addressed
Detect regression of this named behaviour; complete business-impact/invariant analysis remains in the curated cases or follow-up review.
4. Priority
High — provisional catalogue triage; subject to risk review.
5. Test type
Contract — provisional grouping from the declaration name.
6. Preconditions
Use section C plus the cited file’s fixtures and setup/teardown hooks. Suite context: top level. Do not infer starting state from the title.
7. Input and test data
No each/for parameter table on this declaration; its callback may still generate inputs. Input/operation expressions: I1, I2, I3, I4, I5, I6, I7, I8, I9, I10. Use disposable fixture data only.
8. Execution steps
1. Prepare the existing source test harness from section C. 2. Run pnpm test. 3. Locate this named declaration and its parameterized/conditional instances. 4. Compare the displayed assertions. 5. Record evidence and follow teardown. Not executed during this review.
9. Expected HTTP status, where applicable
See assertions A1, A6, A8, A9 below. A numeric schema/helper expectation is not automatically an HTTP response contract.
10. Expected response headers and body
See assertions A1, A2, A3, A4, A5, A7, A13 below. Referenced variables remain symbolic; no universal response envelope is assumed.
11. Expected state changes
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
12. Expected emitted events or downstream calls, where applicable
See assertions A5, A8, A9, A10 below. No delivery guarantee beyond the checked expressions is inferred.
13. Negative assertions: what must not happen
See assertions A10, A11 below. Only the shown negative/rejection checks are claimed; other forbidden effects require review.
14. Cleanup and postconditions
Use the cited file’s hooks/finally blocks and section C. Restore mocks and remove only isolated test data.
15. Actual result
Not run — no execution evidence collected.
16. Evidence references
test/worker.test.mjs:466; assertion/input source links below. Source key: test/worker.test.mjs :: serves the static kind catalogue without Corpus and agrees with OpenAPI and all agent docs :: line 466 at this pinned revision.
17. Execution date
Not run.
18. Status and outstanding issues
Existing declaration documented; indirect helper assertions and full semantic coverage are not inferred from static extraction.
test/worker.test.mjs:466 — serves the static kind catalogue without Corpus and agrees with OpenAPI and all agent docs. Run pnpm test from /home/johnny/projects/toastmachine-resources-worker after preparing its existing test environment; this invokes the suite.
22. Implementation status
Existing automated test
23. Execution status
Not run
24. Known limitations
Static source inventory only. Loops, parameter tables, shared helpers and conditional modifiers can change executed counts. Indirect helper assertions are not expanded.
25. Follow-up actions
Reconcile runtime instances with this declaration, review symbolic fixtures and unasserted effects, and record execution evidence. Preserve this ID.
RES-056 — documents only implemented kind filters with repeated-parameter OR semantics
Field
Source-backed specification or observation
1. Test ID and name
RES-056 — documents only implemented kind filters with repeated-parameter OR semantics
2. Requirement or guarantee
Source test intent: documents only implemented kind filters with repeated-parameter OR semantics. Displayed assertions establish this test’s expected checks, not a separate system-wide guarantee.
3. Purpose and risk addressed
Detect regression of this named behaviour; complete business-impact/invariant analysis remains in the curated cases or follow-up review.
4. Priority
High — provisional catalogue triage; subject to risk review.
5. Test type
Contract — provisional grouping from the declaration name.
6. Preconditions
Use section C plus the cited file’s fixtures and setup/teardown hooks. Suite context: top level. Do not infer starting state from the title.
7. Input and test data
No each/for parameter table on this declaration; its callback may still generate inputs. Input/operation expressions: I1, I2. Use disposable fixture data only.
8. Execution steps
1. Prepare the existing source test harness from section C. 2. Run pnpm test. 3. Locate this named declaration and its parameterized/conditional instances. 4. Compare the displayed assertions. 5. Record evidence and follow teardown. Not executed during this review.
9. Expected HTTP status, where applicable
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
10. Expected response headers and body
See assertions A1, A3, A5, A6 below. Referenced variables remain symbolic; no universal response envelope is assumed.
11. Expected state changes
See assertions A5, A6, A7 below. Expression grouping does not prove complete before/after state coverage.
12. Expected emitted events or downstream calls, where applicable
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
13. Negative assertions: what must not happen
See assertions A5, A11 below. Only the shown negative/rejection checks are claimed; other forbidden effects require review.
14. Cleanup and postconditions
Use the cited file’s hooks/finally blocks and section C. Restore mocks and remove only isolated test data.
15. Actual result
Not run — no execution evidence collected.
16. Evidence references
test/worker.test.mjs:530; assertion/input source links below. Source key: test/worker.test.mjs :: documents only implemented kind filters with repeated-parameter OR semantics :: line 530 at this pinned revision.
17. Execution date
Not run.
18. Status and outstanding issues
Existing declaration documented; indirect helper assertions and full semantic coverage are not inferred from static extraction.
test/worker.test.mjs:530 — documents only implemented kind filters with repeated-parameter OR semantics. Run pnpm test from /home/johnny/projects/toastmachine-resources-worker after preparing its existing test environment; this invokes the suite.
22. Implementation status
Existing automated test
23. Execution status
Not run
24. Known limitations
Static source inventory only. Loops, parameter tables, shared helpers and conditional modifiers can change executed counts. Indirect helper assertions are not expanded.
25. Follow-up actions
Reconcile runtime instances with this declaration, review symbolic fixtures and unasserted effects, and record execution evidence. Preserve this ID.
A11 line 601: expect(text).not.toContain("do not offer kind filtering")
Source inputs and operations
I1 line 540: worker.fetch(new Request(`https://example.com${path}`), env, context)
I2 line 540: new Request(`https://example.com${path}`)
RES-057 — every OpenAPI message-kind schema agrees with the packaged canonical catalogue
Field
Source-backed specification or observation
1. Test ID and name
RES-057 — every OpenAPI message-kind schema agrees with the packaged canonical catalogue
2. Requirement or guarantee
Source test intent: every OpenAPI message-kind schema agrees with the packaged canonical catalogue. Displayed assertions establish this test’s expected checks, not a separate system-wide guarantee.
3. Purpose and risk addressed
Detect regression of this named behaviour; complete business-impact/invariant analysis remains in the curated cases or follow-up review.
4. Priority
High — provisional catalogue triage; subject to risk review.
5. Test type
Contract — provisional grouping from the declaration name.
6. Preconditions
Use section C plus the cited file’s fixtures and setup/teardown hooks. Suite context: top level. Do not infer starting state from the title.
7. Input and test data
No each/for parameter table on this declaration; its callback may still generate inputs. Input/operation expressions: I1, I2. Use disposable fixture data only.
8. Execution steps
1. Prepare the existing source test harness from section C. 2. Run pnpm test. 3. Locate this named declaration and its parameterized/conditional instances. 4. Compare the displayed assertions. 5. Record evidence and follow teardown. Not executed during this review.
9. Expected HTTP status, where applicable
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
10. Expected response headers and body
See assertions A4, A6, A7, A8 below. Referenced variables remain symbolic; no universal response envelope is assumed.
11. Expected state changes
See assertions A6 below. Expression grouping does not prove complete before/after state coverage.
12. Expected emitted events or downstream calls, where applicable
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
13. Negative assertions: what must not happen
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
14. Cleanup and postconditions
Use the cited file’s hooks/finally blocks and section C. Restore mocks and remove only isolated test data.
15. Actual result
Not run — no execution evidence collected.
16. Evidence references
test/worker.test.mjs:605; assertion/input source links below. Source key: test/worker.test.mjs :: every OpenAPI message-kind schema agrees with the packaged canonical catalogue :: line 605 at this pinned revision.
17. Execution date
Not run.
18. Status and outstanding issues
Existing declaration documented; indirect helper assertions and full semantic coverage are not inferred from static extraction.
test/worker.test.mjs:605 — every OpenAPI message-kind schema agrees with the packaged canonical catalogue. Run pnpm test from /home/johnny/projects/toastmachine-resources-worker after preparing its existing test environment; this invokes the suite.
22. Implementation status
Existing automated test
23. Execution status
Not run
24. Known limitations
Static source inventory only. Loops, parameter tables, shared helpers and conditional modifiers can change executed counts. Indirect helper assertions are not expanded.
25. Follow-up actions
Reconcile runtime instances with this declaration, review symbolic fixtures and unasserted effects, and record execution evidence. Preserve this ID.
Source assertions
A1 line 623: expect(catalogue).toEqual(KIND_CATALOGUE)
I1 line 616: worker.fetch(\n new Request(`https://example.com${path}`),\n env,\n context,\n )
I2 line 617: new Request(`https://example.com${path}`)
RES-058 — OpenAPI bypasses the previous schema cache and keeps both MIME variants current on GET and HEAD
Field
Source-backed specification or observation
1. Test ID and name
RES-058 — OpenAPI bypasses the previous schema cache and keeps both MIME variants current on GET and HEAD
2. Requirement or guarantee
Source test intent: OpenAPI bypasses the previous schema cache and keeps both MIME variants current on GET and HEAD. Displayed assertions establish this test’s expected checks, not a separate system-wide guarantee.
3. Purpose and risk addressed
Detect regression of this named behaviour; complete business-impact/invariant analysis remains in the curated cases or follow-up review.
4. Priority
High — provisional catalogue triage; subject to risk review.
5. Test type
Contract — provisional grouping from the declaration name.
6. Preconditions
Use section C plus the cited file’s fixtures and setup/teardown hooks. Suite context: top level. Do not infer starting state from the title.
7. Input and test data
No each/for parameter table on this declaration; its callback may still generate inputs. Input/operation expressions: I1, I2, I3, I4, I5, I6, I7. Use disposable fixture data only.
8. Execution steps
1. Prepare the existing source test harness from section C. 2. Run pnpm test. 3. Locate this named declaration and its parameterized/conditional instances. 4. Compare the displayed assertions. 5. Record evidence and follow teardown. Not executed during this review.
9. Expected HTTP status, where applicable
See assertions A17 below. A numeric schema/helper expectation is not automatically an HTTP response contract.
10. Expected response headers and body
See assertions A1, A2, A3, A4, A6, A7, A8, A9, A12, A13, A15, A16, A18, A19, A20 below. Referenced variables remain symbolic; no universal response envelope is assumed.
11. Expected state changes
See assertions A3, A5, A6, A8, A9, A10, A11, A12, A13, A14, A16 below. Expression grouping does not prove complete before/after state coverage.
12. Expected emitted events or downstream calls, where applicable
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
13. Negative assertions: what must not happen
See assertions A4 below. Only the shown negative/rejection checks are claimed; other forbidden effects require review.
14. Cleanup and postconditions
Use the cited file’s hooks/finally blocks and section C. Restore mocks and remove only isolated test data.
15. Actual result
Not run — no execution evidence collected.
16. Evidence references
test/worker.test.mjs:705; assertion/input source links below. Source key: test/worker.test.mjs :: OpenAPI bypasses the previous schema cache and keeps both MIME variants current on GET and HEAD :: line 705 at this pinned revision.
17. Execution date
Not run.
18. Status and outstanding issues
Existing declaration documented; indirect helper assertions and full semantic coverage are not inferred from static extraction.
test/worker.test.mjs:705 — OpenAPI bypasses the previous schema cache and keeps both MIME variants current on GET and HEAD. Run pnpm test from /home/johnny/projects/toastmachine-resources-worker after preparing its existing test environment; this invokes the suite.
22. Implementation status
Existing automated test
23. Execution status
Not run
24. Known limitations
Static source inventory only. Loops, parameter tables, shared helpers and conditional modifiers can change executed counts. Indirect helper assertions are not expanded.
25. Follow-up actions
Reconcile runtime instances with this declaration, review symbolic fixtures and unasserted effects, and record execution evidence. Preserve this ID.
Source assertions
A1 line 735: expect(response.headers.get("X-Cache")).toBe("MISS")
A2 line 736: expect(response.headers.get("Content-Type")).toContain(format)
A3 line 738: expect(spec.components.schemas.Message.properties.kind.items.enum).toEqual(\n KIND_NAMES,\n )
A4 line 741: expect(spec.paths["/register"].post.requestBody).toBeUndefined()
A5 line 742: expect(spec.paths["/messages"].get.operationId).toBe("listMessages")
A6 line 743: expect(\n spec.paths["/{endpoint_id}/createConversation"].post.requestBody.content[\n "application/json"\n ].schema.properties.content["x-max-utf16-code-units"],\n ).toBe(65536)
A7 line 748: expect(\n spec.paths["/{endpoint_id}/createRelationship"].post.responses["428"]\n .headers["X-ToastMachine-Onboarding"],\n ).toBeDefined()
A8 line 752: expect(spec.paths["/conversations"].get.description).toContain(\n "Every nonempty response page",\n )
A9 line 755: expect(spec.paths["/agents"].get.description).toContain(\n "offset=response.offset + response.agents.length",\n )
A10 line 761: expect(messagePage.properties.next.format).toBe("uri-reference")
A11 line 762: expect(messagePage.properties.previous.format).toBe("uri-reference")
A12 line 763: expect(\n spec.paths["/{endpoint_id}/createConversation"].post.responses["428"],\n ).toBeDefined()
A13 line 766: expect(\n spec.paths["/agents/{author_id}"].get.responses["200"].content[\n "application/json"\n ].schema.properties.longest_gap_seconds.type,\n ).toBe("number")
RES-059 — production discovery advertises the public origin while local development retains its own URL
Field
Source-backed specification or observation
1. Test ID and name
RES-059 — production discovery advertises the public origin while local development retains its own URL
2. Requirement or guarantee
Source test intent: production discovery advertises the public origin while local development retains its own URL. Displayed assertions establish this test’s expected checks, not a separate system-wide guarantee.
3. Purpose and risk addressed
Detect regression of this named behaviour; complete business-impact/invariant analysis remains in the curated cases or follow-up review.
4. Priority
High — provisional catalogue triage; subject to risk review.
5. Test type
Contract — provisional grouping from the declaration name.
6. Preconditions
Use section C plus the cited file’s fixtures and setup/teardown hooks. Suite context: top level. Do not infer starting state from the title.
7. Input and test data
No each/for parameter table on this declaration; its callback may still generate inputs. Input/operation expressions: I1, I2, I3, I4, I5, I6, I7. Use disposable fixture data only.
8. Execution steps
1. Prepare the existing source test harness from section C. 2. Run pnpm test. 3. Locate this named declaration and its parameterized/conditional instances. 4. Compare the displayed assertions. 5. Record evidence and follow teardown. Not executed during this review.
9. Expected HTTP status, where applicable
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
10. Expected response headers and body
See assertions A3, A4, A8, A9, A10 below. Referenced variables remain symbolic; no universal response envelope is assumed.
11. Expected state changes
See assertions A7, A9 below. Expression grouping does not prove complete before/after state coverage.
12. Expected emitted events or downstream calls, where applicable
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
13. Negative assertions: what must not happen
See assertions A9 below. Only the shown negative/rejection checks are claimed; other forbidden effects require review.
14. Cleanup and postconditions
Use the cited file’s hooks/finally blocks and section C. Restore mocks and remove only isolated test data.
15. Actual result
Not run — no execution evidence collected.
16. Evidence references
test/worker.test.mjs:793; assertion/input source links below. Source key: test/worker.test.mjs :: production discovery advertises the public origin while local development retains its own URL :: line 793 at this pinned revision.
17. Execution date
Not run.
18. Status and outstanding issues
Existing declaration documented; indirect helper assertions and full semantic coverage are not inferred from static extraction.
test/worker.test.mjs:793 — production discovery advertises the public origin while local development retains its own URL. Run pnpm test from /home/johnny/projects/toastmachine-resources-worker after preparing its existing test environment; this invokes the suite.
22. Implementation status
Existing automated test
23. Execution status
Not run
24. Known limitations
Static source inventory only. Loops, parameter tables, shared helpers and conditional modifiers can change executed counts. Indirect helper assertions are not expanded.
25. Follow-up actions
Reconcile runtime instances with this declaration, review symbolic fixtures and unasserted effects, and record execution evidence. Preserve this ID.
Source assertions
A1 line 802: expect(production.base_url).toBe("https://toastmachine.io")
A2 line 803: expect(local.base_url).toBe("http://127.0.0.1:8790")
A3 line 818: expect((await old.json()).servers[0].url).toContain("workers.dev")
A4 line 825: expect(response.headers.get("X-Cache")).toBe("MISS")
A5 line 827: expect(spec.servers[0].url).toBe(production.base_url)
A6 line 828: expect(spec.info.contact.url).toBe(production.base_url)
A7 line 829: expect(spec.info.description).toContain(\n "message APIs do not offer application/xml",\n )
A8 line 837: expect(spec.paths[path].get.responses["200"].content).toHaveProperty(\n format,\n )
A9 line 841: expect(\n spec.paths["/messages"].get.responses["200"].content,\n ).not.toHaveProperty("application/xml")
A10 line 849: expect((await localResponse.json()).servers[0].url).toBe(local.base_url)
Source inputs and operations
I1 line 806: new Request("https://toastmachine.io/openapi.json")
I6 line 844: worker.fetch(\n new Request(`${local.base_url}/openapi.json`),\n { NODE_CONFIG: config.env.local.vars.NODE_CONFIG },\n ctx,\n )
I7 line 845: new Request(`${local.base_url}/openapi.json`)
RES-060 — publishes the versioned relationship catalogue in each representation and routes assertion queries
Field
Source-backed specification or observation
1. Test ID and name
RES-060 — publishes the versioned relationship catalogue in each representation and routes assertion queries
2. Requirement or guarantee
Source test intent: publishes the versioned relationship catalogue in each representation and routes assertion queries. Displayed assertions establish this test’s expected checks, not a separate system-wide guarantee.
3. Purpose and risk addressed
Detect regression of this named behaviour; complete business-impact/invariant analysis remains in the curated cases or follow-up review.
4. Priority
High — provisional catalogue triage; subject to risk review.
5. Test type
Contract — provisional grouping from the declaration name.
6. Preconditions
Use section C plus the cited file’s fixtures and setup/teardown hooks. Suite context: top level. Do not infer starting state from the title.
7. Input and test data
No each/for parameter table on this declaration; its callback may still generate inputs. Input/operation expressions: I1, I2, I3, I4, I5, I6, I7, I8, I9, I10, I11, I12. Use disposable fixture data only.
8. Execution steps
1. Prepare the existing source test harness from section C. 2. Run pnpm test. 3. Locate this named declaration and its parameterized/conditional instances. 4. Compare the displayed assertions. 5. Record evidence and follow teardown. Not executed during this review.
9. Expected HTTP status, where applicable
See assertions A3, A7, A8 below. A numeric schema/helper expectation is not automatically an HTTP response contract.
10. Expected response headers and body
See assertions A4, A5, A6, A11 below. Referenced variables remain symbolic; no universal response envelope is assumed.
11. Expected state changes
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
12. Expected emitted events or downstream calls, where applicable
See assertions A7, A8, A9 below. No delivery guarantee beyond the checked expressions is inferred.
13. Negative assertions: what must not happen
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
14. Cleanup and postconditions
Use the cited file’s hooks/finally blocks and section C. Restore mocks and remove only isolated test data.
15. Actual result
Not run — no execution evidence collected.
16. Evidence references
test/worker.test.mjs:852; assertion/input source links below. Source key: test/worker.test.mjs :: publishes the versioned relationship catalogue in each representation and routes assertion queries :: line 852 at this pinned revision.
17. Execution date
Not run.
18. Status and outstanding issues
Existing declaration documented; indirect helper assertions and full semantic coverage are not inferred from static extraction.
test/worker.test.mjs:852 — publishes the versioned relationship catalogue in each representation and routes assertion queries. Run pnpm test from /home/johnny/projects/toastmachine-resources-worker after preparing its existing test environment; this invokes the suite.
22. Implementation status
Existing automated test
23. Execution status
Not run
24. Known limitations
Static source inventory only. Loops, parameter tables, shared helpers and conditional modifiers can change executed counts. Indirect helper assertions are not expanded.
25. Follow-up actions
Reconcile runtime instances with this declaration, review symbolic fixtures and unasserted effects, and record execution evidence. Preserve this ID.
Source assertions
A1 line 880: expect(catalogue.relationship_types).toEqual(\n RELATIONSHIP_CATALOGUE.relationship_types,\n )
A2 line 883: expect(catalogue.catalogue_version).toBe(2)
A10 line 939: expect(api.paths["/relationships"]).toBeDefined()
A11 line 940: expect(\n api.paths["/{endpoint_id}/createRelationship"].post.requestBody.content[\n "application/json"\n ].schema.$ref,\n ).toBe("#/components/schemas/CreateRelationshipRequest")
Source inputs and operations
I1 line 874: worker.fetch(\n new Request("https://example.com" + path),\n env,\n ctx,\n )
I2 line 875: new Request("https://example.com" + path)
I3 line 890: worker.fetch(\n new Request("https://example.com" + path, {\n method,\n headers: { Accept: accept },\n }),\n env,\n ctx,\n )
I4 line 891: new Request("https://example.com" + path, {\n method,\n headers: { Accept: accept },\n })
I5 line 905: worker.fetch(\n new Request("https://example.com" + path, {\n headers: { Accept: "image/png" },\n }),\n env,\n ctx,\n )
I6 line 906: new Request("https://example.com" + path, {\n headers: { Accept: "image/png" },\n })
I7 line 916: worker.fetch(\n new Request("https://example.com" + path, { method: "POST" }),\n env,\n ctx,\n )
I8 line 917: new Request("https://example.com" + path, { method: "POST" })
I9 line 924: worker.fetch(\n new Request(\n "https://example.com/relationship-assertions?message_id=[fixture identifier]",\n ),\n env,\n ctx,\n )
I10 line 925: new Request(\n "https://example.com/relationship-assertions?message_id=[fixture identifier]",\n )
I11 line 933: worker.fetch(\n new Request("https://example.com/openapi.json"),\n env,\n ctx,\n )
I12 line 934: new Request("https://example.com/openapi.json")
RES-061 — publishes one security contract and links discovery and OpenAPI to its served section
Field
Source-backed specification or observation
1. Test ID and name
RES-061 — publishes one security contract and links discovery and OpenAPI to its served section
2. Requirement or guarantee
Source test intent: publishes one security contract and links discovery and OpenAPI to its served section. Displayed assertions establish this test’s expected checks, not a separate system-wide guarantee.
3. Purpose and risk addressed
Detect regression of this named behaviour; complete business-impact/invariant analysis remains in the curated cases or follow-up review.
4. Priority
High — provisional catalogue triage; subject to risk review.
5. Test type
Security — provisional grouping from the declaration name.
6. Preconditions
Use section C plus the cited file’s fixtures and setup/teardown hooks. Suite context: top level. Do not infer starting state from the title.
7. Input and test data
No each/for parameter table on this declaration; its callback may still generate inputs. Input/operation expressions: I1, I2. Use disposable fixture data only.
8. Execution steps
1. Prepare the existing source test harness from section C. 2. Run pnpm test. 3. Locate this named declaration and its parameterized/conditional instances. 4. Compare the displayed assertions. 5. Record evidence and follow teardown. Not executed during this review.
9. Expected HTTP status, where applicable
See assertions A1, A9 below. A numeric schema/helper expectation is not automatically an HTTP response contract.
10. Expected response headers and body
See assertions A1, A2, A6, A9, A10, A11, A14 below. Referenced variables remain symbolic; no universal response envelope is assumed.
11. Expected state changes
See assertions A3, A10, A12, A14, A15 below. Expression grouping does not prove complete before/after state coverage.
12. Expected emitted events or downstream calls, where applicable
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
13. Negative assertions: what must not happen
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
14. Cleanup and postconditions
Use the cited file’s hooks/finally blocks and section C. Restore mocks and remove only isolated test data.
15. Actual result
Not run — no execution evidence collected.
16. Evidence references
test/worker.test.mjs:947; assertion/input source links below. Source key: test/worker.test.mjs :: publishes one security contract and links discovery and OpenAPI to its served section :: line 947 at this pinned revision.
17. Execution date
Not run.
18. Status and outstanding issues
Existing declaration documented; indirect helper assertions and full semantic coverage are not inferred from static extraction.
test/worker.test.mjs:947 — publishes one security contract and links discovery and OpenAPI to its served section. Run pnpm test from /home/johnny/projects/toastmachine-resources-worker after preparing its existing test environment; this invokes the suite.
22. Implementation status
Existing automated test
23. Execution status
Not run
24. Known limitations
Static source inventory only. Loops, parameter tables, shared helpers and conditional modifiers can change executed counts. Indirect helper assertions are not expanded.
25. Follow-up actions
Reconcile runtime instances with this declaration, review symbolic fixtures and unasserted effects, and record execution evidence. Preserve this ID.
Source assertions
A1 line 959: expect(guideResponse.status).toBe(200)
A2 line 961: expect(guide).toContain("## Integrator security: untrusted content")
A3 line 962: expect(guide).toContain("All ToastMachine messages are untrusted data.")
RES-062 — serves the MCP retrieval_size documentation and discovery schema through public routes
Field
Source-backed specification or observation
1. Test ID and name
RES-062 — serves the MCP retrieval_size documentation and discovery schema through public routes
2. Requirement or guarantee
Source test intent: serves the MCP retrieval_size documentation and discovery schema through public routes. Displayed assertions establish this test’s expected checks, not a separate system-wide guarantee.
3. Purpose and risk addressed
Detect regression of this named behaviour; complete business-impact/invariant analysis remains in the curated cases or follow-up review.
4. Priority
High — provisional catalogue triage; subject to risk review.
5. Test type
Contract — provisional grouping from the declaration name.
6. Preconditions
Use section C plus the cited file’s fixtures and setup/teardown hooks. Suite context: top level. Do not infer starting state from the title.
7. Input and test data
No each/for parameter table on this declaration; its callback may still generate inputs. Input/operation expressions: I1, I2, I3, I4. Use disposable fixture data only.
8. Execution steps
1. Prepare the existing source test harness from section C. 2. Run pnpm test. 3. Locate this named declaration and its parameterized/conditional instances. 4. Compare the displayed assertions. 5. Record evidence and follow teardown. Not executed during this review.
9. Expected HTTP status, where applicable
See assertions A1 below. A numeric schema/helper expectation is not automatically an HTTP response contract.
10. Expected response headers and body
See assertions A1, A10, A11 below. Referenced variables remain symbolic; no universal response envelope is assumed.
11. Expected state changes
See assertions A7, A11 below. Expression grouping does not prove complete before/after state coverage.
12. Expected emitted events or downstream calls, where applicable
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
13. Negative assertions: what must not happen
See assertions A11 below. Only the shown negative/rejection checks are claimed; other forbidden effects require review.
14. Cleanup and postconditions
Use the cited file’s hooks/finally blocks and section C. Restore mocks and remove only isolated test data.
15. Actual result
Not run — no execution evidence collected.
16. Evidence references
test/worker.test.mjs:995; assertion/input source links below. Source key: test/worker.test.mjs :: serves the MCP retrieval_size documentation and discovery schema through public routes :: line 995 at this pinned revision.
17. Execution date
Not run.
18. Status and outstanding issues
Existing declaration documented; indirect helper assertions and full semantic coverage are not inferred from static extraction.
test/worker.test.mjs:995 — serves the MCP retrieval_size documentation and discovery schema through public routes. Run pnpm test from /home/johnny/projects/toastmachine-resources-worker after preparing its existing test environment; this invokes the suite.
22. Implementation status
Existing automated test
23. Execution status
Not run
24. Known limitations
Static source inventory only. Loops, parameter tables, shared helpers and conditional modifiers can change executed counts. Indirect helper assertions are not expanded.
25. Follow-up actions
Reconcile runtime instances with this declaration, review symbolic fixtures and unasserted effects, and record execution evidence. Preserve this ID.
A2 line 1013: expect(text).toContain("## MCP retrieval size estimates")
A3 line 1014: expect(text).toContain("serialized_bytes` (non-negative integer)")
A4 line 1015: expect(text).toContain("estimated_tokens` (non-negative integer)")
A5 line 1016: expect(text).toContain("ceil(serialized_bytes / 4)")
A6 line 1017: expect(text).toContain("utf8-json-bytes-div4-v1")
A7 line 1018: expect(text).toContain("not a model-tokenizer count")
A8 line 1019: expect(text).toContain(\n "Other tools and raw HTTP resource bodies do not expose it",\n )
A9 line 1030: expect(spec["x-toastmachine-mcp"].retrieval_size.tools).toHaveLength(7)
A10 line 1031: expect(\n spec["x-toastmachine-mcp"].retrieval_size.schema.properties.serialized_bytes\n .type,\n ).toBe("integer")
A11 line 1035: expect(spec.components.schemas.Message.properties).not.toHaveProperty(\n "retrieval_size",\n )
Source inputs and operations
I1 line 1006: worker.fetch(\n new Request(`https://example.com${path}`),\n env,\n ctx,\n )
I2 line 1007: new Request(`https://example.com${path}`)
I3 line 1024: worker.fetch(\n new Request("https://example.com/openapi.json"),\n env,\n ctx,\n )
I4 line 1025: new Request("https://example.com/openapi.json")
RES-063 — endpoint routing distinguishes UUID syntax from the downstream authentication gate
Field
Source-backed specification or observation
1. Test ID and name
RES-063 — endpoint routing distinguishes UUID syntax from the downstream authentication gate
2. Requirement or guarantee
Source test intent: endpoint routing distinguishes UUID syntax from the downstream authentication gate. Displayed assertions establish this test’s expected checks, not a separate system-wide guarantee.
3. Purpose and risk addressed
Detect regression of this named behaviour; complete business-impact/invariant analysis remains in the curated cases or follow-up review.
4. Priority
High — provisional catalogue triage; subject to risk review.
5. Test type
Security — provisional grouping from the declaration name.
6. Preconditions
Use section C plus the cited file’s fixtures and setup/teardown hooks. Suite context: top level. Do not infer starting state from the title.
7. Input and test data
No each/for parameter table on this declaration; its callback may still generate inputs. Input/operation expressions: I1, I2. Use disposable fixture data only.
8. Execution steps
1. Prepare the existing source test harness from section C. 2. Run pnpm test. 3. Locate this named declaration and its parameterized/conditional instances. 4. Compare the displayed assertions. 5. Record evidence and follow teardown. Not executed during this review.
9. Expected HTTP status, where applicable
See assertions A1 below. A numeric schema/helper expectation is not automatically an HTTP response contract.
10. Expected response headers and body
See assertions A1 below. Referenced variables remain symbolic; no universal response envelope is assumed.
11. Expected state changes
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
12. Expected emitted events or downstream calls, where applicable
See assertions A2 below. No delivery guarantee beyond the checked expressions is inferred.
13. Negative assertions: what must not happen
No direct assertion identified for this field; inspect the referenced helpers before stating an expectation.
14. Cleanup and postconditions
Use the cited file’s hooks/finally blocks and section C. Restore mocks and remove only isolated test data.
15. Actual result
Not run — no execution evidence collected.
16. Evidence references
test/worker.test.mjs:1041; assertion/input source links below. Source key: test/worker.test.mjs :: endpoint routing distinguishes UUID syntax from the downstream authentication gate :: line 1041 at this pinned revision.
17. Execution date
Not run.
18. Status and outstanding issues
Existing declaration documented; indirect helper assertions and full semantic coverage are not inferred from static extraction.
test/worker.test.mjs:1041 — endpoint routing distinguishes UUID syntax from the downstream authentication gate. Run pnpm test from /home/johnny/projects/toastmachine-resources-worker after preparing its existing test environment; this invokes the suite.
22. Implementation status
Existing automated test
23. Execution status
Not run
24. Known limitations
Static source inventory only. Loops, parameter tables, shared helpers and conditional modifiers can change executed counts. Indirect helper assertions are not expanded.
25. Follow-up actions
Reconcile runtime instances with this declaration, review symbolic fixtures and unasserted effects, and record execution evidence. Preserve this ID.
Source assertions
A1 line 1078: expect(response.status).toBe(accepted ? 401 : 404)
A2 line 1079: expect(fetch).toHaveBeenCalledTimes(accepted ? 1 : 0)
I2 line 1067: new Request(`https://example.com/${id}/operation-token`)
F. Test categories
This maps selected cases rather than all source assertions. An unselected category is not automatically absent from the Worker or wider suite.
Category
Applicability and selected coverage
Happy-path behaviour
No dedicated selected case; applicability and wider coverage require investigation before marking Not applicable.
Input validation and boundary conditions
No dedicated selected case; applicability and wider coverage require investigation before marking Not applicable.
Authentication and authorisation
Selected cases: RES-003. Their limitations apply.
API and contract compatibility
Selected cases: RES-001, RES-002, RES-004, RES-005. Their limitations apply.
Data integrity and consistency
No dedicated selected case; applicability and wider coverage require investigation before marking Not applicable.
Idempotency and duplicate operations
No dedicated selected case; applicability and wider coverage require investigation before marking Not applicable.
Pagination and ordering
Selected cases: RES-004. Their limitations apply.
Dependency interactions
Selected cases: RES-002, RES-006. Their limitations apply.
Timeout, retry and partial-failure handling
No dedicated selected case; applicability and wider coverage require investigation before marking Not applicable.
Security and abuse prevention
Selected cases: RES-003. Their limitations apply.
Observability and diagnostics
Selected cases: RES-006. Their limitations apply. No complete logging, metrics, redaction or alerting guarantee is established here.
Regression tests
No dedicated selected case; applicability and wider coverage require investigation before marking Not applicable.
Integration and end-to-end tests
Selected cases: RES-001, RES-002. Their limitations apply.
G. Execution instructions
pnpm test checks the packaged protocol then runs Vitest. pnpm openapi:check runs generation, custom-record-schema validation and Redocly checks; it creates a generated API file. pnpm typecheck, pnpm lint and pnpm format:check are separate. The deploy workflow runs openapi:check, but does not invoke the application test suite.
Run documented commands from /home/johnny/projects/toastmachine-resources-worker only in the prepared test environment. None was run here. Commands are defined in package.json; release behaviour is declared in the CI/deploy workflow. Each case names its existing assertions or proposed location.
Execution layer
Instruction and evidence boundary
Setup and teardown
Use section C and the cited fixtures; record environment and revision and remove only disposable test data.
Unit tests
Use the package suite for the relevant direct-helper cases; no separate unit-only command is assumed.
Integration tests
Use the existing harness and service replacements. This does not prove a live cross-deployment guarantee.
Contract tests
Use the existing package suite. Resources also defines openapi:check; schema checks do not replace runtime assertions.
Proposed tests
Implement the specified case first; a proposed path is not an existing runnable test.
CI workflow references
The inspected deployment workflow does not invoke the application suite. Other build/type/schema checks do not establish these cases executed.
H. Results and evidence
Test ID
Last run
Result
Evidence
Notes
RES-001
Not run
Not run
Source/test inspection only; no execution log.
Existing automated test
RES-002
Not run
Not run
Source/test inspection only; no execution log.
Existing automated test
RES-003
Not run
Not run
Source/test inspection only; no execution log.
Existing automated test
RES-004
Not run
Not run
Source/test inspection only; no execution log.
Existing automated test
RES-005
Not run
Not run
Source/test inspection only; no execution log.
Partially covered
RES-006
Not run
Not run
Source/test inspection only; no execution log.
Proposed test, not implemented
Execution status
Meaning
Not run
No result is recorded in this review.
Passing
A recorded execution met the scoped assertions in its stated environment.
Failing
A recorded execution did not meet one or more assertions.
Blocked
An identified prerequisite prevents execution.
Skipped
Deliberate non-execution with a recorded reason.
Implementation status
Meaning
Existing automated test
Named assertions cover the scoped case, subject to its stated limitations.
Partially covered
Related assertions exist but specific expectations still need verification.
Proposed test, not implemented
New automated implementation is proposed, not claimed to exist.
Blocked by missing prerequisites
A specified prerequisite prevents implementation.
A passing related test does not establish every associated guarantee. Record command, environment, immutable revision, run date and output evidence before changing an execution result. Source inspection is not execution evidence.
Complete automated source catalogue results
These entries correspond to source declarations, not additional or runtime-expanded tests.
RES-005 is schema-example coverage, not proof of agreement with every real downstream response.
RES-006 proposes explicit characterization of cache read failure. No cache-failure recovery guarantee is stated by the current code.
A matching local SDK or sibling source does not establish the behaviour of a published SDK or hosted OpenAPI version.
Feed payload rendering has automated examples in test/structured-payload.test.mjs, but outage, malformed upstream feed data and cache failure paths need separate evidence.
No authoritative performance or cache-availability target was found; complete live environment isolation has not been verified.
Known flaky tests and historical failure rates: Unknown; execution history was not assessed. No new reproduced application defect is claimed. Follow-up ownership and execution dates remain unassigned. Characterization proposals may expose a requirement decision without establishing a stronger approved guarantee.