Task: Integrate static frontend architecture into project memory

Identity

Promote the accepted static Web + Go API architecture from source task 20260816-static-frontend-go-api-4f8c2a7d into canonical project memory.
Reconcile current state, architecture, domain language, decisions, success criteria, commitments, and task history with implementation commit b14b4fc.

Preserve historical task/proposal records while making canonical documents describe the implemented target unambiguously.
Record deployment as pending; do not infer live ACK routing or workload revisions from the public endpoint.
Keep Go authorization authoritative and record client guards as UX only.
Preserve the one-replica Go constraint until file storage is shared.

Canonical memory now describes a statically exported Next.js frontend served by unprivileged Nginx, with all runtime API, file, authentication, authorization, database, and WorkerLoop responsibilities in Go.
ADR-003, DEP-001, module/data-flow documentation, domain terminology, commitments, and current-state rollout guidance are aligned with b14b4fc.
The deployment gap is explicit: immutable image publication, target-cluster validation, and live authentication/file smoke tests remain outstanding.

check_project_docs.py: PASS.
check_doc_drift.py --task-id 20260816-integrate-static-frontend-2c7e91b4: PASS.
git diff --check: PASS.
Read-only sol_reviewer verdict: PASS after resolving the two identified documentation inconsistencies.

Publish immutable Web and Go image tags/digests, update ACK manifests, and run server-side dry-run before rollout.
Verify login, /api/auth/me, role boundaries, deep links, file routes, and health/readiness probes against the deployed revision.
Configure OSS/shared storage before Go Pod replacement or horizontal scale if uploads and generated results must persist.