de8c5c7135
Build [v1.14.31]
2026-04-25 12:53:41 +03:00
18cb466b50
docs(07.1-frontend-overhaul): update state and plan for Task 4
2026-04-25 12:44:59 +03:00
8dc8b7da9f
Build [v1.14.28]
2026-04-25 12:43:41 +03:00
ffcc60c38b
Build [v1.14.27]
2026-04-25 12:26:20 +03:00
701e30fb27
Build [v1.14.25]
2026-04-25 12:21:30 +03:00
7f5cfe637a
chore: cleanup audit source file
2026-04-23 16:36:56 +03:00
7c4441a962
Build [v1.14.22]
2026-04-23 16:16:04 +03:00
d9dffdc389
chore(07): remove deprecated bash scripts and legacy env files
2026-04-23 12:56:30 +03:00
0127831b58
docs(07-01): complete config structure and schemas plan summary
2026-04-23 12:42:49 +03:00
b7218175bb
docs(phase-7): create detailed phase plans for config consolidation (4 plans, 14 tasks)
2026-04-23 12:29:05 +03:00
dacf7d2921
docs(phase-7): capture consolidated context from structured discussion
...
Discussion locked in 4 key decisions:
1. YAML Format: All configs standardized on YAML (backend.yaml, frontend.yaml,
network.yaml, docker.yaml) for better structure and validation
2. Secrets Management: Separate config/secrets.yaml file (git-ignored) with
config/secrets.yaml.example template + strong documentation
3. Examples: Commit all .yaml.example files for developer onboarding
4. Scripts: Audit bash scripts for redundancy, then convert all needed ones
to Python for native YAML parsing and cleaner architecture
Immediate deprecation of inventory.env (no fallback after Phase 7).
Discussion log preserved in 07-DISCUSSION-LOG.md
Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com >
2026-04-23 12:20:53 +03:00
2b7a2b3a89
docs(phase-7): add configuration consolidation planning
...
- Phase 7: Config Consolidation
- CONTEXT.md: Defines scope, decisions, and requirements
- PLAN.md: 18-task implementation plan with detailed acceptance criteria
- Centralize all configs into config/ folder
- Update deploy scripts, backend loading, and documentation
- Maintain backward compatibility with inventory.env
Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com >
2026-04-23 12:07:39 +03:00
8aeabcf1f5
chore: major codebase cleanup and documentation consolidation
2026-04-23 11:44:33 +03:00
be3555d7cd
docs(phase-6): add dual-deployment requirement - docker and standalone modes
...
- Both Docker and start_server.sh standalone modes required
- Shared config files between both modes (no duplication)
- Single config source of truth (inventory.env)
- Both modes available for development and production use
2026-04-22 18:21:12 +03:00
4e6f940b75
refactor(phase-6): remove scale testing plan, simplify to docker + runbook
...
- Delete PLAN-02-SCALE-TESTING.md (scale testing deferred to v3)
- Rename PLAN-03-BACKUP-RUNBOOK to PLAN-02-OPERATIONAL-RUNBOOK
- Phase 6 now has 2 executable plans instead of 3
2026-04-22 18:18:00 +03:00
4ea9625928
docs(phase-6): revise context - single-instance deployment, Docker only, no scale testing
...
- Lock decision: Single-instance Docker deployment (not multi-site)
- Remove scale testing from Phase 6 scope (defer to v3)
- Simplify to 2 plans: Docker deployment + operational runbook
- Update success criteria to focus on reliability, not performance testing
2026-04-22 18:17:45 +03:00
4b7621fcd1
feat(6): phase 6 planning complete - deployment, scale testing, backup/restore
...
Phase 6 comprehensive plans ready for execution:
Plan 1: Docker Containerization & Deployment Automation (6 tasks)
- Enhance backend/frontend Dockerfiles with health checks
- Create deploy.sh for single-command deployment
- Environment automation and validation
- Quick start guide and troubleshooting docs
Plan 2: Scale Testing & Performance Optimization (6 tasks)
- Locust-based load testing framework (5 concurrent users)
- Database seeding (10K items with realistic data)
- Metrics collection (CPU, memory, response times)
- Performance baseline establishment and SLO documentation
- Health check monitoring automation
- Load test execution guide
Plan 3: Backup/Restore & Operational Runbook (7 tasks)
- Automated backup script (daily/weekly with retention)
- Restore validation and disaster recovery procedures
- Cron job configuration for scheduled backups
- Comprehensive operational runbook (deployment, scaling, troubleshooting)
- Health monitoring checklist (daily/weekly/monthly)
- Disaster recovery plan (3+ scenarios, <10min RTO)
- Operations documentation index and integration guide
Context document summarizes:
- Phase goal: Production-ready multi-site deployment
- Key decisions: Docker strategy, automation scope, scale limits
- Upstream dependencies: Phase 5 complete
- Success criteria: Single-command deploy, 10K items + 5 users <2s latency
- Backup strategy: Daily incremental, weekly full (30/90 day retention)
All plans include:
- Detailed task breakdowns (5-7 per plan)
- Acceptance criteria and testing procedures
- Dependencies and blockers
- Effort estimates and risk assessment
- Success metrics and monitoring guidance
Ready for execution phase (estimated 4-5 weeks total).
2026-04-22 18:13:35 +03:00
d0c0f8a84c
docs(phase-5): verification review - all blocking issues resolved, ready to merge
2026-04-22 18:09:18 +03:00
43094c42d1
docs(phase-5): code review fixes complete - auth headers and validation
2026-04-22 18:05:24 +03:00
62475ae0af
docs(phase-5): code review complete
2026-04-22 18:02:33 +03:00
a68d1bd23d
docs(5-plan-02): add summary - all 6 tasks completed, full test coverage
2026-04-22 17:44:55 +03:00
7f3ed6c666
docs(5.1): complete Phase 5 Plan 01 execution summary and session handover
...
- Created 5-PLAN-01-SUMMARY.md with full implementation report
- Updated SESSION_STATE.md with Session 38 completion details
- Phase 5 Plan 01 status: COMPLETED (5/5 tasks, all tests written)
- Ready for inventory page integration and Phase 5 Plan 02 execution
2026-04-22 17:43:02 +03:00
ae3ca2cbee
feat(5): phase 5 planning complete - 3 plans, 18 tasks covering quick adjust, search, exports
2026-04-22 17:36:36 +03:00
6471f6c86f
docs(5): phase 5 context finalized - quick quantity adjust, search, exports locked
2026-04-22 17:33:44 +03:00
965c7631b2
docs(4.1): phase 4.1 UAT complete - all 14 tests pass, ready for next phase
2026-04-22 17:02:36 +03:00
b0d93e8be8
docs(4.1): wave 3 execution complete - frontend components for search integration
2026-04-22 16:47:24 +03:00
42efe54265
docs(4.1): wave 2 execution complete - web scraping and spec extraction backend services
2026-04-22 16:38:21 +03:00
5ba488ea5e
docs(4.1): wave 1 execution complete - spare-parts classification foundation
2026-04-22 16:36:11 +03:00
ac87c4c06b
docs(4.1): planning complete - research + 3 executable plans
...
Phase 4.1: AI Prompt Enhancement — Spare Parts Deep Identification
Artifacts:
- 4.1-RESEARCH.md: Web scraping patterns, spare-parts classification, integration architecture
- 4.1-PLAN-01.md (Wave 1): Spare-parts whitelist + AI prompt enhancement (4 tasks)
- 4.1-PLAN-02.md (Wave 2): Web scraping service + backend integration (6 tasks)
- 4.1-PLAN-03.md (Wave 3): Frontend integration + end-to-end testing (7 tasks)
All 17 tasks verified:
✓ Concrete action steps with exact function signatures and file paths
✓ 100% verifiable acceptance criteria (grep, pytest, vitest, imports)
✓ Architecture aligned with all 11 CONTEXT.md decisions
✓ CLAUDE.md compliance: TypeScript strict, API tests, UI fidelity
✓ Wave dependencies correctly ordered
✓ Risk mitigation: rate limiting, timeout handling, offline graceful degradation
Ready for execution via /gsd-execute-phase 4.1
2026-04-22 16:28:26 +03:00
b90085cce5
docs(4.1): capture phase context and discussion log for AI spare parts deep identification
...
- AI Prompt: Detailed categorization to distinguish spare parts from consumables
- Search: Web scraping (requests + BeautifulSoup) to extract Google results, no API key
- Trigger: Automatic background search after AI extraction if category matches whitelist
- UX: Block until search completes, user reviews and edits all fields before save
- Mapping: Extract product type/specs/manufacturer/description to Notes field
- Retry on failure, user can skip if needed
2026-04-22 16:16:51 +03:00
