Repository navigation
feat(workspace): add confirmed cloud data reset - #11
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
@codex review |
|
Codex Review: Didn't find any major issues. 🎉 Reviewed commit: ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
|
@codex security review |
🛡️ Codex Security ReviewSecurity review completed. No security issues were found in this pull request. Reviewed commit: Only the user who started this review can view the report in Codex. ℹ️ About Codex security reviews in GitHubThis is an experimental Codex feature. Security reviews are triggered when:
Once complete, Codex will leave suggestions, or a comment if no findings are found. |
Problem and resulting behavior
Settings could reset only the current device, leaving no supported way to start again with empty cloud business data. Add Reset cloud data with a fresh scope preview and typed
RESETconfirmation. Successful reset keeps the original Gist, token, and connection.The coordinator clears all five business collections and removes provably published outputs in one verified Gist PATCH. It retains immutable migration backup, external files, tombstones, and recovery journals. A reset revision boundary blocks old queues, delayed actions, batch imports, and compatibility reconcile from replaying pre-reset data. The public Server API contract stays unchanged.
The accepted specification and bilingual user/operations guides are included. Reset does not erase GitHub history or replace repair for invalid cloud documents.
Task and verification evidence
/root/Clouds/SubMan-cloud-reset/feat/cloud-reset.243db4cc4272e7e4772355fcc7f8e06a84976259.b3b4bb218056c0ddad3a0fd445d2e70b7544d487.bun test: 758 passed across 74 files.bun run docs:check,bun run check(including generated Worker types),bun run lint: passed.bun run test:sing-box: 15 generated outbounds validated with pinned sing-box 1.14.0.bun run deploy:check: build and deployment dry-run passed.git diff --check: passed.b3b4bb218056c0ddad3a0fd445d2e70b7544d487./tmp/subman-cloud-reset-desktop.pngand/tmp/subman-cloud-reset-mobile.png; not uploaded publicly.Review gate (update before merge)
Review evidence:
b3b4bb218056c0ddad3a0fd445d2e70b7544d487.chatgpt-codex-connector[bot].Merge and completion (update after authorized merge)
b3b4bb218056c0ddad3a0fd445d2e70b7544d487.7742e2c723a4d5bdd64ce1899ce0362e683420d7.origin/main;git range-diffreports the original/rebased commit as equal, both stable patch IDs areeee0a2f1fb8ff9758b089d697131ce838b0d943e, and the complete task and merge trees are identical. No integration content changes required repeat runtime validation.mainfast-forwarded to7742e2c723a4d5bdd64ce1899ce0362e683420d7, matchingorigin/main.fix/gists-readonlyworktree and branch were preserved./tmp/subman-cloud-reset-delivery.7742e2c723a4d5bdd64ce1899ce0362e683420d7. No manual production deployment was requested or run.