Files
LorenEteval_Furious/Furious/Repository/AGENTS.md
T
2026-08-20 19:35:06 +08:00

1.3 KiB

Repository guidance

  • Repositories are the only persistence authority for profiles, subscriptions, routing, and TUN settings. Keep Qt/UI/workflow concerns out of repository implementations.
  • Preserve stable IDs, ordering, unknown compatible fields, legacy migrations, and subscription ownership. Display names and row indexes are not identities.
  • Subscription synchronization may update only profiles explicitly managed by that subscription and identified by stable profile keys. Never delete user-created or another subscription's data.
  • Public collection access currently returns live mutable application-owned collections for compatibility. Document this honestly and avoid introducing a second cached copy; new mutations should flow through named repository operations when practical.
  • Load failures retain recoverable data where possible and log actionable context. Never silently replace malformed explicit configuration with unrelated defaults when doing so loses user intent.
  • Singleton repository caches are application-lifetime finite objects and must be reset/sandboxed in tests.

Verification

  • Test old/current schemas, unknown fields, ordering, stable identity, subscription isolation, malformed persisted data, round trips, and isolated temporary settings.