fix(changelog): prepend #588 entry to top of Unreleased section (F8)
CI / benchmark-publish (pull_request) Has been skipped
CI / lint (pull_request) Successful in 15s
CI / build (pull_request) Successful in 16s
CI / quality (pull_request) Successful in 18s
CI / security (pull_request) Successful in 36s
CI / typecheck (pull_request) Successful in 38s
CI / unit_tests (pull_request) Successful in 2m42s
CI / integration_tests (pull_request) Successful in 3m2s
CI / docker (pull_request) Successful in 39s
CI / coverage (pull_request) Successful in 4m32s
CI / benchmark-regression (pull_request) Successful in 29m33s

Move the (#588) CHANGELOG entry from after (#203) to the top of the
## Unreleased section, matching the convention that newest entries are
prepended first. All pre-existing entries (#473, #495, #203, #494)
remain intact and unmodified.

Addresses reviewer finding F8 from PR #611 second-pass review.
Refs: #588
This commit is contained in:
2026-03-06 20:31:09 +00:00
parent 13618fb8d5
commit fb96d7910b
+12 -12
View File
@@ -2,6 +2,18 @@
## Unreleased
- Added `PostgreSQLAnalyzer` and `DockerComposeAnalyzer` domain-specific analyzers
(Phase 2 of issue #588). `PostgreSQLAnalyzer` parses DDL content via regex and
extracts `uko-data:Table`, `uko-data:Column`, `uko-data:ForeignKey`, `uko-data:View`,
and `uko-data:Schema` triples with column metadata (data type, nullability, primary
key). `DockerComposeAnalyzer` parses Docker Compose YAML via `yaml.safe_load` and
extracts `uko-infra:DeploymentUnit`, `uko-infra:Service`, `uko-infra:Port`,
`uko-infra:EnvironmentVariable`, and `uko-infra:connectsTo` triples. Both satisfy
`AnalyzerProtocol` and register in `AnalyzerRegistry` by file extension. Includes
34 Behave BDD scenarios covering all four analyzers (protocol conformance, registry
operations, triple extraction, error handling, cross-analyzer URI scheme and
confidence checks), 6 Robot Framework integration smoke tests, and updated
`__init__.py` exports. (#588)
- Added general-purpose domain event system under
`cleveragents.infrastructure.events`. `EventType` StrEnum defines 38 typed
event identifiers across 9 domains (plan lifecycle, decision, invariant, actor,
@@ -38,18 +50,6 @@
server-mode wiring. `--log-level` flag controls logging verbosity. Includes 48 Behave
BDD scenarios, Robot Framework smoke tests, ASV startup latency benchmarks, and
`docs/reference/lsp_stub.md`. (#203)
- Added `PostgreSQLAnalyzer` and `DockerComposeAnalyzer` domain-specific analyzers
(Phase 2 of issue #588). `PostgreSQLAnalyzer` parses DDL content via regex and
extracts `uko-data:Table`, `uko-data:Column`, `uko-data:ForeignKey`, `uko-data:View`,
and `uko-data:Schema` triples with column metadata (data type, nullability, primary
key). `DockerComposeAnalyzer` parses Docker Compose YAML via `yaml.safe_load` and
extracts `uko-infra:DeploymentUnit`, `uko-infra:Service`, `uko-infra:Port`,
`uko-infra:EnvironmentVariable`, and `uko-infra:connectsTo` triples. Both satisfy
`AnalyzerProtocol` and register in `AnalyzerRegistry` by file extension. Includes
34 Behave BDD scenarios covering all four analyzers (protocol conformance, registry
operations, triple extraction, error handling, cross-analyzer URI scheme and
confidence checks), 6 Robot Framework integration smoke tests, and updated
`__init__.py` exports. (#588)
- Validated M3 acceptance criteria for v3.2.0 milestone closure. All 10 E2E
verification tests pass against the final implementation, exercising real
CLI command paths (``plan use``, ``plan execute``, ``plan tree``,