chore: bump effect-operator-kit to the peer-dependency release

[solomonneas]

Bumps @lidless-labs/effect-operator-kit from 1f793ac to be71030 (v0.2.0).

The kit now declares effect as a peerDependency instead of a regular dependency. That is the correct packaging for a library: it lets the consumer own the single effect version and removes the latent dual-runtime risk of two effect copies resolving in the same process.

This repo imports effect directly in source but did not declare it (it was resolving transitively through the kit's old regular dependency). Now that the kit makes effect a required peer, this PR adds effect (^3.21.4) as a direct dependency to satisfy the peer and drop the phantom-dependency reliance. Matches the reference impl (jellyfin-mcp, already on be71030 with effect declared directly).

Verified with Brigade:

• npm test -> exit 0
• npm run typecheck -> exit 0

[solomonneas]

Exact-head merge evidence for 05bcb30f211398c65d8ea6047ffc7fd8192a4c78:

• Independent exact-head review: APPROVE, no blocking findings
• Brigade receipt: 20260717-023053-work-verify-e354c6
• Receipt digest: 583b4511ff6f4904e7b52462d7eaf5e5e6076c6a937b50ebc859a7d41c3607dd
• Local gate: 237 tests passed, typecheck passed, build passed
• CI: Node 20 and Node 22 CI passed
• Introduced-content guard passed with the GitHub SSH transport literal narrowly allowed