# P01 Foundation Progress Report Date: 2026-07-18 ## Status P01 implementation, local verification, focused commits, and normal Forgejo branch publication are complete. The stage is ready for a `feat/p01-foundation → main` PR review. PD-0008 was resolved by the project owner with option A: - P01 includes basic non-sensitive Profile metadata CRUD. - P02 retains slots, active connections, auto-connect, switching protection, duplicate server-instance handling, and credential enrollment. ## Completed - Verified P00 PR #1 merged into `main` at `b3420e4`. - Created `feat/p01-foundation` from the merged baseline. - Added persistent SQLite under the Tauri application-data directory. - Added WAL, a bounded busy timeout, foreign-key enforcement, and transactional `user_version` migrations. - Added schema v2 for `connection_profiles`. - Verified fresh creation and v1-to-v2 migration without losing existing messages. - Verified five saved Profiles, full CRUD, and persistence after reopening the database. - Added bounded Tauri list/create/update/delete commands. - Added Rust-owned UUIDs and RFC 3339 timestamps. - Added URL normalization and rejection of embedded credentials, query strings, fragments, implicit HTTP, and invalid fingerprints. - Added strict IPC rejection for unknown Token, password, and API Key fields. - Added strict frontend ConnectionProfile Schemas. - Added a basic React Profile manager with list/create/edit/delete and explicit deletion confirmation. - Added no Token, password, API Key, Cookie, or NAS credential input. - Added a tracing writer that redacts output before writing. - Retained tray, close-to-tray, explicit quit, and single-instance focus behavior. - Added ADR-0004 for the Profile lifecycle and secret boundary. ## Verification | Check | Result | | ------------------------------------------------------- | --------------------------------------------------------------------------- | | Frontend format, ESLint, TypeScript, Vitest, Vite build | Passed; 3 Vitest tests | | Playwright Chromium | Passed; 1 test | | Rust fmt, Clippy with warnings denied, check | Passed | | Rust tests | Passed; 50 normal tests, 2 explicit manual tests ignored | | SQLite fresh schema v2 | Passed | | SQLite v1-to-v2 migration | Passed; existing message preserved | | Five Profile CRUD | Passed | | Profile close/reopen persistence | Passed | | Unknown secret IPC fields | Passed; rejected | | Protocol Schema export | Passed; no drift | | Tauri development startup | Passed; executable launched and was deliberately stopped after verification | | Tauri release executable | Passed | | NSIS installer | Passed; `0.1.0-alpha.1`, 3,827,899 bytes | | NSIS SHA-256 | `90EB68CDB5EAEDEA675050DA0F30DDAB5E8A0345FF176690A31FA5F66C818740` | | Forgejo feature branch | Passed; normal push through `2154c3b`, no force and no `main` merge | ## Security boundary - React never receives or submits credential values. - P01 IPC accepts only non-sensitive Profile fields. - Unknown input fields are rejected by Serde. - SQLite stores non-sensitive Profile metadata and reserves only an opaque `credential_reference`. - HTTP requires an explicit insecure-transport flag. - URLs containing credentials, query strings, or fragments are rejected. - No arbitrary command, unrestricted filesystem, registry-write, input-injection, or destructive file API was added. ## Build environment note The prior P01 release attempt found a missing generated `bindgen.rs` in the local `libsqlite3-sys 0.38.1` release cache. The official cached `bindgen_bundled_version.rs` was copied to the exact expected build-cache location, and the matching SHA-256 was recorded: `5B5A37A74DC728FB0BCD041867EB577C03C95E2FE46285262C589A3B1CD4BBAC` This was an environment cache repair only. No repository file or dependency version was changed. The current production build completed successfully using the repaired cache. ## Deferred to P02 - companion and operations slot assignment; - maximum two active connections; - REST/SSE activation and cancellation; - auto-connect validation; - Profile switching protection; - duplicate `server_instance_id` warnings; - formal credential enrollment, lookup, rotation, and deletion. ## Not claimed - Forgejo CI has not run. - No real AstrBot gateway compatibility is claimed. - No real credential was used. - No real UNC file transaction was executed. - No automatic merge to `main` was performed.