Skip to content

feat(workspace): add confirmed cloud data reset - #11

Merged
KnowSky404 merged 1 commit into
mainfrom
feat/cloud-reset
Nov 1, 2026
Merged

KnowSky404 merged 1 commit into
mainfrom
feat/cloud-reset

Conversation

@KnowSky404

@KnowSky404 KnowSky404 commented Nov 1, 2026 •

Copy link
Copy Markdown
Owner

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 RESET confirmation. 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

  • Worktree / branch: /root/Clouds/SubMan-cloud-reset / feat/cloud-reset.
  • Base SHA: 243db4cc4272e7e4772355fcc7f8e06a84976259.
  • Tested head SHA: b3b4bb218056c0ddad3a0fd445d2e70b7544d487.
  • Bun 1.3.14 local validation:
    • bun test: 758 passed across 74 files.
    • bun run docs:check, bun run check (including generated Worker types), bun run lint: passed.
    • Build plus Cloudflare Vitest integration: 10 passed, including RPC/SQLite idempotency recovery and stale-preview HTTP rejection.
    • bun run test:sing-box: 15 generated outbounds validated with pinned sing-box 1.14.0.
    • All 81 Playwright cases passed in isolated groups (41 + 20 + 20); the seven cloud-reset cases passed again after final layout adjustments.
    • bun run deploy:check: build and deployment dry-run passed.
    • git diff --check: passed.
  • CI results for this head: verify passed, completed 2026-11-01T09:17:36Z on b3b4bb218056c0ddad3a0fd445d2e70b7544d487.
  • UI evidence: Playwright desktop 1280 x 720 and Chinese mobile 390 x 844; page identity, initial warning visibility, console health, cancellation, typed confirmation, delayed cloud acknowledgement, retry/conflict persistence, and retained credentials verified. Local screenshots are retained at /tmp/subman-cloud-reset-desktop.png and /tmp/subman-cloud-reset-mobile.png; not uploaded publicly.
  • Limitations: GitHub used fixtures/mocks; no real Gist was accessed or changed. No production deployment or live GitHub acceptance is claimed.
  • Independent local review findings were reproduced and resolved with regression tests. This does not substitute for current-head Codex bot review.

Review gate (update before merge)

  • Codex Code Review completed for the current head; author and SHA verified.
  • Security Review and other required reviews completed when enabled; actual repository configuration checked.
  • Review SHA, completion times, and evidence links recorded below.
  • Valid blocking findings resolved; false positives explained with evidence.
  • Required CI checks passed for the current head; new commits reviewed again.

Review evidence:

  • Head: b3b4bb218056c0ddad3a0fd445d2e70b7544d487.
  • Actual review author: chatgpt-codex-connector[bot].
  • Code Review: completed 2026-11-01T09:17:22.144724Z with no major issues; receipt, per-review summary and SHA. No inline findings or unresolved threads.
  • Security Review: completed 2026-11-01T09:21:21.700589Z with no security issues; explicit receipt, per-review summary and SHA. Enabled for this PR; the summary records mergeGateEnabled=false and a P0 threshold, while the project-required completion gate was still enforced.
  • Actual repository queries return no repository rulesets, no effective main-branch rules, and no classic branch protection. Rebase merging is enabled; no other configured review/check gates were found. The project-mandated review and CI gates still apply.

Merge and completion (update after authorized merge)

  • Authorization: user requested PR submission and merge.
  • Strategy: rebase merge pinned to the verified current head, without an administrative bypass.
  • PR: feat(workspace): add confirmed cloud data reset #11; MERGED at 2026-11-01T09:22:42Z.
  • Reviewed original head: b3b4bb218056c0ddad3a0fd445d2e70b7544d487.
  • Rebase merge SHA: 7742e2c723a4d5bdd64ce1899ce0362e683420d7.
  • Main integration: merge SHA is in origin/main; git range-diff reports the original/rebased commit as equal, both stable patch IDs are eee0a2f1fb8ff9758b089d697131ce838b0d943e, and the complete task and merge trees are identical. No integration content changes required repeat runtime validation.
  • Original checkout: clean main fast-forwarded to 7742e2c723a4d5bdd64ce1899ce0362e683420d7, matching origin/main.
  • Cleanup: task worktree and local branch removed; remote branch deleted with a lease pinned to the reviewed original head. Remote absence verified. The unrelated fix/gists-readonly worktree and branch were preserved.
  • Validation evidence and screenshots retained outside the removed worktree at /tmp/subman-cloud-reset-delivery.
  • Repository-triggered post-merge main CI: https://github.com/KnowSky404/SubMan/actions/runs/41292882598 passed on 7742e2c723a4d5bdd64ce1899ce0362e683420d7. No manual production deployment was requested or run.

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Nov 1, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-11-01T09:17:22.144724Z b3b4bb2 Manual request
🔒 Security Review ✅ Completed 2026-11-01T09:21:21.700589Z b3b4bb2 Manual request
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@KnowSky404

Copy link
Copy Markdown
Owner Author

@codex review

@chatgpt-codex-connector

Copy link
Copy Markdown

Codex Review: Didn't find any major issues. 🎉

Reviewed commit: b3b4bb2180

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

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".

@KnowSky404

Copy link
Copy Markdown
Owner Author

@codex security review

@chatgpt-codex-connector

Copy link
Copy Markdown

🛡️ Codex Security Review

Security review completed. No security issues were found in this pull request.

Reviewed commit: b3b4bb2180

View security finding report

Only the user who started this review can view the report in Codex.

ℹ️ About Codex security reviews in GitHub

This is an experimental Codex feature. Security reviews are triggered when:

  • You comment "@codex security review"
  • A regular code review gets triggered (for example, "@codex review" or when a PR is opened), and you’re opted in so security review runs alongside code review

Once complete, Codex will leave suggestions, or a comment if no findings are found.

@KnowSky404
KnowSky404 merged commit 7742e2c into main Nov 1, 2026
1 check passed
@KnowSky404
KnowSky404 deleted the feat/cloud-reset branch November 1, 2026 09:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant