Vibecode HuntStand

You are building a lean indie version of HuntStand.

Create the following project files first, then implement the application by following them. Keep the files updated as decisions change. Do not collapse this into a single README or prompt.

===== README.md =====
# HuntStand indie build

## Goal

Build the smallest trustworthy replacement for the core HuntStand workflow for one developer or a tiny team.

## Scope

An offline-capable PWA map where you drop stands, cameras, food plots and trails, draw your own property polygon, log sits with wind and moon data, and export everything as GeoJSON.

## Quick start

1. Install the documented dependencies.
2. Copy `.env.example` to `.env`.
3. Run the development command chosen during implementation.
4. Complete the acceptance checks in `BUILD_PLAN.md`.

## Honest limits

This build deliberately does not replace:
- Nationwide parcel boundaries and landowner names, which are licensed data you cannot regenerate
- Fresh leaf-off aerial imagery and multi-source topo layers across the whole country
- Live sharing with a hunting party: shared markers, check-ins, and who is sitting where right now
- Native app polish offline: reliable background GPS tracks, tile prefetch, battery behavior
- Weather radar, rut and deer movement forecasts, and the constant map data refreshes

If those capabilities are essential, use HuntStand instead of pretending the gap is solved.

===== AGENTS.md =====
# Agent instructions

- Optimize for a working, understandable weekend build.
- Prefer the fewest moving parts that satisfy the brief.
- Do not invent cryptography, security guarantees, APIs, or compliance claims.
- Keep secrets out of source control and logs.
- Add focused tests for destructive, security-sensitive, and data-loss paths.
- Run the project checks before declaring the build complete.
- Record any deliberate shortcut in the README under "Tradeoffs".

===== BUILD_PLAN.md =====
# Build plan

## Original build brief

Build a personal, offline-first hunting scouting map as a PWA. No accounts, no server, no telemetry. All data stays on the device.

Stack, no substitutions:
- Vite + React + TypeScript
- MapLibre GL JS for the map
- Dexie (IndexedDB) for all storage
- vite-plugin-pwa for installability and tile caching
- Tailwind for styling, keep it plain and thumb-friendly

Map:
- Base layers switchable: satellite and topo from MapTiler using VITE_MAPTILER_KEY from .env, plus an OpenStreetMap raster fallback that needs no key
- "Download this area" button: prefetch tiles for the current viewport at zoom 12 to 16 into the service worker cache, show progress and cache size, allow clearing

Data model in Dexie: properties (name, GeoJSON polygon, acres computed), markers (type: stand, blind, camera, plot, trail cam, gate, sign, custom; lat, lng, notes, photo blob), tracks (recorded GPS line, timestamps), sits (marker id, start, end, wind dir and speed, temp, moon phase, sightings list with species, count, sex, time, free notes).

Features:
- Tap map to add a marker, choose type from an icon grid, attach a photo from the camera input
- Draw or import property polygons: file import for GeoJSON, KML and GPX, since county GIS portals hand those out. Show acreage.
- Record a walk: watchPosition into a track, works with screen on, stop and save
- Wind overlay: fetch current and hourly wind direction and speed from Open-Meteo for the map center, draw an arrow and a compass rose, and shade a simple downwind cone from any selected stand so it is obvious which stands are burned today
- Sunrise, sunset and moon phase computed locally with suncalc, no API
- Sit log: start a sit from a stand marker, it snapshots wind, temp and moon, then log sightings as you go
- Export and import everything as one JSON file, plus GeoJSON export of markers and tracks

Explicitly out of scope: parcel boundaries or landowner names (no legal source to pull from, the user imports their own), multi-user sharing, sync, push notifications, deer movement predictions.

Seed with two example markers and a sample property polygon so the UI is not empty. Write a README that states plainly what it does not do.

## Required capabilities

- A MapTiler or Mapbox key for satellite and topo tiles, or plain OpenStreetMap tiles if you accept no imagery
- County or state GIS parcel exports downloaded by hand for the properties you care about
- Open-Meteo for forecast and wind, no key needed
- A phone that will actually install a PWA and cache tiles

## Delivery order

1. Scaffold the smallest runnable application and document its commands.
2. Implement the primary data model and core workflow.
3. Add validation, safe failure states, and persistence.
4. Cover the critical path with automated tests.
5. Exercise a clean install from the README and fix every missing step.

## Done when

- A new user can go from clone to first successful workflow using only the README.
- The core workflow works without paid infrastructure unless the brief requires it.
- Tests cover the highest-risk behavior.
- Known limitations are explicit rather than hidden.

===== .env.example =====
# Copy to .env and document every variable when it is introduced.
# Never put real credentials in this file.

APP_ENV=development
# Add only values required by the selected implementation.

You are building a lean indie version of HuntStand.

Create the following project files first, then implement the application by following them. Keep the files updated as decisions change. Do not collapse this into a single README or prompt.

===== README.md =====
# HuntStand indie build

## Goal

Build the smallest trustworthy replacement for the core HuntStand workflow for one developer or a tiny team.

## Scope

An offline-capable PWA map where you drop stands, cameras, food plots and trails, draw your own property polygon, log sits with wind and moon data, and export everything as GeoJSON.

## Quick start

1. Install the documented dependencies.
2. Copy `.env.example` to `.env`.
3. Run the development command chosen during implementation.
4. Complete the acceptance checks in `BUILD_PLAN.md`.

## Honest limits

This build deliberately does not replace:
- Nationwide parcel boundaries and landowner names, which are licensed data you cannot regenerate
- Fresh leaf-off aerial imagery and multi-source topo layers across the whole country
- Live sharing with a hunting party: shared markers, check-ins, and who is sitting where right now
- Native app polish offline: reliable background GPS tracks, tile prefetch, battery behavior
- Weather radar, rut and deer movement forecasts, and the constant map data refreshes

If those capabilities are essential, use HuntStand instead of pretending the gap is solved.

===== AGENTS.md =====
# Agent instructions

- Optimize for a working, understandable weekend build.
- Prefer the fewest moving parts that satisfy the brief.
- Do not invent cryptography, security guarantees, APIs, or compliance claims.
- Keep secrets out of source control and logs.
- Add focused tests for destructive, security-sensitive, and data-loss paths.
- Run the project checks before declaring the build complete.
- Record any deliberate shortcut in the README under "Tradeoffs".

===== BUILD_PLAN.md =====
# Build plan

## Original build brief

Build a personal, offline-first hunting scouting map as a PWA. No accounts, no server, no telemetry. All data stays on the device.

Stack, no substitutions:
- Vite + React + TypeScript
- MapLibre GL JS for the map
- Dexie (IndexedDB) for all storage
- vite-plugin-pwa for installability and tile caching
- Tailwind for styling, keep it plain and thumb-friendly

Map:
- Base layers switchable: satellite and topo from MapTiler using VITE_MAPTILER_KEY from .env, plus an OpenStreetMap raster fallback that needs no key
- "Download this area" button: prefetch tiles for the current viewport at zoom 12 to 16 into the service worker cache, show progress and cache size, allow clearing

Data model in Dexie: properties (name, GeoJSON polygon, acres computed), markers (type: stand, blind, camera, plot, trail cam, gate, sign, custom; lat, lng, notes, photo blob), tracks (recorded GPS line, timestamps), sits (marker id, start, end, wind dir and speed, temp, moon phase, sightings list with species, count, sex, time, free notes).

Features:
- Tap map to add a marker, choose type from an icon grid, attach a photo from the camera input
- Draw or import property polygons: file import for GeoJSON, KML and GPX, since county GIS portals hand those out. Show acreage.
- Record a walk: watchPosition into a track, works with screen on, stop and save
- Wind overlay: fetch current and hourly wind direction and speed from Open-Meteo for the map center, draw an arrow and a compass rose, and shade a simple downwind cone from any selected stand so it is obvious which stands are burned today
- Sunrise, sunset and moon phase computed locally with suncalc, no API
- Sit log: start a sit from a stand marker, it snapshots wind, temp and moon, then log sightings as you go
- Export and import everything as one JSON file, plus GeoJSON export of markers and tracks

Explicitly out of scope: parcel boundaries or landowner names (no legal source to pull from, the user imports their own), multi-user sharing, sync, push notifications, deer movement predictions.

Seed with two example markers and a sample property polygon so the UI is not empty. Write a README that states plainly what it does not do.

## Required capabilities

- A MapTiler or Mapbox key for satellite and topo tiles, or plain OpenStreetMap tiles if you accept no imagery
- County or state GIS parcel exports downloaded by hand for the properties you care about
- Open-Meteo for forecast and wind, no key needed
- A phone that will actually install a PWA and cache tiles

## Delivery order

1. Scaffold the smallest runnable application and document its commands.
2. Implement the primary data model and core workflow.
3. Add validation, safe failure states, and persistence.
4. Cover the critical path with automated tests.
5. Exercise a clean install from the README and fix every missing step.

## Done when

- A new user can go from clone to first successful workflow using only the README.
- The core workflow works without paid infrastructure unless the brief requires it.
- Tests cover the highest-risk behavior.
- Known limitations are explicit rather than hidden.

===== .env.example =====
# Copy to .env and document every variable when it is introduced.
# Never put real credentials in this file.

APP_ENV=development
# Add only values required by the selected implementation.

You are building a production product version of HuntStand.

Create the following project files first, then implement the application by following them. Keep the files updated as decisions change. Do not collapse this into a single README or prompt.

===== PRODUCT.md =====
# HuntStand product brief

## Problem

Drawing pins on a map and logging what you saw at dawn is a trivial build, and an agent will hand you a working offline map in an afternoon. The part people actually pay for is the data underneath: nationwide parcel boundaries with owner names, recent high resolution aerial and topo imagery, and radar and wind layers stitched into one mobile app that works with no signal. That parcel layer is licensed, not scraped, and the imagery bill is real. Add the club side of it, where four people share the same map and see each other's stand check-ins live, and your local-only build stops covering the use case. Build the personal scouting notebook, keep paying if you need to know who owns the ridge behind you.

## Product outcome

An offline-capable PWA map where you drop stands, cameras, food plots and trails, draw your own property polygon, log sits with wind and moon data, and export everything as GeoJSON.

## Target user

A serious builder who needs a maintainable product foundation rather than a one-off demo.

## Required capabilities

- A MapTiler or Mapbox key for satellite and topo tiles, or plain OpenStreetMap tiles if you accept no imagery
- County or state GIS parcel exports downloaded by hand for the properties you care about
- Open-Meteo for forecast and wind, no key needed
- A phone that will actually install a PWA and cache tiles

## Explicit non-goals for v1

- Nationwide parcel boundaries and landowner names, which are licensed data you cannot regenerate
- Fresh leaf-off aerial imagery and multi-source topo layers across the whole country
- Live sharing with a hunting party: shared markers, check-ins, and who is sitting where right now
- Native app polish offline: reliable background GPS tracks, tile prefetch, battery behavior
- Weather radar, rut and deer movement forecasts, and the constant map data refreshes

## Success criteria

- The primary workflow is measurable end to end.
- Setup is reproducible in a clean environment.
- Failure, recovery, and support paths are documented.
- Product claims match what the implementation actually guarantees.

===== ARCHITECTURE.md =====
# Architecture

## Starting brief

Build a personal, offline-first hunting scouting map as a PWA. No accounts, no server, no telemetry. All data stays on the device.

Stack, no substitutions:
- Vite + React + TypeScript
- MapLibre GL JS for the map
- Dexie (IndexedDB) for all storage
- vite-plugin-pwa for installability and tile caching
- Tailwind for styling, keep it plain and thumb-friendly

Map:
- Base layers switchable: satellite and topo from MapTiler using VITE_MAPTILER_KEY from .env, plus an OpenStreetMap raster fallback that needs no key
- "Download this area" button: prefetch tiles for the current viewport at zoom 12 to 16 into the service worker cache, show progress and cache size, allow clearing

Data model in Dexie: properties (name, GeoJSON polygon, acres computed), markers (type: stand, blind, camera, plot, trail cam, gate, sign, custom; lat, lng, notes, photo blob), tracks (recorded GPS line, timestamps), sits (marker id, start, end, wind dir and speed, temp, moon phase, sightings list with species, count, sex, time, free notes).

Features:
- Tap map to add a marker, choose type from an icon grid, attach a photo from the camera input
- Draw or import property polygons: file import for GeoJSON, KML and GPX, since county GIS portals hand those out. Show acreage.
- Record a walk: watchPosition into a track, works with screen on, stop and save
- Wind overlay: fetch current and hourly wind direction and speed from Open-Meteo for the map center, draw an arrow and a compass rose, and shade a simple downwind cone from any selected stand so it is obvious which stands are burned today
- Sunrise, sunset and moon phase computed locally with suncalc, no API
- Sit log: start a sit from a stand marker, it snapshots wind, temp and moon, then log sightings as you go
- Export and import everything as one JSON file, plus GeoJSON export of markers and tracks

Explicitly out of scope: parcel boundaries or landowner names (no legal source to pull from, the user imports their own), multi-user sharing, sync, push notifications, deer movement predictions.

Seed with two example markers and a sample property polygon so the UI is not empty. Write a README that states plainly what it does not do.

## Boundaries

Separate the product into replaceable modules for interface, application logic, persistence, external integrations, and operational concerns. Keep domain logic independent from delivery frameworks and vendors.

## Production baseline

- Configuration: validated at startup with safe local defaults where possible.
- Security: least privilege, input validation, secret redaction, rate limits on abuse-prone paths, and no invented security primitives.
- Data: explicit schema and migrations, transactional writes where integrity matters, backup and restore instructions.
- Integrations: adapters around third-party providers, idempotent webhook or job processing, bounded retries, and timeouts.
- Observability: structured logs with request or operation IDs, an error-tracking hook, and health/readiness checks where a server exists.
- Quality: unit tests for domain rules, integration tests at module boundaries, and one end-to-end critical-path test.

## Decision records

For each major dependency, document why it was chosen, its failure mode, and how it can be replaced. Do not introduce infrastructure until a requirement justifies it.

===== AGENTS.md =====
# Agent instructions

- Read `PRODUCT.md` and `ARCHITECTURE.md` before changing code.
- Implement milestone by milestone; keep each change reviewable and leave the application runnable.
- Treat authentication, payments, encryption, imports, webhooks, and destructive actions as high-risk boundaries when present.
- Never invent cryptography or silently weaken a requirement to make a test pass.
- Use provider interfaces for external services and deterministic fakes in tests.
- Add migrations and rollback or recovery notes for persistent data changes.
- Log useful operational context without credentials, tokens, passwords, or personal data.
- Update documentation and run all checks before completing a milestone.

===== MILESTONES.md =====
# Delivery milestones

## M0 — Decisions and scaffold

- Confirm the runtime, persistence model, threat boundaries, and deployment target.
- Create a reproducible local environment and continuous checks.

## M1 — Core workflow

- Implement the smallest end-to-end product path with validation and tests.
- Keep integrations behind interfaces.

## M2 — Trust layer

- Add secure failure behavior, recovery paths, audit-relevant events, and data safeguards.
- Test abuse cases and destructive operations.

## M3 — Operability

- Add structured logs, error reporting hooks, health signals, backup/restore documentation, and deployment configuration.

## M4 — Release gate

- Run a clean-install test, critical-path end-to-end test, dependency review, and documented rollback exercise.
- Compare the shipped behavior with `PRODUCT.md` and publish remaining limitations.

===== OPERATIONS.md =====
# Operations

## Before release

- Validate configuration and secrets at startup.
- Define backup, restore, and rollback procedures and test them.
- Document logs, error tracking, health signals, and alert ownership.
- Set dependency update and vulnerability review expectations.

## Incident checklist

1. Contain the issue without destroying evidence or user data.
2. Record the timeline and affected scope.
3. Rotate exposed secrets and revoke compromised sessions or credentials.
4. Restore from a verified source when needed.
5. Document the root cause, remediation, and regression test.

## Launch constraint

Do not market omitted HuntStand capabilities as implemented. The v1 non-goals in `PRODUCT.md` remain user-visible limitations until they are deliberately delivered.

# HuntStand indie build

## Goal

Build the smallest trustworthy replacement for the core HuntStand workflow for one developer or a tiny team.

## Scope

An offline-capable PWA map where you drop stands, cameras, food plots and trails, draw your own property polygon, log sits with wind and moon data, and export everything as GeoJSON.

## Quick start

1. Install the documented dependencies.
2. Copy `.env.example` to `.env`.
3. Run the development command chosen during implementation.
4. Complete the acceptance checks in `BUILD_PLAN.md`.

## Honest limits

This build deliberately does not replace:
- Nationwide parcel boundaries and landowner names, which are licensed data you cannot regenerate
- Fresh leaf-off aerial imagery and multi-source topo layers across the whole country
- Live sharing with a hunting party: shared markers, check-ins, and who is sitting where right now
- Native app polish offline: reliable background GPS tracks, tile prefetch, battery behavior
- Weather radar, rut and deer movement forecasts, and the constant map data refreshes

If those capabilities are essential, use HuntStand instead of pretending the gap is solved.

# Agent instructions

- Optimize for a working, understandable weekend build.
- Prefer the fewest moving parts that satisfy the brief.
- Do not invent cryptography, security guarantees, APIs, or compliance claims.
- Keep secrets out of source control and logs.
- Add focused tests for destructive, security-sensitive, and data-loss paths.
- Run the project checks before declaring the build complete.
- Record any deliberate shortcut in the README under "Tradeoffs".

# Build plan

## Original build brief

Build a personal, offline-first hunting scouting map as a PWA. No accounts, no server, no telemetry. All data stays on the device.

Stack, no substitutions:
- Vite + React + TypeScript
- MapLibre GL JS for the map
- Dexie (IndexedDB) for all storage
- vite-plugin-pwa for installability and tile caching
- Tailwind for styling, keep it plain and thumb-friendly

Map:
- Base layers switchable: satellite and topo from MapTiler using VITE_MAPTILER_KEY from .env, plus an OpenStreetMap raster fallback that needs no key
- "Download this area" button: prefetch tiles for the current viewport at zoom 12 to 16 into the service worker cache, show progress and cache size, allow clearing

Data model in Dexie: properties (name, GeoJSON polygon, acres computed), markers (type: stand, blind, camera, plot, trail cam, gate, sign, custom; lat, lng, notes, photo blob), tracks (recorded GPS line, timestamps), sits (marker id, start, end, wind dir and speed, temp, moon phase, sightings list with species, count, sex, time, free notes).

Features:
- Tap map to add a marker, choose type from an icon grid, attach a photo from the camera input
- Draw or import property polygons: file import for GeoJSON, KML and GPX, since county GIS portals hand those out. Show acreage.
- Record a walk: watchPosition into a track, works with screen on, stop and save
- Wind overlay: fetch current and hourly wind direction and speed from Open-Meteo for the map center, draw an arrow and a compass rose, and shade a simple downwind cone from any selected stand so it is obvious which stands are burned today
- Sunrise, sunset and moon phase computed locally with suncalc, no API
- Sit log: start a sit from a stand marker, it snapshots wind, temp and moon, then log sightings as you go
- Export and import everything as one JSON file, plus GeoJSON export of markers and tracks

Explicitly out of scope: parcel boundaries or landowner names (no legal source to pull from, the user imports their own), multi-user sharing, sync, push notifications, deer movement predictions.

Seed with two example markers and a sample property polygon so the UI is not empty. Write a README that states plainly what it does not do.

## Required capabilities

- A MapTiler or Mapbox key for satellite and topo tiles, or plain OpenStreetMap tiles if you accept no imagery
- County or state GIS parcel exports downloaded by hand for the properties you care about
- Open-Meteo for forecast and wind, no key needed
- A phone that will actually install a PWA and cache tiles

## Delivery order

1. Scaffold the smallest runnable application and document its commands.
2. Implement the primary data model and core workflow.
3. Add validation, safe failure states, and persistence.
4. Cover the critical path with automated tests.
5. Exercise a clean install from the README and fix every missing step.

## Done when

- A new user can go from clone to first successful workflow using only the README.
- The core workflow works without paid infrastructure unless the brief requires it.
- Tests cover the highest-risk behavior.
- Known limitations are explicit rather than hidden.

# Copy to .env and document every variable when it is introduced.
# Never put real credentials in this file.

APP_ENV=development
# Add only values required by the selected implementation.

# HuntStand product brief

## Problem

Drawing pins on a map and logging what you saw at dawn is a trivial build, and an agent will hand you a working offline map in an afternoon. The part people actually pay for is the data underneath: nationwide parcel boundaries with owner names, recent high resolution aerial and topo imagery, and radar and wind layers stitched into one mobile app that works with no signal. That parcel layer is licensed, not scraped, and the imagery bill is real. Add the club side of it, where four people share the same map and see each other's stand check-ins live, and your local-only build stops covering the use case. Build the personal scouting notebook, keep paying if you need to know who owns the ridge behind you.

## Product outcome

An offline-capable PWA map where you drop stands, cameras, food plots and trails, draw your own property polygon, log sits with wind and moon data, and export everything as GeoJSON.

## Target user

A serious builder who needs a maintainable product foundation rather than a one-off demo.

## Required capabilities

- A MapTiler or Mapbox key for satellite and topo tiles, or plain OpenStreetMap tiles if you accept no imagery
- County or state GIS parcel exports downloaded by hand for the properties you care about
- Open-Meteo for forecast and wind, no key needed
- A phone that will actually install a PWA and cache tiles

## Explicit non-goals for v1

- Nationwide parcel boundaries and landowner names, which are licensed data you cannot regenerate
- Fresh leaf-off aerial imagery and multi-source topo layers across the whole country
- Live sharing with a hunting party: shared markers, check-ins, and who is sitting where right now
- Native app polish offline: reliable background GPS tracks, tile prefetch, battery behavior
- Weather radar, rut and deer movement forecasts, and the constant map data refreshes

## Success criteria

- The primary workflow is measurable end to end.
- Setup is reproducible in a clean environment.
- Failure, recovery, and support paths are documented.
- Product claims match what the implementation actually guarantees.

# Architecture

## Starting brief

Build a personal, offline-first hunting scouting map as a PWA. No accounts, no server, no telemetry. All data stays on the device.

Stack, no substitutions:
- Vite + React + TypeScript
- MapLibre GL JS for the map
- Dexie (IndexedDB) for all storage
- vite-plugin-pwa for installability and tile caching
- Tailwind for styling, keep it plain and thumb-friendly

Map:
- Base layers switchable: satellite and topo from MapTiler using VITE_MAPTILER_KEY from .env, plus an OpenStreetMap raster fallback that needs no key
- "Download this area" button: prefetch tiles for the current viewport at zoom 12 to 16 into the service worker cache, show progress and cache size, allow clearing

Data model in Dexie: properties (name, GeoJSON polygon, acres computed), markers (type: stand, blind, camera, plot, trail cam, gate, sign, custom; lat, lng, notes, photo blob), tracks (recorded GPS line, timestamps), sits (marker id, start, end, wind dir and speed, temp, moon phase, sightings list with species, count, sex, time, free notes).

Features:
- Tap map to add a marker, choose type from an icon grid, attach a photo from the camera input
- Draw or import property polygons: file import for GeoJSON, KML and GPX, since county GIS portals hand those out. Show acreage.
- Record a walk: watchPosition into a track, works with screen on, stop and save
- Wind overlay: fetch current and hourly wind direction and speed from Open-Meteo for the map center, draw an arrow and a compass rose, and shade a simple downwind cone from any selected stand so it is obvious which stands are burned today
- Sunrise, sunset and moon phase computed locally with suncalc, no API
- Sit log: start a sit from a stand marker, it snapshots wind, temp and moon, then log sightings as you go
- Export and import everything as one JSON file, plus GeoJSON export of markers and tracks

Explicitly out of scope: parcel boundaries or landowner names (no legal source to pull from, the user imports their own), multi-user sharing, sync, push notifications, deer movement predictions.

Seed with two example markers and a sample property polygon so the UI is not empty. Write a README that states plainly what it does not do.

## Boundaries

Separate the product into replaceable modules for interface, application logic, persistence, external integrations, and operational concerns. Keep domain logic independent from delivery frameworks and vendors.

## Production baseline

- Configuration: validated at startup with safe local defaults where possible.
- Security: least privilege, input validation, secret redaction, rate limits on abuse-prone paths, and no invented security primitives.
- Data: explicit schema and migrations, transactional writes where integrity matters, backup and restore instructions.
- Integrations: adapters around third-party providers, idempotent webhook or job processing, bounded retries, and timeouts.
- Observability: structured logs with request or operation IDs, an error-tracking hook, and health/readiness checks where a server exists.
- Quality: unit tests for domain rules, integration tests at module boundaries, and one end-to-end critical-path test.

## Decision records

For each major dependency, document why it was chosen, its failure mode, and how it can be replaced. Do not introduce infrastructure until a requirement justifies it.

# Agent instructions

- Read `PRODUCT.md` and `ARCHITECTURE.md` before changing code.
- Implement milestone by milestone; keep each change reviewable and leave the application runnable.
- Treat authentication, payments, encryption, imports, webhooks, and destructive actions as high-risk boundaries when present.
- Never invent cryptography or silently weaken a requirement to make a test pass.
- Use provider interfaces for external services and deterministic fakes in tests.
- Add migrations and rollback or recovery notes for persistent data changes.
- Log useful operational context without credentials, tokens, passwords, or personal data.
- Update documentation and run all checks before completing a milestone.

# Delivery milestones

## M0 — Decisions and scaffold

- Confirm the runtime, persistence model, threat boundaries, and deployment target.
- Create a reproducible local environment and continuous checks.

## M1 — Core workflow

- Implement the smallest end-to-end product path with validation and tests.
- Keep integrations behind interfaces.

## M2 — Trust layer

- Add secure failure behavior, recovery paths, audit-relevant events, and data safeguards.
- Test abuse cases and destructive operations.

## M3 — Operability

- Add structured logs, error reporting hooks, health signals, backup/restore documentation, and deployment configuration.

## M4 — Release gate

- Run a clean-install test, critical-path end-to-end test, dependency review, and documented rollback exercise.
- Compare the shipped behavior with `PRODUCT.md` and publish remaining limitations.

# Operations

## Before release

- Validate configuration and secrets at startup.
- Define backup, restore, and rollback procedures and test them.
- Document logs, error tracking, health signals, and alert ownership.
- Set dependency update and vulnerability review expectations.

## Incident checklist

1. Contain the issue without destroying evidence or user data.
2. Record the timeline and affected scope.
3. Rotate exposed secrets and revoke compromised sessions or credentials.
4. Restore from a verified source when needed.
5. Document the root cause, remediation, and regression test.

## Launch constraint

Do not market omitted HuntStand capabilities as implemented. The v1 non-goals in `PRODUCT.md` remain user-visible limitations until they are deliberately delivered.

$ choose a build depth, inspect the files, then open the complete pack in your agent · this prompt is generated from the build plan · improve it via PR