feat: generation-safe policy replacement and unsubscription #101
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "feat/policy-generation-lifecycle"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Policy registry lifecycle primitive
register returns generation-bound unsubscribe; optional remove; trusted same-ID replace preserves position/atomic required identity. Snapshot ordered handlers per invocation so suspended chains don't mix generations. Invalid replacement retains existing hooks; stale cleanup cannot remove replacement. Required identities cannot unsubscribe/remove, teardown clear preserves missing-required behavior.
6focused/full559tests/typecheck/build/diffcheckPASS. Deferred in-flight test reproduces old map-iterator mixing and proves old chain/new next invocation. Required failure/replacement tests. Docs explicitly no whole-turn snapshot/resource disposal/admin module reload/persistent overlay; these remain next integration slice. Plugin registration startup-only; no silent baseline gate deletion. Author inspected, no extra independent review/reset. Original drafts preserved, standing delivery mandate. Merge not rollout.