# Local development for [repository]

## Supported path

- Mode and reason: [native / host source + container dependencies / full-container]
- Supported OS/CPU, runtime/package manager and Docker/Compose features if used:
- Prerequisites and actual source/config/lockfile paths:

## Configure and bootstrap

1. [Copy nonsecret examples to a private local config; required fields and precedence]
2. [Choose project/worktree identity and distinct ports/data ownership if parallel]
3. [Install locked dependencies; initialize/seed/migrate using the actual mechanism]

| Component | Host address | Container address | Readiness check | Persistent resource / owner |
|---|---|---|---|---|
| [component] | [actual loopback port or none] | [service DNS/port or N/A] | [actual check] | [resource] |

## Command contract

| Operation | Verified command and working directory | Expected result / scope |
|---|---|---|
| Validate configuration | [redacted/offline check] | [what it proves] |
| Start / run | [supported mode command] | [selected files/profile/environment] |
| Observe | [status/logs or local process output] | [success and failure indicators] |
| Test | [isolated test target] | [separate data/identities and exit status] |
| Debug / reload | [actual workflow] | [changed source is used] |
| Refresh dependencies | [lockfile-driven command] | [caches/volumes that may persist] |
| Stop | [data-preserving operation] | [what remains] |

## Data and recovery

- Data volumes/local paths, initialization and seed assumptions:
- Migration/backfill command and compatibility:
- Export/backup/restore when needed:
- Separate destructive reset procedure: exact targets, discarded data and user-authorized scope:
- Normal stop/rebuild does not reset persistent data; no global prune in bootstrap.

## Troubleshooting and evidence

| Symptom | Bounded check | Corrective action |
|---|---|---|
| [port/mount/readiness/config/permission failure] | [redacted check] | [owned resource only] |

State which modes, host platforms, image builds, hot reload, persistence and integration behavior were actually tested. Offline config validation alone is not a running-stack test.