Initial commit: AirCoding V1.0.0 Alpha architecture baseline

Complete architecture document set with multi-model review remediation:
- Frozen interface contracts, runtime semantics, DB schemas
- Event/tool/error/provider registries
- Scheduler and main agent state machines
- C4 module/code views, solution architecture, baseline V1
- Multi-model review reports and joint assessment
- Phase-gate remediation complete (P0/P1/P2/UX resolved)
- Implementation plan with T-000A through T-045
- Reference folders kept as placeholders only

AirPlan/AGENTS.md

@@ -0,0 +1,69 @@
+# AGENTS.md
+
+## Workflow Root
+
+- This project uses `AirPlan/` as the workflow root.
+- Keep planning, execution state, ADR, C4, validation, debug, and plugin runtime data under `AirPlan/`.
+- The repo-root `AGENTS.md` only bootstraps into this file.
+
+<!-- AIRARC:BEGIN -->
+## AirArc Workflow
+
+1. Use `AirPlan/AGENTS.md` as the canonical project context entry point.
+2. Load and maintain:
+   - `AirPlan/docs/analysis/requirements.md`
+   - `AirPlan/docs/architecture/solution-architecture.md`
+   - `AirPlan/docs/architecture/baselineV1.md`
+   - `AirPlan/docs/architecture/db-schema-v1.md`
+   - `AirPlan/docs/architecture/event-registry-v1.md`
+   - `AirPlan/docs/architecture/tool-registry-v1.md`
+   - `AirPlan/docs/architecture/scheduler-state-machine-v1.md`
+   - `AirPlan/docs/architecture/prompt-layering-v1.md`
+   - `AirPlan/docs/architecture/provider-capability-matrix-v1.md`
+   - `AirPlan/docs/architecture/error-taxonomy-v1.md`
+   - `AirPlan/docs/architecture/artifact-naming-v1.md`
+   - `AirPlan/docs/architecture/scope-escalation-v1.md`
+   - `AirPlan/docs/architecture/security-model-v1.md`
+   - `AirPlan/docs/architecture/capability-trust-v1.md`
+   - `AirPlan/docs/architecture/cross-platform-matrix-v1.md`
+   - `AirPlan/docs/architecture/branch-deepcode-cli/`
+   - `AirPlan/docs/architecture/c4/module.md`
+   - `AirPlan/docs/architecture/c4/code-view.md`
+   - `AirPlan/docs/architecture/interface-contracts-v1.md`
+   - `AirPlan/docs/architecture/runtime-semantics-v1.md`
+   - `AirPlan/docs/architecture/多模型三视角审查联合评估.md`
+   - `AirPlan/docs/architecture/adr/`
+   - `AirPlan/docs/architecture/decisions-round-1.md`
+   - `AirPlan/docs/architecture/decisions-round-2.md`
+   - `AirPlan/docs/architecture/decisions-round-3.md`
+   - `AirPlan/docs/architecture/main-agent-state-machine.md`
+3. Produce or refine `AirPlan/plan.md` and `AirPlan/todo.md`.
+4. Keep plans optimized for lower-cost follow-up sessions, including scope, validation, file targets, and parallelization boundaries.
+5. AirArc is architecture-only: it may plan tasks and edit planning or architecture documents, but it must not write code or implement tasks directly.
+<!-- AIRARC:END -->
+
+<!-- AIRENG:BEGIN -->
+## AirEng Workflow
+
+1. Use `/aireng` as the sole scheduler for confirmed execution.
+2. Prefer `AirPlan/state/airarc/reviews/execution-plan.json`, then `AirPlan/state/airarc/reviews/parallel-review.json`, before falling back to local `AirPlan/todo.md`.
+3. Dispatch isolated `/airdo` subagents with bounded concurrency instead of defaulting to parent-thread coding.
+4. Monitor active workers on a 5-minute cadence, merge ready results, and continue later waves automatically when work remains.
+5. Keep `AirPlan/todo.md`, `AirPlan/plan.md`, `AirPlan/AGENTS.md`, ADR, and C4 docs synchronized during dispatch, monitoring, repair, and merge.
+6. AirEng owns global debug, XDB, repair, intervention, and document convergence, but it should only intervene directly for hard blockers and must return to scheduler mode immediately afterward.
+<!-- AIRENG:END -->
+
+<!-- AIRDO:BEGIN -->
+## AirDo Workflow
+
+1. Use `/airdo` for one narrow task slice from `AirPlan/todo.md`.
+2. Before editing, load:
+   - `AirPlan/AGENTS.md`
+   - `AirPlan/docs/architecture/adr/`
+   - `AirPlan/docs/architecture/c4/module.md`
+   - `AirPlan/plan.md`
+   - `AirPlan/todo.md`
+3. Keep task-local progress resumable in `AirPlan/state/airdo/`.
+4. When AirEng owns orchestration, return shared document changes through `documentUpdates`.
+5. Route GUI work through AirXDB, debugging through AirDbg, network evidence through AirNDB, and static analysis through AirSDB when needed.
+<!-- AIRDO:END -->