AMPR-216: T3 — Typed failure + RoutingEvent when no model meets the floor

[wow-miley]

Summary

• Makes RoutingResolution a sealed interface (Success | FloorUnmet) so a rung floor that no registered model satisfies is a typed, terminal result — not a silent downgrade
• Adds RoutingEvent.RouteFloorUnmet (HIGH urgency) emitted on EventSerialBus alongside existing routing events, carrying requestedFloor and bestAvailableRung for diagnostics
• CognitiveRelayImpl.resolve throws RoutingFloorUnmetException; resolveWithMetadata returns FloorUnmet — callers choose which API surface to use
• AgentLLMService throws RoutingFloorUnmetException rather than silently falling through to a sub-floor config

Changes

• RoutingResolution → sealed interface (Success, FloorUnmet) in CognitiveRelay.kt
• RouteFloorUnmet data class added to RoutingEvent.kt
• RoutingFloorUnmetException (new file) for the resolve() throw path
• CognitiveRelayImpl: floor-unmet detection + emitRouteFloorUnmet + bestRungAmongCapabilityRules helper
• SignificanceAwareEventLogger: RouteFloorUnmet → SIGNIFICANT
• AgentLLMService: handles FloorUnmet sealed variant
• CognitiveRelayPassthrough, CognitiveRelayCapabilityTest, CognitiveRelayCostTest, CognitiveRelayImplTest, RoutingEventTest: updated for sealed RoutingResolution
• CognitiveRelayFloorTest (new): 8 tests covering all validation criteria from the ticket

Test plan

• FloorUnmet returned when minRung = THREE and best available is rung TWO
• Success returned when a rung THREE model exists and matches
• Floor-unmet is terminal — no sub-floor AIConfiguration produced
• resolve() throws RoutingFloorUnmetException with correct requestedFloor / bestAvailableRung
• RouteFloorUnmet event emitted on EventSerialBus with correct fields
• RouteSelected NOT emitted when floor is unmet
• null bestAvailableRung when registry has no descriptors for the configured rules
• No regression: no minRung requirement resolves to Success normally

Closes: AMPR-216 · Depends on: #577 (T2)

🤖 Generated with Claude Code

[github-actions]

Concept staleness check — 4 warning(s).

These changes touched files listed under a concept's tracked_sources without updating the concept file. Either update the concept (and bump last_verified) or include a Concept-Verified: <ConceptName> trailer in a commit on this PR.

Validator output

⚠ Concept 'CognitionTrace' may be stale: ampere-core/src/commonMain/kotlin/link/socket/ampere/agents/domain/event/RoutingEvent.kt matches tracked_sources pattern ampere-core/src/commonMain/kotlin/link/socket/ampere/agents/domain/event/RoutingEvent.kt but docs/concepts/cognition-trace.md was not modified.
⚠ Concept 'CognitiveRelay' may be stale: ampere-core/src/commonMain/kotlin/link/socket/ampere/agents/domain/routing/CognitiveRelay.kt matches tracked_sources pattern ampere-core/src/commonMain/kotlin/link/socket/ampere/agents/domain/routing/** but docs/concepts/cognitive-relay.md was not modified.
⚠ Concept 'EventSerialBus' may be stale: ampere-core/src/commonMain/kotlin/link/socket/ampere/agents/events/utils/SignificanceAwareEventLogger.kt matches tracked_sources pattern ampere-core/src/commonMain/kotlin/link/socket/ampere/agents/events/utils/SignificanceAwareEventLogger.kt but docs/concepts/event-serial-bus.md was not modified.
⚠ Concept 'PropelLoop' may be stale: ampere-core/src/commonMain/kotlin/link/socket/ampere/agents/domain/reasoning/AgentLLMService.kt matches tracked_sources pattern ampere-core/src/commonMain/kotlin/link/socket/ampere/agents/domain/reasoning/** but docs/concepts/propel-loop.md was not modified.

validate-concepts: 4 warning(s). Validator informs; never blocks.