Test a packaged client from a clean consumer directory
The client works in the monorepo but its published archive omits runtime files.
- Focused work estimate
- 2h 30m + prerequisites
- Priority in the scenario
- High
- Engineering practice
- Packaging · Module systems
Estimated field mix
- Developer tooling70%
- Quality engineering30%
Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence.
Review it, then add it to your workspace.
The board opens an editable draft; nothing is saved until you confirm it. Sign-in and workspace permissions apply, and Demo boards remain ephemeral.
Project context
A fictional partner platform publishes TypeScript clients. Generator upgrades create noisy diffs, occasional runtime mismatches, and uncertainty about which schema was packaged.
Setup prerequisites
- Create a small public API schema and two local mock server versions; use a temporary local package registry or archive files.
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
- BSDKGEN-101 · Record the exact inputs behind a generated client
- BSDKGEN-102 · Normalize schema ordering without changing semantics
- BSDKGEN-103 · Separate transport code from generated resource methods
- BSDKGEN-104 · Represent nullable and optional fields distinctly in clients
- BSDKGEN-105 · Generate errors that preserve safe machine-readable details
Acceptance criteria
- Install the local archive outside the workspace.
- Exercise ESM imports and declared type exports.
- Verify the archive excludes fixtures and credentials.
Implementation constraints
- Use local archives; no public publication or real account required.
Verification to include
- Run a request against the mock server.
- Remove an exported file and detect the package failure.
Deliverables
- Clean-consumer smoke check.
Rollout and recovery
Gate local release candidates on archive validation.
Value of the work
For the engineer: Practice reproducible generation, compatibility reviews, and package provenance.
For the team: Reduce partner integration surprises with reviewable clients and recoverable releases.
Evidence boundaries
Outcome Evidence: Tests, patches, and runbooks are requested deliverables. They become Outcome Evidence only through a qualified Mission and immutable Evidence IDs.
Ownership Evidence: Independent adaptation must be observed under a declared verification policy and cite immutable Evidence IDs. Completing a planning ticket establishes no Ownership Evidence.