KofTwentyTwo/Jarvis
2
0 Fork 0
Code Issues 111 Pull Requests 16 Actions Packages Projects Releases 4 Wiki Activity

v1.1 OQ-T2: promote fixture corpus format from harness-internal to spec-documented #82

New Issue
Open
opened 2026-05-12 19:30:30 +00:00 by KofTwentyTwo · 0 comments
KofTwentyTwo commented 2026-05-12 19:30:30 +00:00 (Migrated from github.com)
Copy link
Copy source

Summary

Promote the fixture corpus shape used by the eval harness + bus parity tests from harness-internal convention to spec-documented contract. Currently fixture format is implicit (`packages/Bus/Tests/BusTests/Fixtures/` + `webview/packages/bus/fixtures/` are byte-identical by convention enforced via `scripts/check-bus-harness-parity.sh`), but the shape isn't documented in the API spec.

Evidence

  • Migration plan §10: `.planning/architecture/JARVIS-API-MIGRATION-PLAN.md:734`.

Gap classification

"documentation gap" — convention exists, contract doesn't.

Recommended action

File against v1.1. Add a fixture-format section to `JARVIS-API-DESIGN-v1.0.md` (post-merge of v0.1 + v0.2). Document file naming, JSON shape, version-bump procedure when adding a new BusOutbound case.

Cross-references

  • Migration plan §10 v1.1
## Summary Promote the fixture corpus shape used by the eval harness + bus parity tests from harness-internal convention to spec-documented contract. Currently fixture format is implicit (\`packages/Bus/Tests/BusTests/Fixtures/\` + \`webview/packages/bus/fixtures/\` are byte-identical by convention enforced via \`scripts/check-bus-harness-parity.sh\`), but the shape isn't documented in the API spec. ## Evidence - Migration plan §10: \`.planning/architecture/JARVIS-API-MIGRATION-PLAN.md:734\`. ## Gap classification \"documentation gap\" — convention exists, contract doesn't. ## Recommended action File against v1.1. Add a fixture-format section to \`JARVIS-API-DESIGN-v1.0.md\` (post-merge of v0.1 + v0.2). Document file naming, JSON shape, version-bump procedure when adding a new BusOutbound case. ## Cross-references - Migration plan §10 v1.1
Sign in to join this conversation.
No Branch/Tag Specified
Labels
Clear labels
area:agent
area:build
area:bus
area:devtool
area:hud
area:logging
area:mcp
area:memory
area:vision
area:voice
audit-finding
bug
Something isn't working
 carry-forward
comment-cleanup
Comment / docstring cleanup per .planning/code-commenting-guide.md
 dependencies
Dependency updates
 documentation
Improvements or additions to documentation
 duplicate
This issue or pull request already exists
 enhancement
New feature or request
 epic
good first issue
Good for newcomers
 help wanted
Extra attention is needed
 invalid
This doesn't seem right
 javascript
Pull requests that update javascript code
 migration
question
Further information is requested
 severity:critical
severity:high
severity:low
severity:medium
wontfix
This will not be worked on
No labels area:build documentation enhancement severity:low
Milestone
No items
No Milestone v1.1 — Backlog (Orpheus, WhisperKit, Voice Log, presence, advanced)
Projects
Clear projects
No projects
Assignees
Clear assignees
forge-recovery (Forge Recovery) james.maes (James Maes)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: KofTwentyTwo/Jarvis#82