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

fix: clean remaining worker rename references

Browse Source
This commit is contained in:
Hare
2026-06-26 00:43:16 +09:00
parent ebf50baa94
commit 94c7aa793a
5 changed files with 17 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files
crates/pod-registry/README.md
+6 -6
View File
@@ -2,29 +2,29 @@
## Role
`pod-registry` tracks live Pod process ownership and delegated scope locks at runtime.
`pod-registry` is the legacy-named crate that tracks live Worker process ownership and delegated scope locks at runtime.
## Boundaries
Owns:
- machine-local live Pod registration
- collision detection for running Pod names
- machine-local live Worker registration
- collision detection for running Worker names
- delegated scope lock bookkeeping
- registry cleanup hooks for stopped or unreachable children
Does not own:
- durable Pod metadata (`pod-store`)
- durable Worker metadata (`pod-store`)
- replayable session logs (`session-store`)
- socket protocol definitions (`protocol`)
- project work item state
## Design notes
The registry is a runtime coordination mechanism. It can help decide whether a Pod is live or colliding, but durable visibility/restoration should be backed by Pod metadata when possible.
The registry is a runtime coordination mechanism. It can help decide whether a Worker is live or colliding, but durable visibility/restoration should be backed by Worker metadata when possible.
## See also
- [`../../docs/design/pod-session-state.md`](../../docs/design/pod-session-state.md)
- [`../../docs/design/worker-session-state.md`](../../docs/design/worker-session-state.md)
- [`../../docs/design/tool-permissions-scope.md`](../../docs/design/tool-permissions-scope.md)