47 lines
3.0 KiB
Markdown
47 lines
3.0 KiB
Markdown
# Current State
|
|
|
|
This file is the integrated default-branch snapshot. Feature tasks record progress in `30-worklog/tasks/{task_id}.md` and propose canonical changes for the Integration Gate. Feature tasks must not rewrite this file; it changes only in integration mode.
|
|
|
|
## Integrated Through
|
|
|
|
- `c44274f` (rebased integration of `84d84ba`, task `20260812-rds-postgres-adapter-7f2c1a`)
|
|
- `79d29bb` (cross-platform ACK manifest validation fix)
|
|
- `4485899` (task-scoped Next.js frontend plus Go backend target design and explicit not-implemented progress record)
|
|
- `064e155` (canonical ADR-003, architecture, current-state, history, and commitment promotion)
|
|
|
|
## Current Focus
|
|
|
|
The implemented application has a production deployment path for Alibaba Cloud ACK backed by direct Alibaba Cloud RDS PostgreSQL access. Local JSON remains an explicit development/test backend. ADR-003 now records the approved future Next.js frontend plus Go modular-monolith backend, but no Go implementation has been merged.
|
|
|
|
## Recently Completed
|
|
|
|
- 2026-08-12: Replaced the Supabase/PostgREST runtime path with a server-only `pg` adapter across data, account, and billing stores.
|
|
- 2026-08-12: Added versioned PostgreSQL migrations, strict backend selection, verified-CA TLS, database readiness, and ACK Web/Worker/migration manifests.
|
|
- 2026-08-12: Accepted and documented the Next.js frontend plus Go backend target, migration contracts, and acceptance criteria. Implementation was explicitly deferred; interrupted code drafts were discarded.
|
|
|
|
## In Progress
|
|
|
|
- Production environment values and the real RDS/ACK rollout are not yet validated in this repository environment.
|
|
- The Go backend migration has not started. Current code remains Next.js full-stack plus the HTTP-polling Node Worker under ACK-001.
|
|
|
|
## Next Recommended Steps
|
|
|
|
1. Before any Go implementation, turn the ADR-003 compatibility requirements into executable HTTP, Cookie, tenant, job, billing, storage, and Webhook contracts.
|
|
2. For the current implementation, back up RDS; verify roles, internal networking, TLS and CA; then run the reviewed migration/Web/Worker rollout if production deployment proceeds before the Go migration.
|
|
3. Keep the current Web at one replica until generated assets are externalized to OSS or another shared object store.
|
|
|
|
## Open Questions / Blockers
|
|
|
|
- Target RDS PostgreSQL version, connection budget, endpoint, TLS enforcement, CA bundle, database roles, and ACK network policy remain deployment inputs.
|
|
- Go implementation still needs a deliberate decision on whether to parse existing `zhinian_session` cookies without logout, plus measured API/backlog data before any later Worker split.
|
|
|
|
## Risky Areas
|
|
|
|
- Database migrations and least-privilege grants must be tested against the actual RDS instance before production cutover.
|
|
- Web pods still own runtime files; PostgreSQL does not make local uploads/generated assets safe for horizontal Web scaling.
|
|
- The current image runs as root; moving to a non-root user requires an explicit writable-path ownership design.
|
|
|
|
## Last Updated
|
|
|
|
2026-08-12
|