[bmscomp]

These two planning documents stayed untracked in the main checkout. This PR commits them next to plans/mcp-server.md, updated to say what shipped.

plans/conformity-spec.md is the design of KafkaReference and POST /api/conformity/check.

• A Shipped row names the PRs that delivered it: feat(conformity): read a KafkaReference strictly and compare its values #407 to test(conformity): hold the CI kind cluster to a reference, live #416 for v1 and v1.1, then feat(conformity): per-topic replication factor and min.insync.replicas #419, feat(conformity): lint and format a reference offline; check lints it first #420, fix(conformity): refuse YAML the CLI would send with a rule missing #421 to fix(conformity): no pass with nothing to check, and the edge cases #424, feat(conformity): lint finds placement, quorum and durability rules no cluster can meet #430, docs(book): a Conformity Checks chapter teaches the reference language step by step #431, feat(conformity): lint finds resource, version and listener rules no cluster can meet #432 and feat(cli): kates conformity check fits the terminal: details go on lines under each row #433.
• The file references point at cli/examples/conformity/, where the schema and examples live.
• The inline examples stay as the 2026-10-19 drafts, and the text says so, since this is a design record.

plans/conformity-enhancements.md is the review of 2026-10-20: four lenses, each finding checked by a verifier, 29 confirmed.

• A new Outcome table maps every finding to the PR that fixed it.
• 17 are fixed (feat(conformity): per-topic replication factor and min.insync.replicas #419 to fix(conformity): no pass with nothing to check, and the edge cases #424, docs(book): a Conformity Checks chapter teaches the reference language step by step #431, feat(cli): kates conformity check fits the terminal: details go on lines under each row #433).
• 2 are partly covered by the book chapter.
• 10 are still open, such as exposed-listener rules, operand checks, a snapshot generator and the MCP tool.

Left out: plans/conformity/, which holds the draft schema and examples. The shipped copies in cli/examples/conformity/ supersede them, and the draft schema lacks kafka.source and topics. Committing both would leave two diverging schemas in the repository.

Checked: every finding id appears in the outcome table (29 of 29). Each PR mapping comes from that PR's description, and every cited PR is merged. No CI job reads plans/.