weichenandCursor 24bbb7b777 Keep a newly seeded model key ahead of a stale secret ...

Why: The active secret_keys row overrides settings plaintext, so a replaced chat key kept returning 401. Migration also mutated the settings map in place, so clearing a matching plaintext never reached the database.
Evidence: go test ./internal/settings/ ./internal/runtime/ -count=1 (SELF, worktree).
Impact: System settings writes adopt a changed secret; conflicting plaintext is kept and logged; 401 errors name the key layer and an 8-hex fingerprint.
Refs: fix/model-key-secret-overlay
Co-authored-by: Cursor <cursoragent@cursor.com>

2026-10-15 10:33:14 +00:00

..

project_metadata_test.go

Admit private member uploads and preserve masked metadata edits

2026-10-13 10:23:37 +00:00

project_metadata.go

Admit private member uploads and preserve masked metadata edits

2026-10-13 10:23:37 +00:00

secrets_test.go

Keep a newly seeded model key ahead of a stale secret

2026-10-15 10:33:14 +00:00

secrets.go

Keep a newly seeded model key ahead of a stale secret

2026-10-15 10:33:14 +00:00

settings_account_write_test.go

Fence U3 account writes and stabilize directory cursors

2026-10-14 07:33:54 +00:00

settings_test.go

Enforce system-managed settings scope with admin system settings API

2026-10-13 04:05:15 +00:00

settings.go

Keep a newly seeded model key ahead of a stale secret

2026-10-15 10:33:14 +00:00