# Development Progress ## Current phase P01 foundation was merged through Forgejo PR #2 at `885abd1`. Development now continues on `feat/p02-dual-connections`, starting with persistent companion/operations slot assignment and its local safety constraints. ## Completed - Read `AGENTS.md`, the architecture, implementation task, and Forgejo predevelopment workflow documents in full. - Verified the Windows, Git, Node.js, package-manager, WebView2, Rust, Tauri, and MSVC environment. - Initialized and normalized Git, established `main`, and pushed the baseline without force. - Completed and merged P00 through Forgejo PR #1 at `b3420e4`. - Created `feat/p01-foundation` from the merged `main`. - Added persistent SQLite startup initialization with WAL, busy timeout, foreign-key enforcement, and transactional migrations. - Added schema v2 with canonical non-sensitive `connection_profiles` metadata. - Added fresh-database, v1-to-v2, future-version, idempotent reopen, five-Profile, CRUD, and persistent-reopen coverage. - Added bounded Tauri Profile list/create/update/delete commands. - Kept UUID and timestamp creation in Rust. - Rejected credential-bearing URLs, URL query/fragment data, implicit HTTP, invalid certificate fingerprints, malformed IDs, unknown fields, and Token/password/API Key fields. - Preserved credential references and runtime-managed fields outside the editable P01 input. - Added strict Zod Schemas for bootstrap and ConnectionProfile IPC payloads. - Added a basic React Profile management UI for non-sensitive metadata only. - Added explicit deletion confirmation and browser-safe Tauri IPC fallback. - Added a redacting tracing writer that sanitizes structured fields and rendered message content. - Retained tray, close-to-tray, explicit quit, and single-instance behavior. - Re-exported protocol Schemas without drift. - Re-ran a real Tauri development startup and reached the Windows executable. - Rebuilt the Windows release executable and NSIS installer. - Recorded the Profile boundary in PD-0008 and ADR-0004. - Verified Forgejo PR #2 was merged at `885abd1553ed8f1428de7118a6f4b59f7e22a45c`. - Fast-forwarded local `main` to the same remote merge commit without rewriting history. - Created `feat/p02-dual-connections` from the updated `main`. - Re-read `AGENTS.md`, the Forgejo workflow, architecture design, and implementation task documents in full for P02. - Kept the approved HTTP Forgejo URL repository-local and prevented the machine-wide HTTP-to-SSH rewrite from changing this repository's transport. ## In progress - P02 first increment: SQLite schema v3 and bounded companion/operations slot assignment. - Protocol/security review for credential lifecycle, real Gateway authentication, authoritative server identity, and certificate-change freeze behavior. ## Remaining - Implement and verify the P02 slot persistence and UI increment. - Implement auto-connect validation, operations switching protection, and duplicate server-instance warnings. - Implement the formal Rust-owned credential lifecycle without returning secret values to React. - Implement two independent configured REST/SSE runtimes only against a reviewed contract; continue using the dual Mock Gateway for deterministic tests. - Run Forgejo CI when a compatible runner is available. - Execute a real UNC transaction only after an authorized disposable fixture is supplied. - Add the combined end-to-end test that keeps configured streams active while the real Tauri window is hidden to tray. ## Blockers - Configured Forgejo SSH `localhost:18086` refuses connections. - LAN SSH `192.168.31.210:18086` responds but rejects the available public key. - Approved HTTP Git push remains operational and is not blocked. - Forgejo runner labels/jobs could not be verified; the jobs API endpoint returned 404. - Real AstrBot Gateway endpoints, authentication semantics, token refresh behavior, and server identity guarantees remain unavailable for compatibility verification. - Certificate fingerprint extraction/pinning behavior must be designed without disabling TLS validation. - These protocol items do not block the local P02 slot-persistence increment. ## Test status - `npm run check:frontend`: passed; Prettier, ESLint, TypeScript, 3 Vitest tests, and Vite production build. - `npm run test:e2e`: passed; 1 Chromium smoke test. - Rust fmt/check/Clippy with warnings denied: passed. - `cargo test --workspace`: passed; 50 normal tests, 2 explicit manual tests ignored. - Profile persistence: passed; five Profile CRUD, close/reopen persistence, and v1-to-v2 migration preserve existing messages. - Secret boundary: passed; unknown Token, password, and API Key input fields are rejected. - Protocol Schema export: passed; no generated drift. - Tauri development startup: passed; executable launched, then was deliberately terminated after verification. - Tauri Windows release executable: passed. - NSIS installer: passed; `0.1.0-alpha.1`, 3,827,899 bytes. - NSIS SHA-256: `90EB68CDB5EAEDEA675050DA0F30DDAB5E8A0345FF176690A31FA5F66C818740`. - Forgejo CI and a real UNC transaction were not executed and are not claimed successful. ## Current branch `feat/p02-dual-connections` ## Recent commits - `885abd1 Merge pull request 'feat(p01): add secure profile foundation and management UI' (#2) from feat/p01-foundation into main` - `b3420e4 Merge pull request 'feat(p00): bootstrap Tauri desktop and validate high-risk spikes' (#1)` - `ed74342 feat(foundation): add persistent bootstrap safeguards` - `6a1eeab docs(p01): record foundation progress and profile boundary` - `02fd25a feat(profile): add secure profile persistence and IPC` - `907a8a3 feat(profile-ui): add basic profile management` - `5672585 chore(version): set P01 alpha version` - `2154c3b docs(p01): resolve profile boundary and record verification` ## Next step Complete the persistent companion/operations slot increment, run the relevant frontend and Rust checks, commit it as a focused Conventional Commit, and push `feat/p02-dual-connections` normally.