docs: integrate static frontend architecture

2026-08-16 21:02:42 +08:00
1 parent b14b4fced7
commit bb50d06d1d
@@ -0,0 +1,60 @@
+# Task: Integrate static frontend architecture into project memory
+
+## Identity
+
+- Task ID: 20260816-integrate-static-frontend-2c7e91b4
+- Mode: Integration
+- Branch: codex/20260816-integrate-static-frontend-2c7e91b4
+- Worktree: D:\Datas\OthersProjects\NianAIGC-integrate-static-frontend-2c7e91b4
+- Base commit: b14b4fced70775eb50fde5b83192b72b09e3d86f
+- Owner: codex
+- Status: Ready for Integration
+
+## Scope
+
+- 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`.
+
+## Intent And Constraints
+
+- 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.
+
+## Outcome
+
+- 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.
+
+## Verification
+
+- `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.
+
+## Follow-ups
+
+- 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.
+
+## Promotion Candidates
+
+- None; canonical promotion is applied directly by this integration task.