Standardize repository README and docs to latest Fast Forward conventions

[coisa]

Objective

Align the repository README and documentation with the current Fast Forward documentation standards so content, automation references, and contributor guidance stay consistent after the recent toolchain and workflow standardization.

Current Limitation

Public documentation (README.md, .github/profile/README.md, and docs pages) still mixes legacy phrasing and link patterns and does not fully reflect the newest doc conventions used by Fast Forward repositories.

Proposed Work

Create a documentation-only refactor that applies the updated style and structure standards across user-facing docs:

• README alignment and wording simplification
• Standardized command and CI references
• Consistent section ordering, naming, and cross-linking
• Accurate repository automation references (actions, reports, branch protections, etc.)
• Synchronized updates where docs depend on generated outputs

Scope

• Update README.md, .github/profile/README.md, and key files under docs/ that expose repository workflows and usage guidance.
• Keep the work limited to documentation and generated output references, without changing runtime behavior.
• Update any references affected by recent actions/workflow behavior.

Non-goals

• Do not change package internals, code behavior, release automation logic, or build tooling itself.
• Do not implement enum updates (kept for issue 2).
• Do not perform broad restructuring outside the repository's existing documentation architecture.

Acceptance Criteria

Delivery Criteria

• README.md and primary docs reflect the current Fast Forward documentation style and terminology.
• Cross-references, links, commands, and file paths are updated and validated against current repository behavior.
• A reviewer can follow the same canonical structure used by other Fast Forward repos after this update.
• No unrelated functional changes are included.

Documentation / Content Criteria

• MUST: The affected documentation or content MUST follow the repository's existing information architecture and naming conventions.
• MUST: Related navigation, cross-links, or synchronized outputs MUST be updated when the change affects them.
• MUST: Examples, commands, and file paths MUST remain accurate for the current repository behavior.
• MUST: The update MUST avoid duplicating content that should live in a single canonical location.