docs: reconcile canonical memory with merged Go backend
This commit is contained in:
@@ -7,7 +7,9 @@ Track future-facing memory: promised follow-ups, unfinished loops, timed checks,
|
||||
| 2026-08-12 | Validate migration, TLS, permissions, and readiness against the real Alibaba Cloud RDS instance. | Before production cutover | Deployment owner | Open | Back up RDS, provision roles/CA/network access, then run the one-shot migration Job. |
|
||||
| 2026-08-12 | Keep Web at one replica until generated assets use OSS or another shared store. | Before raising Web replicas | Deployment owner | Open | Configure and validate external object storage. |
|
||||
| 2026-08-12 | Harden the runtime image to non-root after writable paths are designed. | Security hardening follow-up | Application owner | Open | Define ownership for runtime and settings paths, then update Docker/ACK security context. |
|
||||
| 2026-08-12 | Implement ADR-003 only after executable compatibility contracts exist. | Before starting the Go migration | Application owner | Open | Add golden tests for HTTP/Cookie/authorization/jobs/billing/storage/Webhooks, then implement vertical slices with single-writer cutover. |
|
||||
| 2026-08-12 | Implement ADR-003 only after executable compatibility contracts exist. | Before starting the Go migration | Application owner | Completed | Contracts exist under `contracts/`; Go implementation merged 2026-08-14. |
|
||||
| 2026-08-14 | Validate the merged Go backend against non-production RDS, real OSS, provider credentials, external Webhooks, and production-like Worker recovery before any Go traffic cutover. | Before Go cutover | Deployment owner | Open | Stand up non-production RDS/OSS and run the contract and recovery suites against the Go binary. |
|
||||
| 2026-08-14 | Decide Cookie cutover behavior (parse existing `zhinian_session` without logout vs. one-time global re-login) and confirm the public `/api/v1` support promise. | Before freezing cutover contracts | Product owner | Open | Product/release decision with explicit re-login or no-logout announcement. |
|
||||
|
||||
## Use
|
||||
|
||||
|
||||
Reference in New Issue
Block a user