feat(community): recent proposal activity + participation summary (closes #262)

[Jaydearcadian]

Closes #262 — FR-7 / UJ-2–4 (community detail: recent proposal activity & participation).

Implemented gates

Gate	Implementation
N6.01	Governance reads remain scoped to the routed record.governorContract; no global Governor fallback.
N6.02	Exact ledger values remain primary. governanceDisplay.ts adds supplemental ~ duration using the ADR-006 5-second assumption and an explicit footnote.
N6.03	Active proposal count from ProposalState.Active.
N6.04	Up to three recent proposals, preserving stored newest-first order.
N6.05	Canonical links: /communities/[id]/proposals/[proposalId].
N6.06	Explanatory helpers appear beside threshold, quorum, delay, and period.
N6.07	Successful empty discovery is rendered as No proposals yet; it is not treated as an error.
N6.08	Discovery-level failure is rendered as Unavailable; partial proposal failures are Stale; loading is Delayed; clean results are Current.
N6.09	Changed-surface verification is green; full repository suite has unrelated baseline failures documented below.

Corrections

The PR is intentionally draft. Commit eedd1d3 adds an explicit discovery-error state so Unavailable is reachable and distinct from an empty successful result. Commit f5d5fe2 resolves the strict TypeScript number | undefined issue in voteAggregation and adds the lint exception for the dependency-failure state.

Verification

• npm install succeeds: 1,093 packages added and 1,099 audited.
• npx eslint . passes.
• tsc --noEmit --project ./tsconfig.json passes.
• Changed-surface/community tests pass: 6 files, 25 tests.
• Full suite: 59 files passed, 5 failed; 404 tests passed, 26 failed.
• Baseline comparison against origin/main reproduces the failing ProposalDetailPage, voteAggregation, and stellar suites. These are outside the Add recent proposal activity and participation summary to community detail #262 changed surface. The two node:test community-factory suites also fail in the existing Vitest configuration because Vite cannot bundle the Node built-in import.
• git diff --check passes and the remote branch head is verified at f5d5fe2d47f14ea57c52827ed18ea4d41fd32346.

The PR remains draft because the repository-wide suite is not green. The #262 changed surface is green, and the remaining failures require a separate baseline/test-harness issue rather than additional #262 feature work.

[vercel]

Someone is attempting to deploy a commit to the caneryy's projects Team on Vercel.

A member of the Team first needs to authorize it.