docs: make multi-worker consistency semantics executable

[dgenio]

Closes #226.

What changed

• Adds docs/deployment-consistency.md with an explicit component-by-component consistency matrix for multi-worker deployments.
• Adds tests/test_multi_worker_consistency.py so the load-bearing claims are executable documentation rather than prose that can silently drift.

The tests pin four current facts:

1. a signed token issued in worker A verifies in worker B when both share the signing secret;
2. default in-memory revocation in A does not propagate to B;
3. rate-limit windows are independent between workers;
4. default handles are process-local and cannot be expanded/fetched from another worker.

Why

The mixed stateless/stateful model is non-obvious: sharing WEAVER_KERNEL_SECRET shares token verification ability, not revocation/limit/handle state. This is a security and operations boundary that adopters need to know before horizontal scaling.

Architecture decision

This PR deliberately does not build a sidecar or shared-state control plane. It documents the evidence first and states that #227 should earn its complexity from real adopter consistency requirements. A small shared-store protocol may be sufficient for some guarantees.

Validation

The new test file uses existing component APIs and should run in the normal CI matrix. No runtime behavior is changed.

[Copilot]

Pull request overview

Warning

Copilot couldn't run its full agentic review because it didn't start before the timeout. Make sure your repository has a runner available, or add a copilot-code-review.yml file specifying one with the runs-on attribute. See the docs for more details.

Makes the multi-worker consistency semantics explicit and verifiable by turning key deployment claims into executable tests and documenting a component-by-component consistency matrix.

Changes:

• Added a new pytest module that asserts cross-worker behavior for token verification, revocation, rate limits, and handles.
• Added a deployment consistency document that summarizes default state locality and links to the tests as evidence.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 6 comments.

File	Description
tests/test_multi_worker_consistency.py	Adds tests intended to “pin” multi-worker consistency semantics across key components.
docs/deployment-consistency.md	Documents default consistency/state-sharing expectations and points to the new tests as executable evidence.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.