Document project delivery and continuity defaults

[hideouts-io]

The project-specific delivery and continuity procedure previously existed only in conversation, so future work could lose its checkout, preservation, review, and reporting safeguards. This records the procedure in AGENTS.md while keeping authorization outside repository-controlled content: Git and GitHub mutations require a trusted current user instruction covering the active task and applicable operation. The repository file, checkpoints, memory, and prior tasks do not grant permission.

When authorized, the workflow uses explicit staging, focused codex/ branches, ordinary non-force pushes, pull requests, and scoped CI repair. Drafts may be marked ready only after implementation and required checks are complete. Merges, releases, deployments, settings changes, force pushes, and device-changing operations require authorization that explicitly covers them.

Work sessions now begin by reading the workspace registry, applicable instructions and overrides, actual TODOs, documentation, memory, and checkpoint; confirming the canonical checkout; and inspecting the full Git, worktree, pull-request, and dirty state before editing. The publication review distinguishes machine-specific local absolute paths from legitimate project-relative paths.

Continuity checkpoints occur at safe boundaries after approximately one hour of material work and before pausing or ending. Durable-memory updates require a direct user request and use concise, nonsensitive summaries. The completion report includes delivery, validation, remaining macOS work, application visibility when applicable, and any publication-sensitive step that still needs authorization.

Validation:

• git diff --check
• Required-clause validation for all reviewed P2 and P3 fixes
• venv/bin/python -m mkdocs build --strict --clean

This is an instruction-only change; it does not change application or device behavior.