Files
tiny-forge/plans/docker-watcher-core/CONTEXT.md
T
alexei.dolgolyov 0bb52f9ec6 chore: add feature planner setup for docker-watcher-core
Create structured plan files with 12 phases covering the full
implementation: scaffold, store, crypto, Docker/NPM clients,
registry poller, webhook, deployer, API layer, SvelteKit frontend,
embedding, and hardening.
2026-03-27 20:42:42 +03:00

1.9 KiB

Feature Context: Docker Watcher Core

Configuration

  • Development mode: Automated
  • Execution mode: Orchestrator
  • Strategy: Big Bang (with per-phase code quality reviews)
  • Build (Go): go build ./cmd/server/
  • Test (Go): go test ./...
  • Lint (Go): golangci-lint run
  • Build (Frontend): cd web && npm run build
  • Test (Frontend): cd web && npm test
  • Dev server: go run ./cmd/server/

Current State

Greenfield project. Only PLAN.md exists with the architecture document.

Temporary Workarounds

None yet.

Cross-Phase Dependencies

  • Phase 2 depends on Phase 1 (store CRUD for seed import)
  • Phases 3 and 4 are independent of each other (can run in parallel)
  • Phase 5 depends on Phase 1 (store for poll state)
  • Phase 6 depends on Phase 3 (Docker inspect for auto-creation) and Phase 1 (store)
  • Phase 7 depends on Phases 3, 4, 5 (Docker, NPM, registry clients)
  • Phase 8 depends on Phases 1-7 (wires everything to HTTP)
  • Phases 9 and 10 are independent of each other (can run in parallel)
  • Phase 11 depends on Phases 8, 9, 10 (embeds frontend, SSE wires to API)
  • Phase 12 depends on all prior phases

Deferred Work

None yet.

Failed Approaches

None yet.

Review Findings Log

None yet.

Phase Execution Log

Phase Agent Used Test Writer Parallel Notes
No phases executed yet

Environment & Runtime Notes

  • Platform: Windows 10 (development), Linux (deployment target)
  • Docker socket: /var/run/docker.sock (Linux) — development may need Docker Desktop
  • Go version: TBD (will be determined in Phase 1)

Implementation Notes

  • Big Bang strategy: intermediate phases skip build/tests, code quality reviews after every phase
  • Final phase (12) is the only phase where build + full test suite must pass
  • Phases 3+4 and 9+10 identified for parallel execution