[Codex Review][FogStack] Review product readiness catalog refresh

[mdheller]

Scope

Codex review gate for the Copilot product-readiness refresh from issue #321.

Review focus

• Confirm changes are docs/catalog only unless the PR explicitly justifies otherwise.
• Confirm catalog/fogstack-packs-v0.1.yaml and docs/FOGSTACK_STATUS.md stay consistent.
• Confirm Office / Collaboration and Registry / Release Distribution are represented if the merged code/docs warrant it.
• Confirm Data/GovernAI and AI/Lattice readiness updates are grounded in merged repo surfaces, not aspiration.
• Confirm no claim says network registry publication, KMS/HSM signing, external identity, or production deployment exists unless the repo actually implements it.
• Confirm existing consumers are not broken by pack ID or schema changes.

Required result

Codex should leave one of:

• APPROVE: safe to merge
• REQUEST CHANGES: exact blockers
• COMMENT: non-blocking improvements

Merge gate

Do not merge the #321 implementation PR until this issue has explicit approval or maintainer override.

[mdheller]

APPROVE: Codex-style review passed for PR #326.

Reviewed against issue #321 and this review gate.

Checks performed:

• PR changes only docs/catalog files: catalog/fogstack-packs-v0.1.yaml, docs/FOGSTACK_PACKS.md, and docs/FOGSTACK_STATUS.md.
• Branch is current with main: 2 commits ahead, 0 behind.
• All workflow runs for head SHA 0c7730f454bc5e9d0a8a55d30c629962de3fedf5 are green.
• YAML/docs align on Office / Collaboration, Registry / Release Distribution, Data / GovernAI, and AI / Lattice Studio posture.
• repository_strategy: single-repo-for-now is preserved.
• No overclaim found for network registry publication, KMS/HSM signing, external identity, live inference/training, live data backend, or production deployment.

Non-blocking note: readiness percentages are still judgment calls, but the PR labels fixture/demo-only surfaces and keeps the claims bounded.

Merge gate status: approved, but PR #326 is still draft. The connector failed to mark it ready because its GitHub GraphQL response shape queried an invalid htmlUrl field. Do not merge until the PR is no longer draft or a maintainer override is explicitly recorded.