docs(docs): Ubuntu native development, Docker for services and isolation, separate VPS; pnpm check:all; CI status

RUST.md §1 (three environments, native install recipe, what stays in Docker
and why), §4 (pre-merge gate, workflow files prepared and never run), §5.8
(native run numbers against the builder image), §6; CLAUDE.md stack row,
commands, map, workflow rule; README quick start and verification; DEPLOY.md
CI status; WORKSPACE.md; TEST_STRATEGY.md; CHANGELOG; review Annex C.1
addendum of 2026-10-13.
This commit is contained in:
bchanot committed 2026-10-13 01:19:15 +02:00
1 parent 981a66f33b
commit 6e2bbec4b0
8 files changed
+233 -68

No files matched your search

@@ -985,3 +985,35 @@ frontend to load the module; no anatomy, PDF or business validation
migration (R2–R5); no avatar processing (R1); everything dockerised, the
production image produced in CI and pulled by the VPS; the live deployment
untouched; no tag or merge into main.
### C.1 Addendum 2026-10-13: development environment and CI status (owner brief after R0)
R0 delivered and validated on the architecture. The owner corrected the
development organisation before closing R0; these points amend Annex B §B.1
and VIII.4 and are implemented on `feature/rust-r0-foundation`:
- Three environments, three roles. The development machine is a self-hosted
Ubuntu server (native, not WSL, not the VPS) with Docker rootless: Rust is
developed and compiled **natively** there (user-level `rustup`, channel of
`rust-toolchain.toml`, `wasm32-unknown-unknown`, `wasm-bindgen-cli` and
`cargo-deny` at the pinned versions; `cargo check / test / build / clippy /
fmt` and the browser module build run without Docker). Docker on that
machine runs the Faunosteo services (Supabase), the worker in its hardened
container, the integration tests, the sandbox and seccomp proofs, and
builds the deployment images (multi-stage). The production VPS is separate
and never compiles.
- The R0 builder image is kept as the reproducible alternative
(`pnpm rust:check:docker`, `pnpm wasm:build:docker`) and as the reference
for a future runner; it is no longer the arbiter of daily work and is not
required for a compile or a test. The worker's isolation is unchanged.
- No CI/CD is operational on the forge (no runner, secret or registry). The
workflow files are prepared material for a separate CI/CD decision; a
workflow is never reported as passed before it has run on the forge. The
pre-merge gate is local: `pnpm check:all` (`scripts/check-all.sh`), which a
future runner calls as is.
- Target of that future step (not implemented): tests on every push and pull
request, Rust and TypeScript checks, PostgreSQL/RLS tests, Docker builds,
security checks, branch verification before a merge, image publication
only in an explicitly authorised workflow.
- R1 (the Step 8 worker) waits for the owner's final validation of this
correction; no deployment, no release 0.2.0.