diff --git a/CHANGELOG.md b/CHANGELOG.md index f7b1308..c41668a 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -22,9 +22,15 @@ The format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/), and - Strict Zod validation for the Rust bootstrap IPC payload, including the active database schema version. - Redacting tracing output writer with structured-field, bearer-token, URL-credential, private-key, and known-secret coverage. - P01 migration, logging, IPC validation, real Tauri startup, and production-build verification. +- SQLite schema v2 for persistent non-sensitive ConnectionProfile metadata. +- Bounded Rust-owned Profile list/create/update/delete IPC with generated UUIDs and timestamps. +- Strict frontend ConnectionProfile Schemas and a basic Profile management UI. +- Migration, five-Profile CRUD, persistent reopen, secret-field rejection, and browser fallback tests. ### Security - Kept credentials and native capabilities in Rust; the React capability set remains `core:default` only. - Added secret redaction and repository scans; no arbitrary PowerShell, CMD, shell, input-injection, registry-write, or unrestricted filesystem API is exposed. - Kept real UNC writes, signing keys, updater keys, and release secrets outside P00. +- Rejected Token, password, API Key, URL credential, query-string credential, and unknown fields at the Profile IPC boundary. +- Required explicit approval for insecure HTTP and kept slots, connections, and credential enrollment outside P01. diff --git a/docs/decisions/ADR-0004-profile-lifecycle-and-secret-boundary.md b/docs/decisions/ADR-0004-profile-lifecycle-and-secret-boundary.md new file mode 100644 index 0000000..de5863b --- /dev/null +++ b/docs/decisions/ADR-0004-profile-lifecycle-and-secret-boundary.md @@ -0,0 +1,64 @@ +# ADR-0004: Profile lifecycle and secret boundary + +- Status: accepted +- Date: 2026-07-18 +- Decision owner: project owner + +## Background + +The architecture document assigns Profile CRUD to stage 1, while the implementation task document groups ConnectionProfile CRUD with the stage 2 dual-connection slots. The conflict affects the SQLite schema, Tauri IPC surface, frontend state, and stage acceptance boundary. + +The project owner selected option A from PD-0008: + +- P01 owns basic ConnectionProfile metadata CRUD. +- P02 owns active slot assignment and all runtime connection behavior. + +## Options considered + +### Option A: basic metadata CRUD in P01 + +Create, list, update, and delete non-sensitive Profile metadata in P01. Keep companion/operations slot assignment, active connections, auto-connect validation, switching protection, and duplicate server-instance detection in P02. + +### Option B: defer all Profile CRUD to P02 + +Keep P01 limited to application bootstrap, persistent SQLite, logging, tray, single-instance, and tests. + +## Decision + +Use option A. + +P01 persists the canonical non-sensitive ConnectionProfile fields and exposes bounded Tauri commands for: + +- listing Profiles; +- creating a Profile; +- updating user-editable metadata; +- deleting a Profile. + +The P01 IPC input does not accept Token, password, API Key, Cookie, Authorization header, NAS credential, or arbitrary extra fields. Rust creates Profile IDs and timestamps. React may receive only non-sensitive metadata and an opaque credential reference. + +The following remain explicitly out of P01: + +- credential value enrollment or retrieval; +- companion/operations slot assignment; +- connection activation and cancellation; +- auto-connect behavior; +- switching protection; +- server_instance_id conflict detection; +- REST/SSE runtime state. + +## Reasons + +- AGENTS.md gives the architecture document higher priority. +- A saved Profile is a durable application-foundation concept and can be implemented without activating a connection. +- Separating metadata from runtime connection state preserves the Rust-owned security boundary. +- The narrow IPC input makes accidental secret transfer to React or SQLite rejectable at deserialization time. + +## Trade-offs + +- P01 can select an authentication type but cannot enroll the corresponding credential value. +- The UI is intentionally a foundation form, not a full connection settings experience. +- Credential deletion and transactional cleanup must be added with the formal credential lifecycle before credential references can be created by production flows. + +## Follow-up + +P02 must consume this metadata model without widening the P01 commands to accept secret values. It must add slots, connection state, auto-connect rules, profile-switch guards, duplicate server-instance warnings, and credential lifecycle integration as separate reviewed increments. diff --git a/docs/decisions/pending-decisions.md b/docs/decisions/pending-decisions.md index dc60a73..4fc3fac 100644 --- a/docs/decisions/pending-decisions.md +++ b/docs/decisions/pending-decisions.md @@ -53,12 +53,11 @@ ## PD-0008: Profile CRUD stage ownership -- Status: unresolved; blocks Profile CRUD implementation only +- Status: resolved; option A selected by the project owner on 2026-07-18 - Conflict: `docs/01_Architecture_Design.md` lists Profile CRUD in stage 1, while `docs/02_Codex_Implementation_Tasks.md` lists ConnectionProfile CRUD in Batch 2. -- Impact: resolving this changes the database schema, Tauri IPC surface, frontend state model, and the acceptance boundary between `feat/p01-foundation` and `feat/p02-dual-connections`. -- Safe current action: complete only the unambiguous P01 foundation work��persistent migrations, validated bootstrap IPC, redacted logging, tray, single-instance, exit flow, and tests. -- Paused work: profile tables, Profile CRUD commands, profile forms, and profile-to-slot assignment. -- Required decision: - - Option A: architecture document wins; implement basic Profile CRUD in P01 and leave slot assignment/connection behavior for P02. - - Option B: implementation task batching wins; keep all ConnectionProfile CRUD in P02. -- Recommendation: Option A is the literal higher-priority document, but the implementation remains paused because AGENTS.md requires explicit reporting for conflicts affecting database structure or public interfaces. +- Decision: implement basic non-sensitive Profile metadata CRUD in P01. +- P01 scope: Profile list, create, update, and delete; SQLite schema v2; bounded Tauri IPC; strict frontend Schema; basic management UI. +- P02 scope: companion/operations slot assignment, active connection state, auto-connect validation, switching protection, and `server_instance_id` conflict detection. +- Secret boundary: P01 commands accept no Token, password, API Key, Cookie, Authorization header, or NAS credential fields. SQLite stores only non-sensitive metadata and future opaque credential references. +- Rationale: AGENTS.md gives the architecture document higher priority, and the selected split keeps runtime connection behavior out of P01. +- ADR: `ADR-0004-profile-lifecycle-and-secret-boundary.md`. diff --git a/docs/implementation-plan.md b/docs/implementation-plan.md index 1ee495c..c236918 100644 --- a/docs/implementation-plan.md +++ b/docs/implementation-plan.md @@ -41,7 +41,7 @@ Establish a reproducible Tauri 2 + React + TypeScript + Rust baseline and comple ### Objective -Turn the P00 Spike skeleton into a durable application foundation without pulling Batch 2 connection-profile behavior forward across an unresolved document boundary. +Turn the P00 Spike skeleton into a durable application foundation. Under the project owner's option A decision, P01 includes basic non-sensitive Profile metadata CRUD while P02 retains all slot and runtime connection behavior. ### Ordered work @@ -49,11 +49,26 @@ Turn the P00 Spike skeleton into a durable application foundation without pullin 2. Apply versioned, transactional, idempotent migrations and refuse unknown future schema versions. 3. Validate Rust-to-TypeScript bootstrap payloads at runtime. 4. Ensure tracing output passes through the shared redaction rules before it reaches a writer. -5. Re-verify tray, single-instance, explicit exit, frontend, Rust, E2E, development startup, and production build behavior. -6. Record the Profile CRUD stage conflict before changing its schema or IPC. +5. Add SQLite schema v2 for canonical non-sensitive ConnectionProfile metadata. +6. Add bounded Tauri list/create/update/delete commands that generate IDs and timestamps in Rust. +7. Reject secret values, URL credentials, query-string credentials, unknown IPC fields, and implicit insecure HTTP. +8. Add strict frontend Profile Schemas and a basic management UI without Token/password/API Key inputs. +9. Test five saved Profiles, CRUD, persistent reopen, v1-to-v2 migration, future-version rejection, and browser fallback. +10. Re-verify tray, single-instance, explicit exit, frontend, Rust, E2E, development startup, Schema export, and production build behavior. +11. Record the decision in PD-0008 and ADR-0004, then commit and push the verified branch normally. -### Paused boundary +### P01 boundary -- `docs/01_Architecture_Design.md` places Profile CRUD in stage 1. -- `docs/02_Codex_Implementation_Tasks.md` places ConnectionProfile CRUD in Batch 2. -- Because this changes database structure and public IPC, Profile CRUD remains paused under PD-0008 until the stage boundary is explicitly resolved. +- Included: durable application database, schema migration, redacted logging, validated bootstrap IPC, basic Profile metadata CRUD, basic Profile management UI, tray, single-instance, and build/test foundations. +- Excluded: slot assignment, active REST/SSE connections, auto-connect behavior, Profile switching protection, duplicate `server_instance_id` handling, and formal credential enrollment. + +### Verification status + +- Frontend formatting, ESLint, TypeScript, 3 Vitest tests, and Vite production build passed. +- Playwright Chromium passed 1/1. +- Rust fmt, Clippy with warnings denied, tests, and check passed. +- Rust test suite passed 50 normal tests; 2 explicit manual tests remained ignored. +- Protocol Schema export completed without drift. +- Real Tauri development startup reached the Windows executable and was then deliberately terminated. +- Windows release and NSIS bundling passed. +- Forgejo CI remains unverified because a compatible runner/jobs endpoint is unavailable. diff --git a/docs/progress.md b/docs/progress.md index ac108f7..9276fcc 100644 --- a/docs/progress.md +++ b/docs/progress.md @@ -2,43 +2,42 @@ ## Current phase -P01 foundation is active on `feat/p01-foundation`; unambiguous foundation work is implemented, while Profile CRUD is paused on a documented stage-boundary conflict. +P01 foundation is active 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` and all authoritative architecture, implementation, and Forgejo workflow documents. +- 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 a local Git repository on `main`. -- Configured `origin` as `ssh://git@localhost:18086/YokiiroBW/AstrBot-Desktop.git`. -- Verified through authenticated Forgejo API and HTTP Git that the remote repository existed, was empty, used `main`, and granted push permission before the baseline push. -- Reauthenticated through Git Credential Manager and non-forced pushed the `main` baseline to Forgejo at `0d12b94`. -- Created and switched to `feat/p00-bootstrap` from the pushed `main` baseline. -- Built the Tauri 2 + React + TypeScript + Rust skeleton with tray, single-instance, CSP, and minimal `core:default` capability. -- Implemented independent companion/operations REST and SSE clients and passed the corrected 30-minute soak. -- Implemented and tested Windows Credential Manager, UI Automation, selected-window capture, Event Log, process, port, foreground-window, authorized log-tail, configuration parsing, and redaction Spikes. -- Implemented and tested composite-key SQLite isolation and recoverable local file transactions with source preservation. -- Added provisional protocol types, ten JSON Schemas, TypeScript exports, drift checks, and two loopback-only Mock Gateway instances. -- Added frontend, Playwright, Rust, integration, Windows-provider, soak, and Forgejo CI entry points. -- Built the Windows release executable and SHA-256-recorded NSIS installer. -- Added dependency, Spike, progress, changelog, and pending-decision records. -- Verified Forgejo PR #1 merged into `main` as `b3420e4`. -- Fast-forwarded local `main` and created `feat/p01-foundation` from the merged baseline. -- Added persistent SQLite startup initialization with WAL, busy timeout, transactional `user_version` migration, idempotent reopen, and future-version rejection. -- Added strict Zod validation for the Rust bootstrap IPC payload and exposed the active database schema version. -- Added a redacting tracing writer that sanitizes structured fields and rendered message content before output. -- Verified a real Tauri development start created the application database in the Windows app-data directory. -- Built the P01 Windows release executable and NSIS installer. -- Committed the implementation, test, and CI increments with Conventional Commit subjects. +- 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. ## In progress -- Recording the Profile CRUD stage conflict and preparing the verified P01 foundation increment for remote review. +- Final documentation review, focused Conventional Commits, and normal Forgejo push. ## Remaining -- Resolve whether Profile CRUD belongs in P01 (architecture document) or P02/Batch 2 (implementation task document) before changing its database schema or public IPC. -- After resolution, complete the selected stage scope and open a PR without automatically merging `main`. -- Run the Forgejo workflow when a compatible runner is available. +- Commit the verified backend, frontend, test, and documentation increments. +- Push `feat/p01-foundation` normally to Forgejo. +- Generate the P01 Forgejo PR title and body; do not 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. @@ -46,22 +45,23 @@ P01 foundation is active on `feat/p01-foundation`; unambiguous foundation work i - Configured Forgejo SSH `localhost:18086` refuses connections. - LAN SSH `192.168.31.210:18086` responds but rejects the available public key. -- HTTP Git push is operational after Git Credential Manager reauthentication and is no longer a blocker. -- Profile CRUD stage ownership conflicts between the architecture and implementation task documents; implementation is paused because it affects database structure and public IPC. +- 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; 2 Vitest tests and production Vite build. -- `pnpm test:e2e`: passed; 1 Chromium smoke test. +- `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`: 44 passed, 2 explicit manual tests ignored. -- Controlled Windows UIA/PrintWindow smoke: 1 passed. -- Corrected dual-SSE soak: 1800.02 seconds, 1800 companion events, 1801 operations events, passed. -- Protocol Schema drift check: passed. -- P01 Tauri development startup and application-data SQLite creation: passed. -- P01 release executable and NSIS installer: passed after repairing the missing official `libsqlite3-sys` binding cache; installer SHA-256 `B8858CBE2F4673FAF40799C1243BCAB0748D194FA3AD67FBD33DDCF26CF27189`. -- pnpm 11.9.0 frozen lockfile-only validation: passed using a local temporary store to avoid the pnpm UNC project-registry limitation. +- `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 @@ -70,16 +70,10 @@ P01 foundation is active on `feat/p01-foundation`; unambiguous foundation work i ## Recent commits -- `5e6e8d5 docs(project): add architecture and implementation specifications` -- `0d12b94 chore(repo): initialize repository and ignore rules` -- `01607c6 feat(p00): add Tauri desktop spike foundation` -- `69b432b test(p00): add frontend browser rust and windows checks` -- `d4af979 ci(forgejo): add portable and windows quality workflows` -- `72a16cb docs(p00): record Forgejo branch publication` - `b3420e4 Merge pull request 'feat(p00): bootstrap Tauri desktop and validate high-risk spikes' (#1)` - `ed74342 feat(foundation): add persistent bootstrap safeguards` -- `353a439 docs(p00): record spike results and unresolved boundaries` +- `6a1eeab docs(p01): record foundation progress and profile boundary` ## Next step -Obtain an explicit decision for PD-0008 before implementing Profile CRUD. Continue other P01 work only if it does not change the disputed profile database or public IPC boundary. +Create focused commits for Profile persistence/IPC, Profile UI/tests, and P01 decision/report documentation. Re-run the proportional checks for each commit, push the branch normally, and prepare the Forgejo PR without merging `main`. diff --git a/docs/reports/p01-foundation-progress.md b/docs/reports/p01-foundation-progress.md index 3815029..c5968ab 100644 --- a/docs/reports/p01-foundation-progress.md +++ b/docs/reports/p01-foundation-progress.md @@ -4,58 +4,84 @@ Date: 2026-07-18 ## Status -P01 foundation work is partially complete on `feat/p01-foundation`. The unambiguous Batch 1 foundation items are implemented and verified. Profile CRUD is intentionally paused under PD-0008 because the architecture and implementation task documents assign it to different stages. +P01 implementation and local verification are complete on `feat/p01-foundation`. The branch still requires focused commits and a normal Forgejo push before the stage can be handed off for 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`. -- Fast-forwarded local `main` and created `feat/p01-foundation`. -- Added a persistent SQLite database under the Tauri application-data directory. -- Added WAL mode, a bounded busy timeout, foreign-key enforcement, and transactional `user_version` migration. -- Added idempotent reopen/persistence tests and rejection of databases newer than the supported schema. -- Added the database schema version to the bootstrap IPC response. -- Added strict frontend Zod validation for the IPC payload and a malformed-payload test. +- 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 the existing tray menu, close-to-tray, explicit quit, and single-instance focus behavior. +- 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; 2 Vitest tests | -| Playwright Chromium | Passed; 1 test | -| Rust fmt, Clippy with warnings denied, check | Passed | -| Rust tests | Passed; 44 normal tests, 2 explicit manual tests ignored | -| Persistent SQLite reopen and migration tests | Passed | -| Logging redaction writer test | Passed | -| Tauri development startup | Passed | -| Windows application-data SQLite creation | Passed; database created at startup | -| Tauri release executable | Passed | -| NSIS installer | Passed; 3,793,884 bytes | -| NSIS SHA-256 | `B8858CBE2F4673FAF40799C1243BCAB0748D194FA3AD67FBD33DDCF26CF27189` | +| 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` | + +## 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 first release attempts failed because the `libsqlite3-sys` release output directory did not contain `bindgen.rs`, although the crate build script had produced the SQLite static library. Cleaning only that package did not restore the file. - -The official pre-generated `bindgen_bundled_version.rs` from the installed `libsqlite3-sys 0.38.1` crate source was copied to the exact `OUT_DIR/bindgen.rs` location expected by the crate's own `build.rs`. Source and destination SHA-256 values matched: +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` -The production build and NSIS bundle then completed. This is recorded as an environment cache repair, not a repository or dependency change. +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. -## Paused boundary +## Deferred to P02 -Profile CRUD is not implemented in this increment. - -- Architecture stage 1 includes Profile CRUD. -- Implementation Batch 2 includes ConnectionProfile CRUD. -- The conflict affects database structure and public IPC. -- PD-0008 requires an explicit stage-boundary decision before work resumes. +- 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 -- P01 is not declared complete while PD-0008 is unresolved. - Forgejo CI has not run. -- No Profile CRUD, profile UI, or slot assignment was added. -- No real credential or destructive file operation was used. +- 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.