mirror of
https://github.com/azaion/gps-denied-onboard.git
synced 2026-06-22 16:21:12 +00:00
Oleksandr Bezdieniezhnykh
1f634c2604
ci/woodpecker/push/02-build-push Pipeline failed
- Modified the autodev state to reflect the current testing phase and details of the new `jetson-e2e` tests. - Enhanced the "How to Test" documentation to provide clearer instructions on the demo replay validation process, including video and tlog alignment steps. - Updated architectural documentation to include the new demo replay operator flow and its dependencies. - Documented the removal of deprecated auto-sync features and clarified the operator-facing UI for replay validation. - Added new entries in the dependencies table for upcoming tasks related to the demo replay flow. These changes improve clarity and usability for operators and developers working with the demo replay system.
2.7 KiB
2.7 KiB
Step 1: Bootstrap Structure Plan (default mode only)
Role: Professional software architect
Goal: Produce 01_initial_structure.md — the first task describing the project skeleton.
Constraints: This is a plan document, not code. The /implement skill executes it.
Steps
- Read
architecture.md, all component specs,system-flows.md,data_model.md, anddeployment/from DOCUMENT_DIR - Read problem, solution, and restrictions from
_docs/00_problem/and_docs/01_solution/ - Research best implementation patterns for the identified tech stack
- Document the structure plan using
templates/initial-structure-task.md
The bootstrap structure plan must include:
- Project folder layout with all component directories
- Shared models, interfaces, and DTOs
- Dockerfile per component (multi-stage, non-root, health checks, pinned base images)
docker-compose.ymlfor local development (all components + database + dependencies)docker-compose.test.ymlfor blackbox test environment (blackbox test runner).dockerignore- CI/CD pipeline file (
.github/workflows/ci.ymlorazure-pipelines.yml) with stages fromdeployment/ci_cd_pipeline.md - Database migration setup and initial seed data scripts
- Observability configuration: structured logging setup, health check endpoints (
/health/live,/health/ready), metrics endpoint (/metrics) - Environment variable documentation (
.env.example) - Test structure with unit and blackbox test locations
Self-verification
- All components have corresponding folders in the layout
- All inter-component interfaces have DTOs defined
- Dockerfile defined for each component
docker-compose.ymlcovers all components and dependenciesdocker-compose.test.ymlenables blackbox testing- CI/CD pipeline file defined with lint, test, security, build, deploy stages
- Database migration setup included
- Health check endpoints specified for each service
- Structured logging configuration included
.env.examplewith all required environment variables- Environment strategy covers dev, staging, production
- Test structure includes unit and blackbox test locations
Save action
Write todo/01_initial_structure.md (temporary numeric name).
Tracker action
Create a work item ticket for this task under the "Bootstrap & Initial Structure" epic. Write the work item ticket ID and Epic ID back into the task header.
Rename action
Rename the file from todo/01_initial_structure.md to todo/[TRACKER-ID]_initial_structure.md (e.g., todo/AZ-42_initial_structure.md). Update the Task field inside the file to match the new filename.
Blocking
BLOCKING: Present structure plan summary to user. Do NOT proceed until user confirms.