feat(ux): add project status facade with freshness and guided next actions

[2233admin]

User flow

code-intel status answers whether the project is ready, which committed run is authoritative, whether it is current for this checkout, and what bounded action to take next.

Scope

• Add a public Rust CLI facade: code-intel status [] [--json].
• Reuse ProjectContext, repository binding, CommittedEvidenceController receipts, and the existing snapshot freshness calculation.
• Report unindexed repositories as needs_run with a recovery action; do not fabricate an empty/green committed run.
• Report indexed repositories as ready or stale with the verified run identity and recorded/current snapshot identities.
• Return structured next actions for context, query, impact, and evidence tracing; keep argv machine-readable and human output concise.
• Treat this issue and docs/research/gitnexus-internalization.md as a living brief that can be revised from product feedback.

Non-goals

• No filesystem-wide project discovery scanner in this slice.
• No GitNexus source, graph database, parser, MCP server, Web UI, or editor integration.
• No change to CodeNexus provider payload, admission, freshness, or unavailable authority semantics.

Acceptance

• Unindexed, current, and stale fixtures are covered.
• The JSON output has a versioned identity and bounded nextActions.
• Command catalog/help/CLI integration contracts are updated.
• Focused Rust tests, relevant integration contracts, Sentrux session gate, and hardcoded-path scan pass.

References DR-0006 and docs/research/gitnexus-internalization.md.

[2233admin]

Claimed by this session. Branch: codex/issue-281-project-status. Approach: add a thin typed Rust status facade over ProjectContext plus committed receipt/freshness, with needs_run recovery and bounded next-action argv; no new provider or indexing semantics.