4.5 KiB
4.5 KiB
Development Progress
Current phase
P01 foundation is complete and published on feat/p01-foundation. The option A boundary is resolved: basic non-sensitive Profile metadata CRUD belongs to P01, while slots and runtime connection behavior remain in P02.
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-foundationfrom the mergedmain. - Added persistent SQLite startup initialization with WAL, busy timeout, foreign-key enforcement, and transactional migrations.
- Added schema v2 with canonical non-sensitive
connection_profilesmetadata. - 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.
In progress
- No code implementation is in progress; the branch is awaiting Forgejo PR review.
Remaining
- Create and review the P01 Forgejo PR; do not automatically merge
main. - 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:18086refuses connections. - LAN SSH
192.168.31.210:18086responds 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.
- No blocker remains for the selected P01 scope.
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/p01-foundation
Recent commits
b3420e4 Merge pull request 'feat(p00): bootstrap Tauri desktop and validate high-risk spikes' (#1)ed74342 feat(foundation): add persistent bootstrap safeguards6a1eeab docs(p01): record foundation progress and profile boundary02fd25a feat(profile): add secure profile persistence and IPC907a8a3 feat(profile-ui): add basic profile management5672585 chore(version): set P01 alpha version2154c3b docs(p01): resolve profile boundary and record verification
Next step
Open feat/p01-foundation → main as a Forgejo PR, review the recorded local verification, and run CI only when a compatible runner is available.