Files
kite/.planning/phases/14-selective-analysis-and-byte-cache/14-09-PLAN.md
T

110 lines
3.9 KiB
Markdown

---
phase: "14"
plan: "09"
type: execute
wave: 8
depends_on:
- "14-01"
- "14-02"
- "14-03"
- "14-04"
- "14-05"
- "14-06"
- "14-07"
- "14-08"
files_modified:
- AGENTS.md
- README.md
- SECURITY.md
- backend/main.py
- frontend/package.json
- .planning/ROADMAP.md
- .planning/STATE.md
- .planning/phases/14-selective-analysis-and-byte-cache/14-VALIDATION.md
- .planning/phases/14-selective-analysis-and-byte-cache/14-SECURITY.md
autonomous: true
requirements:
- ANALYZE-01
- ANALYZE-02
- ANALYZE-03
- ANALYZE-04
- ANALYZE-05
- ANALYZE-06
- ANALYZE-07
- CACHE-03
- CACHE-04
- CACHE-05
---
<objective>
Close Phase 14 with documentation, version bump, full verification gates, security evidence, and an atomic commit/push once all implementation plans pass.
Scope fence: do not add new feature behavior here except small fixes required by gate failures.
</objective>
<context>
@AGENTS.md
@README.md
@SECURITY.md
@.planning/ROADMAP.md
@.planning/STATE.md
@.planning/phases/14-selective-analysis-and-byte-cache/14-CONTEXT.md
@.planning/phases/14-selective-analysis-and-byte-cache/14-PATTERNS.md
</context>
<tasks>
<task type="auto">
<name>Task 1: Update docs, versions, roadmap, and closeout artifacts</name>
<files>AGENTS.md, README.md, SECURITY.md, backend/main.py, frontend/package.json, .planning/ROADMAP.md, .planning/STATE.md, .planning/phases/14-selective-analysis-and-byte-cache/14-VALIDATION.md, .planning/phases/14-selective-analysis-and-byte-cache/14-SECURITY.md</files>
<read_first>
- AGENTS.md
- README.md
- SECURITY.md
- backend/main.py
- frontend/package.json
</read_first>
<action>
Update current-state docs for Phase 14 completion, shared module maps for new analysis/cache services and routes, README feature/API/settings documentation, SECURITY threat register and gate evidence, ROADMAP plan checkboxes, and STATE next action. Apply the project version bump rule after Phase 14 completion using `backend/main.py` and `frontend/package.json` as sources of truth.
</action>
<acceptance_criteria>
- Docs describe selective analysis, byte cache, settings, API surface, and alpha/non-public status accurately.
- No secrets or provider item names from live data are included.
- ROADMAP marks Phase 14 complete and Phase 15 next.
- Version numbers are consistent across backend/frontend/docs.
</acceptance_criteria>
</task>
<task type="auto">
<name>Task 2: Run full gates and commit/push</name>
<files>all changed files</files>
<read_first>
- AGENTS.md testing, security, and git protocols
- .planning/phases/14-selective-analysis-and-byte-cache/14-SECURITY.md
</read_first>
<action>
Run focused Phase 14 tests, full backend suite, full frontend suite, `docker compose config --quiet`, Bandit, npm audit, Python dependency audit if local tooling supports Python 3.12, and an executable secret scan (`gitleaks` or `trufflehog`). Fix root-cause failures within scope. Commit and push the Phase 14 closeout only after gates pass or accepted pre-existing/tooling gaps are documented.
</action>
<acceptance_criteria>
- Backend and frontend tests pass with zero Phase 14 failures.
- Security scans report zero new high/critical issues.
- Secret scan reports no new secrets.
- Atomic commit uses the project commit format and is pushed.
</acceptance_criteria>
<verify><automated>docker compose config --quiet</automated></verify>
</task>
</tasks>
<verification>
1. `cd backend && pytest -q`
2. `cd frontend && npm run test`
3. `python3 -m bandit -r backend/ --exclude backend/tests`
4. `cd frontend && npm audit --audit-level=high`
5. `docker compose config --quiet`
6. Run available secret scan and document pre-existing findings only.
</verification>
<output>Create `.planning/phases/14-selective-analysis-and-byte-cache/14-09-SUMMARY.md` and mark Phase 14 complete when all gates pass.</output>