qa(advisoryai): verify codex companion and sync FLOW/task state
This commit is contained in:
@@ -0,0 +1,55 @@
|
||||
# Sprint 20260211_019 - AdvisoryAI Unchecked Feature Verification Batch 2
|
||||
|
||||
## Topic & Scope
|
||||
- Continue FLOW-based verification for remaining unchecked `advisoryai` features after previous batch completion.
|
||||
- Enforce problems-first checks before selecting new queued advisory features.
|
||||
- Produce Tier 0/1/2 evidence and move terminally verified features to `docs/features/checked/advisoryai/`.
|
||||
- Working directory: `src/AdvisoryAI`.
|
||||
- Expected evidence: `docs/qa/feature-checks/runs/advisoryai/**`, `docs/qa/feature-checks/state/advisoryai.json`, feature-file moves.
|
||||
|
||||
## Dependencies & Concurrency
|
||||
- Depends on `docs/qa/feature-checks/FLOW.md` and `src/AdvisoryAI/**`.
|
||||
- Cross-directory updates in `docs/features/**`, `docs/qa/feature-checks/**`, and `docs/implplan/**` are required for auditable verification.
|
||||
- Concurrent-agent constraint: if another module is already in `checking` and actively owned by other agents, do not take over contested files; record skip reason and continue available AdvisoryAI queue.
|
||||
|
||||
## Documentation Prerequisites
|
||||
- `docs/qa/feature-checks/FLOW.md`
|
||||
- `src/AdvisoryAI/AGENTS.md`
|
||||
- `docs/modules/advisory-ai/architecture.md`
|
||||
|
||||
## Delivery Tracker
|
||||
|
||||
### QA-AIAI-VERIFY-004 - Verify `ai-codex-zastava-companion`
|
||||
Status: DONE
|
||||
Dependency: none
|
||||
Owners: QA / Test Automation
|
||||
Task description:
|
||||
- Verify Codex/Zastava companion implementation claims in AdvisoryAI source, contracts, web endpoints, and companion test suite.
|
||||
- Capture Tier 0 source evidence, Tier 1 build/test evidence, and Tier 2 behavioral endpoint/service evidence.
|
||||
- Move feature file from `docs/features/unchecked/advisoryai/` to `docs/features/checked/advisoryai/` on pass.
|
||||
|
||||
Completion criteria:
|
||||
- [x] Tier 0 source verification completed.
|
||||
- [x] Tier 1 build and test verification completed.
|
||||
- [x] Tier 2 behavioral verification completed with fresh run evidence.
|
||||
- [x] State file updated and feature moved to checked.
|
||||
|
||||
## Execution Log
|
||||
| Date (UTC) | Update | Owner |
|
||||
| --- | --- | --- |
|
||||
| 2026-02-11 | Sprint created; started `ai-codex-zastava-companion` verification with run-001. | QA |
|
||||
| 2026-02-11 | `ai-codex-zastava-companion` verification completed (`run-001`): companion service, contracts, endpoint behavior, and companion test suite passed; feature moved to `docs/features/checked/advisoryai/`. | QA |
|
||||
| 2026-02-11 | Re-verified `ai-codex-zastava-companion` with fresh `run-002` Tier 0/1/2 artifacts and updated checked-doc verification links. | QA |
|
||||
| 2026-02-11 | Re-verified `ai-action-policy-gate` with `run-002` after adding action workflow integration coverage for approval audit path and idempotent replay. | QA |
|
||||
|
||||
## Decisions & Risks
|
||||
- Cross-module problem state detected: `attestor/ai-authority-classification-engine` is in `checking`.
|
||||
- Concurrency decision: treat cross-module ownership as obstacle and continue AdvisoryAI queue to avoid contested edits.
|
||||
- Risk: `dotnet test --filter` may emit `MTP0001` and execute full test assembly under Microsoft.Testing.Platform.
|
||||
- Mitigation: capture logs and record warning in run artifacts.
|
||||
- Decision: previous `NOT_FOUND` feature dossier was stale; current codebase includes `CodexZastavaCompanionService`, companion contracts, and `POST /v1/advisory-ai/companion/explain` endpoint with passing endpoint/service tests.
|
||||
- Decision: for targeted Tier 2 evidence, used xUnit runner class filters (`*.Tests.exe -class ...`) to avoid MTP filter ambiguity.
|
||||
- Decision: refreshed checked feature verification references to `run-002` where new evidence was captured.
|
||||
|
||||
## Next Checkpoints
|
||||
- AdvisoryAI batch complete; proceed to the next module selected by FLOW problem-state ordering.
|
||||
Reference in New Issue
Block a user