mirror of
https://github.com/LorenEteval/Furious.git
synced 2026-10-08 06:48:09 +03:00
32 lines
3.0 KiB
Markdown
32 lines
3.0 KiB
Markdown
# Repository guidance
|
|
|
|
Inherit the root and `Furious/AGENTS.md`. Consult the Interface and Models guides when changing their contracts.
|
|
This scope owns restoration, migration, ordering, and persistence; workflows and presentation remain outside it.
|
|
|
|
- Repositories restore, migrate, order, and persist profiles, subscriptions, routings, and TUN settings. They do not own
|
|
network workflows, controller state, test schedulers, or presentation.
|
|
- `Storage` owns one application-lifetime backend per collection and exposes live mutable collections for compatibility.
|
|
Do not add a second cache/snapshot authority. Prefer named repository mutations so validation and commit boundaries
|
|
can move behind the repository over time.
|
|
- Preserve stable profile/subscription IDs, subscription ownership/key, ordering, unknown fields, and legacy schemas.
|
|
Active row/index and display text are compatibility/presentation state, not identity.
|
|
- A restore failure remains observable. Automatic cleanup must not replace unreadable persisted bytes with an empty
|
|
fallback; only an explicit successful replacement may do so. Root decoding, individual-record hydration, and later
|
|
serialization are separate failure boundaries. Test malformed records inside a valid root as well as malformed
|
|
roots; the existing root fallback is not a guarantee that every record error is recoverable.
|
|
- Stage fallible decode/migration before live mutation. Subscription reconciliation currently belongs to
|
|
`Service/SubscriptionSync.py` and commits through the compatibility live collection: matched managed profiles
|
|
retain object/profile identity and local metadata, removed profiles become stale, and unrelated groups remain
|
|
intact. Do not add a second reconciliation algorithm here merely because persistence belongs to this scope.
|
|
- Distinguish a live-collection commit from serialization/flush and subsequent controller effects. The compatibility
|
|
collection can change before it is flushed; a successful in-memory synchronization is not proof of an atomic disk
|
|
transaction. Preserve explicit flush/cleanup behavior and report failures at the boundary that actually failed.
|
|
Batched UI commands may commit several live mutations; cancellation prevents later batches without restoring
|
|
already committed ones. Do not impose whole-command atomicity without changing callers and failure semantics.
|
|
- Moving a profile between subscription displays does not automatically make it remotely managed; preserve the explicit
|
|
distinction between local membership and synchronization ownership.
|
|
- Verify legacy/current/unknown-field round trips, malformed roots, restore-failure preservation, ordering/stable
|
|
identity, group isolation, reconciliation commit behavior, and persistence in temporary QSettings namespaces. Use
|
|
`tests/test_repository_contracts.py` and `tests/test_subscription_sync.py` to revalidate this scope. Reordering a
|
|
filtered view must preserve hidden slots and relocate activation by profile ID, not by its former row.
|