refactor: clarify resource control boundaries
This commit is contained in:
parent
eb0f69f287
commit
d443b82f1a
5 changed files with 275 additions and 64 deletions
|
|
@ -45,11 +45,11 @@ behavior.
|
|||
ownership and locking rules.
|
||||
- `[x]` Existing daemon startup and status tests pass unchanged.
|
||||
|
||||
- `[~]` Extract local control routing.
|
||||
- `[x]` Extract local control routing.
|
||||
Acceptance criteria:
|
||||
- `[x]` Local `ControlRequest` dispatch is a routing layer, not the home of
|
||||
every feature implementation.
|
||||
- `[ ]` Each command family has a small handler module or function group.
|
||||
- `[x]` Each command family has a small handler module or function group.
|
||||
- `[x]` Local-only behavior remains covered by existing integration tests.
|
||||
|
||||
- `[~]` Extract protected peer-control routing.
|
||||
|
|
@ -64,13 +64,13 @@ behavior.
|
|||
repeating peer-card boilerplate.
|
||||
- `[x]` Remote request tests still prove discovery alone grants no access.
|
||||
|
||||
- `[ ]` Extract resource module handlers.
|
||||
- `[x]` Extract resource module handlers.
|
||||
Acceptance criteria:
|
||||
- `[ ]` CAS/file-root, KV, DB, document, pubsub, pipe, SSH, and overlay
|
||||
- `[x]` CAS/file-root, KV, DB, document, pubsub, pipe, SSH, and overlay
|
||||
handlers are separated enough that each can be reviewed independently.
|
||||
- `[ ]` Each module documents its resource IDs, capabilities, and mutation
|
||||
- `[x]` Each module documents its resource IDs, capabilities, and mutation
|
||||
points.
|
||||
- `[ ]` No generic `geth-common` crate is introduced.
|
||||
- `[x]` No generic `geth-common` crate is introduced.
|
||||
|
||||
- `[x]` Extract live-sync engine.
|
||||
Acceptance criteria:
|
||||
|
|
|
|||
Loading…
Reference in a new issue