Decide curated promotion scope for infrastructure enrichment

[Svaag]

Context

Knowledge PR #15 added source-cited OpenRouter LLM infrastructure enrichment under okf/generated/enriched/infrastructure.md. The synthesis is useful for retrieval/context packs, but generated enrichment remains advisory and subordinate to repository source truth.

Goal

Decide which high-value, durable facts or operating lessons from the infrastructure enrichment should be promoted into reviewed curated OKF under okf/curated/.

Candidate promotion topics

• Knowledge MCP deployment contract: containerized, read-only, loopback-bound, streamable HTTP default at /mcp, SSE support retained.
• Docker routed IPv6 pattern on loop: GUA 2a0c:b641:b50:f0::/64, no IPv4/NAT dependency, host networking plus loopback bind for Knowledge MCP.
• Knowledge/Engineering/NOC credential separation: CI/CD PR-Agent OpenRouter key, Engineering Loop runtime key, Knowledge Loop enrichment key.
• Observed evidence boundaries: sanitized, evidence-only, time-bounded runtime facts lose to A0/A1 intended state.
• Monitoring and deployment smoke contract for Knowledge MCP rollouts.
• Any durable lessons from the infrastructure enrichment that should become A1 reviewed OKF rather than A4 advisory synthesis.

Acceptance criteria

• For each promoted item, create or update curated OKF with truth_owner: okf, authority: A1, non-empty source_refs, last_verified_at, confidence, and dispute_policy.
• Do not promote broad generated prose wholesale.
• Preserve repo_wins/source-truth hierarchy where source repos own intended state.
• Add retrieval/eval coverage for promoted concepts that agents should reliably find.
• Regenerate exports/reports and pass the standard Knowledge validation suite.