Workspace support for bounded project reviews and SQLite development #4
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "feat/project-delivery-loops"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Companion to https://git.z3k.sh/z3k-tech/console/pulls/25
Verification
PASS locally: PYTHONDONTWRITEBYTECODE=1 python3 -B -m unittest discover -s workspace -p test_delivery_loops.py; equivalent test_project_sqlite.py and test_project_workspaces.py suites; node workspace/test_card_brief.js; sh -n workspace/card-runner; sh -n workspace/dev-server; git diff --check.
The new suites run in the workspace Dockerfile as well. Full production amd64 image has not been built locally; no real provider-agent or production run is claimed. The existing workspace workflow triggers on main pushes only, not feature-branch PRs.
Rollout / limitations
Publish/roll this compatible runner before enabling the companion console features. Merging this PR publishes mutable workspace:1, which can roll existing Studios. Do not merge until that deployment is intended. No main branches or production resources were changed for this PR.
SQLite is Studio/dev only; no production/preview PVC configuration, data migration or backup is included. Limits are launches and time, not provider billing caps; shared workspace credentials mean review separation is not a hostile-agent sandbox. Reviews rely on structured independent-agent evidence. Console remains the owner of shipping approval and deployment verification.
Follow-up requested before merge: isolated worktrees + current-main validation
Verification: full Go suite passed against disposable PostgreSQL 17; go vet, templ generation and CSS build passed. Real local Git fixtures passed for private review worktrees, rebase conflicts, concurrent PR update leases, latest-main changes and paused/offline/expired execution. Human validation tests cover session/CSRF, all-repository evidence, stale main, separate approval and successful shipping. Desktop/mobile browser checks passed, using the browser-checking skill's local Chromium fallback because BrowserAct has no configured browser.