# Grand Project - Special One Preparation Package

## GPO Snapshot
- Snapshot timestamp: 2026-08-22 21:40:27 Pacific/Auckland
- Project: GP-PROJ-001 - Grand Project
- Overall state: 32.1% complete
- Canonical SHA: 82091a1ed67f8b40b48c63111cd2953c4f82bc86
- Documentation state: current through CMD-20260822-001; health Attention required

## Previous Round Closure
- Previous milestone/run: GP-M10 - SEO/Public Surface
- Git closure state: Recorded canonical SHA 82091a1ed67f8b40b48c63111cd2953c4f82bc86
- CI/smoke state: evidence exists in the reconciled roadmap and test history, with current review items still tracked separately.

## Current Milestone
- Current/next milestone: GP-M04 - Core Platform Services
- Ready queue count: 1
- Review queue count: 1
- Candidate queue kind: ready
- Candidate work item count: 1

## Ready Work
- GP-M04-009: Integrate production Auth login hotfix into canonical main [Ready] (GP-M04)

## Review Items
- GP-M04-007: Analytics Foundation [Needs Review] (GP-M04)

## Recommended Round Objective
- Work the ready queue in milestone order.

## Workstreams
## Integrate production Auth login hotfix into canonical main
- Task IDs: GP-M04-009
- Existing Minion: None
- Objective: production Auth login hotfix acceptance
- Detailed Objective: Production Auth is ahead of canonical main and needs reconciliation before analytics work resumes.
- Dependencies: None
- Relevant Components: app/routers/dashboard.py, app/templates/base.html, app/templates/dashboard.html
- Acceptance Criteria: GP-M04-009 is implemented against the canonical GPO state., GP-M04-009 is validated through the relevant route or service test coverage., The public dashboard and generated handoff remain consistent.
- Required Tests: python -m pytest tests/test_next_round.py, python -m pytest tests/test_documentation_part_d.py
- Collision Risk: Medium
- Parallelisation Suitability: Safe Parallel
- Why Now: GP-M04-009 is Ready, GP-M01 is closed, and an existing owner can be reused.

## Parallelisation
- Classification: Safe Parallel
- Reason: Only one ready workstream exists, so no scheduling collision is expected.

## Integration Order
- Document Generator first, Notifications second, then review the SEO carry-forward items if they remain unresolved.

## Minions On Demand
- Reuse a suitable existing Minion when one exists.
- Do not create a new Minion merely because a new workstream exists.
- Create a Minion only when the work is genuinely independent, no existing Minion is suitable, and ownership boundaries are safe.
- Register any new Minion in the coordinator control plane.
- MINION-10 remains the persistent Documentation Helper.

## Documentation Helper Gate
- Current documentation helper state: Attention required
- Documentation action: catch up documentation

## Git Startup Gate
- Previous completed accepted work must be committed, pushed, and synchronized before new work starts.

## Required Validation
- Preserve canonical hostname handling.
- Validate the changed routes and generated outputs through the public dashboard.
- Keep review items out of the ready queue until evidence supports promotion.

## Git Closure Gate
- Integration -> validation -> CI -> smoke tests -> documentation -> commit -> push -> remote SHA verification -> round closure.

## Completion Criteria
- The ready work is integrated and validated.
- The documentation helper is current or explicitly no-op.
- The generated prompt can be pasted directly into ChatGPT or Special One.
- The next-round plan is saved with a stable ID and current snapshot.

## Carry-Forward / Review Items
- GP-M04-007

## GPO Context
- Project: GP-PROJ-001 - Grand Project
- Canonical URL: https://home.waltons.co.nz
- Persistent helper: MINION-10