docs: document `uf init --force` behavior for Group B sub-tools

[yvonnedevlinrh]

Context

PR unbound-force/unbound-force#524 fixes a bug where uf init --force silently skipped re-initialization for Group B sub-tools (specify, replicator, openspec, gaze). This is a user-visible behavior correction that requires documentation updates.

Upstream issue: unbound-force/unbound-force#479

What Changed

Previously, uf init --force only re-initialized Dewey (Group A). Group B tools were silently skipped even with --force, leaving the user with a false impression that all tools were re-initialized.

After the fix:

• uf init --force re-initializes all sub-tools, not just Dewey
• Sub-tools that support --force (specify, openspec, gaze) receive the flag via their CLI
• Idempotent tools (replicator) are re-run without a force flag
• The init summary now shows "re-initialized" for tools that were force-refreshed, distinguishing them from first-time "initialized"

Documentation Impact

Any documentation covering uf init or uf init --force should reflect:

1. --force scope: The flag applies to all sub-tools, not just file scaffolding and Dewey
2. Recovery workflow: uf init --force is the documented recovery path for partial or interrupted initialization
3. Output distinction: The init summary displays "re-initialized" for force-refreshed tools vs "initialized" for first-time setup

Spec Reference

• Spec 017 FR-007: uf init --force MUST overwrite stale config
• Spec 027 FR-014 (delta): Force flag passthrough for Group B tools
• OpenSpec change: openspec/changes/fix-init-force-passthrough/

[jflowers]

Triage Assessment

Verdict: Valid | Category: Enhancement (documentation) | Objectivity: Objective

This issue is a well-scoped documentation request that fulfills the constitution's Cross-Repo Documentation mandate. The behavioral change in uf init --force (PR unbound-force/unbound-force#524) — extending scope from Dewey-only to all sub-tools — is user-visible and requires corresponding documentation updates.

Minor note: The spec reference "Spec 027 FR-014" appears to be inaccurate — Spec 027 (Externalize Tool Initialization) defines FR-001 through FR-013 only. The Spec 017 FR-007 reference is valid.

Recommended next steps:

• Update uf init documentation to reflect the expanded --force scope
• Document the "re-initialized" vs "initialized" output distinction
• Add the recovery workflow using uf init --force

This triage was performed by the Divisor review panel.