Enforce atomic Effect-family versions and reconcile runtime documentation

[ian-pascoe]

What to build

Keep core Effect and its Bun and SQLite adapters on one exact release, and make the architecture document accurately distinguish the Effect behavior implemented today from target behavior planned for later releases.

Acceptance criteria

• Every directly declared Effect runtime package uses the same exact version without a range.
• The lockfile resolves one matching Effect runtime family.
• An automated verification check fails if the declared runtime versions diverge or use ranges.
• Architecture documentation names the current release and no longer claims unimplemented structured logging or metrics are active.
• Future Effect upgrades have one documented atomic verification path.
• The full verification command passes.

Blocked by

None (can start immediately).