Export inventory-grid diagnostics without stock data
Support needs grid state but copying rows exposes inventory. Add an opt-in diagnostic download.
- Focused work estimate
- 1h 30m + prerequisites
- Priority in the scenario
- Low
- Engineering practice
- Observability · Data minimization
Estimated field mix
- Privacy engineering60%
- Frontend40%
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
Fictional supplier Reedworks uses a browser inventory table. Quantities are planning records, not live warehouse instructions.
Setup prerequisites
- Create synthetic SKUs with revisions and nullable quantities.
- Implement a local paginated adapter with conditional updates.
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
- CGRID-101 · Render unknown stock separately from zero
- CGRID-104 · Maintain inventory selection while sorted rows update
- CGRID-103 · Validate stock edits before saving
- CGRID-105 · Reject stale stock updates without losing drafts
- CGRID-106 · Define keyboard entry and escape for inventory cells
- CGRID-108 · Preview pasted stock ranges before applying them
- CGRID-109 · Report individual results for a partial stock save
Acceptance criteria
- Includes grid version and flags
- Omits quantities and SKU labels
- User previews the report
Implementation constraints
- Allowlist diagnostic fields.
Verification to include
- Export populated grid
- Verify secret-like fixture values are absent
Deliverables
- Exporter and exclusion checks
Rollout and recovery
Remove export if unexpected fields appear.
Value of the work
For the engineer: Practice grid interaction and concurrent edit recovery.
For the team: Inspect how changes protect operator intent during partial failures.
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.