# Changelog

## Score

- CAI 44 → 43 (-1.1)
- Rubric changed (rubric-2026.10.5 → rubric-2026.11.2) — scores are not directly comparable.

## Lenses

- Code Health 71 → 71 (+0.0)
- Architecture 94 → 69 (-25.7)
- Maturity 43 → 43 (+0.0)
- Readiness 34 → 34 (+0.0)
- Security 42 → 42 (-0.5)
- Performance 85 → 85 (+0.0)

## Resolved (10)

- Coverage not measured — no coverage collector is wired up
- Documentation: no installation or build instructions (README.md)
- Documentation: no usage examples (README.md)
- The name 'connect' is used for fields that represent callbacks or actions to be invoked (e.g., `Action`, `Func`), which is semantically a noun/property name for a handler. However, in the context of `MockDataProducer` and `SimpleSubject`, these are clearly callback delegates (handlers) rather than the act of connecting itself. While 'connect' is a verb, using it as a field name for a delegate is ambiguous compared to standard conventions like 'OnConnect' or 'ConnectHandler'. More critically, comparing `MockDataProducer.connect` (a `Func`) and `SimpleSubject.connect` (an `Action`), the naming is consistent in its ambiguity, but inconsistent with the broader codebase where event-like handlers are often named with 'On' prefix (e.g., `OnRequest`, `OnClose`, `OnError`). However, since both are named 'connect' and serve similar 'callback' roles, this is a minor style issue rather than a cross-concept inconsistency. A stronger inconsistency is found in the test class `HttpServerTransactionDelegateTests` which tests `HttpServerTransactionDelegate`, but the delegate itself is named `HttpServerTransactionDelegate` while the transaction class is `HttpServerTransaction`. This is consistent. Let's look closer. `MockDataProducer.connect` vs `SimpleSubject.connect`. Both are callbacks. The inconsistency is that they are named as verbs/nouns 'connect' instead of following the 'On[Event]' pattern used elsewhere in the codebase (e.g., `OnRequest`, `OnClose`, `OnError`, `OnException`, `OnStop`, `OnEnd`, `OnConnected`, `OnData`). This creates a mixed convention for event/callback fields.
- XML-doc coverage: Kayak (Kayak/Kayak.csproj)
- XML-doc coverage: Kayak.Cli (Kayak.Cli/Kayak.Cli.csproj)
- XML-doc coverage: Kayak.Oars (Kayak.Oars/Kayak.Oars.csproj)
- XML-doc coverage: KayakDocs (tools/KayakDocs/KayakDocs.csproj)
- XML-doc coverage: KayakExamples (KayakExamples/KayakExamples.csproj)
- redundant comment (tools/KayakDocs/Program.cs)

## New (20)

- redundant comment (Kayak.Cli/Properties/AssemblyInfo.cs)
- redundant comment (Kayak.Cli/Properties/AssemblyInfo.cs)
- redundant comment (Kayak.Cli/Properties/AssemblyInfo.cs)
- redundant comment (Kayak.Cli/Properties/AssemblyInfo.cs)
- redundant comment (Kayak.Oars/Properties/AssemblyInfo.cs)
- redundant comment (Kayak.Oars/Properties/AssemblyInfo.cs)
- redundant comment (Kayak.Oars/Properties/AssemblyInfo.cs)
- redundant comment (Kayak.Oars/Properties/AssemblyInfo.cs)
- redundant comment (Kayak.Tests/Properties/AssemblyInfo.cs)
- redundant comment (Kayak.Tests/Properties/AssemblyInfo.cs)
- redundant comment (Kayak.Tests/Properties/AssemblyInfo.cs)
- redundant comment (Kayak.Tests/Properties/AssemblyInfo.cs)
- redundant comment (KayakExamples/Properties/AssemblyInfo.cs)
- redundant comment (KayakExamples/Properties/AssemblyInfo.cs)
- redundant comment (KayakExamples/Properties/AssemblyInfo.cs)
- redundant comment (KayakExamples/Properties/AssemblyInfo.cs)
- redundant comment (tools/KayakDocs/Properties/AssemblyInfo.cs)
- redundant comment (tools/KayakDocs/Properties/AssemblyInfo.cs)
- redundant comment (tools/KayakDocs/Properties/AssemblyInfo.cs)
- redundant comment (tools/KayakDocs/Properties/AssemblyInfo.cs)

## Architecture

- Unchanged — 2 containers · 0 contexts · 0 edges
