Diagnose local startup without collecting source or secrets
A support bundle recursively archives the workspace to explain startup failures, capturing source files and environment secrets.
- Focused work estimate
- 6h + prerequisites
- Priority in the scenario
- High
- Engineering practice
- Diagnostics · Privacy · Redaction
Estimated field mix
- DevOps60%
- Privacy engineering40%
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 support portal requires a database, cache, object store, and mail catcher. Setup lives in personal notes, reset scripts sometimes target shared resources, and offline work fails after package caches are cleared. Build a local-only development contract with synthetic data; no shared staging system or production credentials are supplied.
Setup prerequisites
- Environment variables
- Service health
- Database migrations
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
- DDEV-101 · Turn the setup notes into one preflight report
- DDEV-102 · Start local services only after validating port ownership
- DDEV-103 · Apply migrations exactly once during concurrent bootstrap
- DDEV-106 · Report readiness by dependency instead of waiting blindly
- DDEV-104 · Seed deterministic accounts without creating duplicates
- DDEV-105 · Reset only resources created by this workspace
- DDEV-108 · Keep Windows and POSIX commands behaviorally equivalent
Acceptance criteria
- Bundle allowlist contains tool versions, bounded health results, safe config identities, and recent bootstrap events
- Source, environment values, tokens, database rows, and payload logs are excluded
- User previews exact included files and fields
Implementation constraints
- Use sentinel secrets and synthetic source fixtures to prove exclusion.
Verification to include
- Generate a useful bundle for a failed readiness probe.
- Place sentinels in every prohibited source and confirm none appear in archive bytes.
Deliverables
- Redacted support bundle and leak regression suite
Rollout and recovery
Keep bundle generation local and user initiated.
Value of the work
For the engineer: Practice developer-environment automation, safe reset boundaries, portability, and diagnostic quality.
For the team: Reduce onboarding and support cost while making local dependencies and destructive operations explicit.
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.