[Copilot][FogStack] Refresh pack readiness for Office, Lattice, Data/GovernAI, and Registry surfaces

[mdheller]

Scope

Refresh FogStack product-pack readiness after the recent upstream Office collaboration, Lattice Studio/Data/GovernAI, GAIA, and registry publication work.

Expected files

• catalog/fogstack-packs-v0.1.yaml
• docs/FOGSTACK_STATUS.md
• optionally docs/FOGSTACK_PACKS.md if prose is stale

Inputs to inspect

• Office collaboration runtime PRs docs(platform): add office collaboration runtime slice #314-services(platform): add suggestion event history #319
• Lattice product-surface PRs Add Lattice Data/GovernAI vertical fixture #299-Add Lattice runtime release readiness fixture #308
• FogStack release/publication PRs through Add Fog Stack filesystem registry adapter #215
• Current docs/FOGSTACK_STATUS.md
• Current catalog/fogstack-packs-v0.1.yaml

Acceptance criteria

• Add explicit row/category for FogStack Office / Collaboration if warranted.
• Add explicit row/category for FogStack Registry / Release Distribution if warranted.
• Update readiness percentages to reflect current merged product surfaces, not stale early estimates.
• Keep repository_strategy: single-repo-for-now unless an independent lifecycle is now demonstrably justified.
• Add notes explaining why Data/GovernAI and AI/Lattice readiness changed.
• Do not overclaim production readiness where surfaces remain fixture-only or demo-only.

Non-goals

• Do not create new repos.
• Do not rename existing pack IDs without migration notes.
• Do not change runtime code.

Copilot implementation instruction

This is a docs/catalog tranche only. Keep changes surgical and cite merged PR numbers in prose where useful.

Codex review checklist

• Confirm readiness numbers are consistent across YAML and docs.
• Confirm Office and Registry additions do not break existing consumers.
• Confirm no claim says external registry, KMS/HSM, or production deployment exists unless it actually exists on main.