Skip to content

fix: register eligible legacy continuity routes - #333

Merged
Pigbibi merged 1 commit into
mainfrom
fix/legacy-continuity-console-sync
Aug 30, 2026
Merged

fix: register eligible legacy continuity routes#333
Pigbibi merged 1 commit into
mainfrom
fix/legacy-continuity-console-sync

Conversation

@Pigbibi

@Pigbibi Pigbibi commented Aug 30, 2026

Copy link
Copy Markdown
Contributor

Summary

  • retain the bounded legacy-continuity policy in the private console profile cache
  • let authenticated deployment reconciliation register a previously unknown legacy route only when the profile/platform policy, audited baseline, and preservation-only inputs all match
  • preserve plugin, option-overlay, and cash-only settings during account sync

Safety

  • this does not create a new live permission, change a runtime target, deploy a service, or submit an order
  • candidate strategies remain blocked by their normal P0-P6 gate
  • legacy registration is limited to private Worker KV and audit logged

Validation

  • rtk test node --experimental-default-type=module tests/strategy_switch_worker_validation.mjs
  • node --check --input-type=module < web/strategy-switch-console/worker.js
  • git diff --check
  • actionlint is covered by remote CI (not installed on the VPS)

Co-Authored-By: Codex <noreply@openai.com>
@Pigbibi
Pigbibi merged commit fb790de into main Aug 30, 2026
6 checks passed
@Pigbibi
Pigbibi deleted the fix/legacy-continuity-console-sync branch August 30, 2026 14:23
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