Tyrell Build 10 PowerGovernance typed logging candidate

Implemented a source-only, isolated shared-logging consumer lane for PowerGovernanceActor; it is ready for owner review but deliberately not integrated or deployed because the shared ecs0lib typed logging API remains a candidate.

• Scope: local isolated worktree only: /Users/richh/dev/_worktrees/tyrell-build10-power-logging-20260902, branch codex/tyrell-build10-power-logging-20260902, final HEAD 768f480a6c978c0213e1f8414e0431b7fc2704c2, ticket FEAT-20260902-10.
• Changed files: Sources/TyrellCore/Safety/PowerGovernanceActor.swift, Tests/TyrellCoreTests/PowerGovernanceCandidateLoggingTests.swift, docs/architecture/2026-09-02-build10-power-logging-candidate.md, and SESSION-STATE.md.
• The candidate-only implementation uses typed ECSUnifiedLogging and ECSLogMessage; workload names and IOKit failure detail are private before retention and sink delivery. It directly awaits logger delivery instead of using a detached task, while preserving AC-only operation, assertion acquire and release, workload reference counts, subsystem/category identity, and existing release-failure behavior.
• Verification: default package swift test passed 621 distinct tests; mapped candidate suite passed 627. Default and candidate release tyrell-app builds passed. Full commands, log hashes, transient-mapping structure, rollback, blocker, and promotion steps are in /Users/richh/dev/_handoff/tyrell-build10-power-logging-migration.md.
• No canonical Tyrell/ecs0lib file, Package.swift, credentials, CloudKit, signing, deployment, service, or live runtime was modified. No backup is required: rollback is to discard this isolated branch, or revert a future integration commit.
• Outstanding owner action: accept/publish a clean canonical ecs0lib revision with the reviewed typed logging API; then promote this lane by replacing the normal dependency and mechanically removing the documented candidate guards and fallback.