livetribe / yama / 30243675729

68%

master: 100%

Build Type

push

github

Committed by maguro

Commit Message

Separate level occupancy from lifecycle capability

The docs claimed only lifecycle-capable components take part in
lifecycle execution. A value whose provider returns a Wire cleanup
occupies a level too, carrying no capability of its own — the runtime
has always worked this way and the prose never said so. Four kinds of
provider output are now named: dependency-only, with or without a
cleanup, and lifecycle-capable, with or without one. Only the first
occupies no level.

The runtime drew no such distinction either: every cleanup was paired
with its component, so a value implementing nothing got a decorator
wrapped around an empty one. The generator settles capability
statically, so the form is chosen at build time instead — WithCleanup
when the value has no capability of its own, WithCleanableComponent
when it has both. The pinned exemplar now emits both.

That also makes a correctness property structural. A paired cleanup
runs ahead of a failed component's gated teardown only by call order;
a standalone cleanup has no gate to sit outside of.

Two documentation corrections ride along. Startup, quiesce, and
shutdown were described as three computed level structures; the runtime
takes one list and walks it forward then back. And cleanupAdapter,
referenced across four documents, was never an identifier in the tree.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

Coverage Stats

21 of 25 new or added lines in 3 files covered. (84.0%)

8 existing lines in 2 files now uncovered.

959 of 1475 relevant lines covered (65.02%)

37.13 hits per line