Keep Windows and POSIX commands behaviorally equivalent
The PowerShell reset resolves symlinks differently from the POSIX script and deletes a fixture path the other implementation refuses.
- Focused work estimate
- 4h + prerequisites
- Priority in the scenario
- High
- Engineering practice
- Cross-platform tooling · Shell safety · Contract testing
Estimated field mix
- DevOps70%
- Developer tooling30%
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-104 · Seed deterministic accounts without creating duplicates
- DDEV-105 · Reset only resources created by this workspace
- DDEV-106 · Report readiness by dependency instead of waiting blindly
Acceptance criteria
- Both entry points call one typed cross-platform core
- Path, quoting, exit status, and signal differences have contract tests
- Unsupported platform behavior fails visibly
Implementation constraints
- Tests use temporary directories and do not invoke destructive commands through another shell.
Verification to include
- Run the shared fixture matrix through both thin entry points.
- Use paths with spaces, links, and metacharacters and compare safe outcomes.
Deliverables
- Cross-platform command core and parity report
Rollout and recovery
Keep platform scripts as wrappers and review every behavioral difference.
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.