5 Commits

Include renames

Author	SHA1	Message	Date
weichen	d7f43acf31	Align multi-instance bootstrap with the U3 account contract ... Why: The multi-instance acceptance test still created alice with a literal password; backend U3 replaced local password-bearing creation with trusted pending-account activation, so the first pin bump past U3 failed test-pg with RECOVERY_CONTRACT_REPLACED. The seam was left pending by the U3 task and this PR is the first to cross it. Evidence: Full TestTwoInstancesOverSharedPG passes against a disposable PostgreSQL 16 container (identity ensure -> bootstrap-admin -> pending create with activation key -> key redemption -> grant-setup password -> api key -> all cross-instance scenarios, 15s). Impact: Test-only bootstrap rewrite (deployment-level identity ensured once per pair, admin bootstrapped first, alice activated through the key redemption and grant-setup password flow); no product code changes. Refs: Dev task feature/pptx-gate-reference-integrity; backend U3 #198	2026-10-15 03:11:08 +00:00
weichen	ecf310fcf1	Fix multi-instance seeding for system-managed settings and repin backend ... Why: The follow-up CI exposed that backend #188 broke the Dev multi-instance suite: serve --mock seeded runtime.mock at the user scope, which system-managed settings now reject, so instances never became healthy. Backend #190 seeds the startup flag into the system scope; this PR repins and drops the now-invalid alice user-scope write. Evidence: Backend #190 CI success at head 0af1ebc (GATE); this PR's composite CI re-runs make test-multi-instance (GATE for the fix). Impact: backend pin 741da4a; multi-instance test comments updated to the system-managed regime. Refs: Backend #188, #190.	2026-10-13 04:47:23 +00:00
weichenandCursor	ca0ab46d5b	Pin the blobstore fallback and cover cross-instance uploads ... Why: an unset object store must keep artifact bytes available to the other process, which the store-level test does not execute. Evidence: cross_artifact_roundtrip failed with EOF on backend c6fb130 and passed on 46073d30 (SELF, isolated u7drill-k4). Impact: Dev now builds the fixed backend. Second-instance write traffic stays closed. Refs: modules/backend tests/integration/multi-instance/multi_instance_test.go Co-authored-by: Cursor <cursoragent@cursor.com>	2026-10-13 01:26:29 +00:00
weichenandCursor	a5d44df505	Clear must_change before API-key use in multi-instance U7 ... Why: Backend login_keys gate blocks Key traffic while must_change_password is set; U7 failed on PUT settings/user 403. Evidence: go test -c multi-instance compiles; CI test-pg will GATE. Impact: loginAlice does session password change alicePass0→alicePass. Refs: Dev PR #426; Backend #170 pin e7b70c2 Co-authored-by: Cursor <cursoragent@cursor.com>	2026-10-12 05:24:02 +00:00
weichen	f705f99b8f	Add U7 two-process acceptance, k6 load harness and release checklist ... Why: collaboration storage U7 (proposal sections 3/5/7) requires two-process HTTP-level acceptance over shared PG, a reproducible load-test entry honoring the load contract, and an auditable pre-release checklist; capacity windows and dual-host runs need user-scheduled resources, so the deliverable here is the verifiable entry, not capacity claims. Evidence: make test green (composite); make test-multi-instance green locally against an isolated PG (five scenarios incl. crash-takeover and restart invariants); run_load.sh --profile smoke end-to-end green (SSE probe p95~18ms, zero seq duplicates, stack auto-recycled); backend pinned to feature branch with the three cross-instance fixes. Impact: new tests/integration/multi-instance (CI test-pg job step), new tests/load/collaboration (k6 + SSE probe + run_load.sh), release checklist at docs/release-multi-instance.md; no runtime behavior change in Dev repo itself. Refs: backend PR #164; task card feature/u7-load-fault-release.	2026-10-12 02:31:35 +00:00