Hare/yoi
1
1
Fork 0
Code Actions Packages Releases Activity

docs: record discovery and Runtime metadata boundary verification

Browse Source
This commit is contained in:
Hare
2026-10-12 10:31:48 +09:00
parent dbcea6c34b
commit b63bdb4402
2 changed files with 65 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/development/backend-db-execution.md
+9
View File
@@ -112,6 +112,15 @@ whole transaction helpers. Additional assignment diagnostics, answer mutations,
and Ticket queries use the same owned caller boundary; do not add a second ledger
or reconstruct processing evidence from Worker liveness.
Worker discovery uses the same whole `workers_response` DB stage as Worker list
and resource detail: projection snapshot, Workdir registry/links, and authority
projection never acquire the shared connection on Tokio. Source-proof requirement
and pure query/cursor validation still precede admission; overload remains 503.
Runtime resource list/detail use a finite Host stage for synchronous Runtime
summary I/O, then await the independent DB binding read. Do not confuse a Runtime
summary callback with the pure stored Worker projection or run network waits on
the sole DB worker.
## Regression evidence
- `db_executor::tests`: real SQLite IMMEDIATE write contention while a current-thread