Document the verified workflow and use numinous-forge

[numinousmuses]

Use numinous-forge as the operator CLI and add a README entry point for the completed demonstration. The trusted workflow downloads the renamed binary and records its verified SHA-256 in the run log. The guide links the merged repairs, rejected PR, recurring run history, and deployed qualification. It also includes a hashed snapshot of the accepted checks and agent instructions, so reviewers can inspect what governed the work and propose changes.

Public receipts omit credentials and private infrastructure details. The guide states the supported Linux scope and distinguishes fork merges from upstream releases.

flowchart LR
  subgraph Before
    B1[Reviewer opens README.md] --> B2[Upstream project introduction]
    B2 --> B3[Search PRs and separate operator records]
    B4[Trusted workflow run_ci.py] --> B5[Download executable named forge]
  end

Loading

flowchart LR
  subgraph After
    A1[Reviewer opens README.md] --> A2[.forge/README.md workflow and examples]
    A2 --> A3[Merged PRs and rejected regression]
    A2 --> A4[.forge/evidence source-bound test receipts]
    A2 --> A5[.forge/policy accepted checks and skills]
    A5 --> A6[Propose reviewed changes for future deployment]
    A7[Trusted workflow run_ci.py] --> A8[Download numinous-forge and verify SHA256]
    A8 --> A9[Submit pinned commit to independent verification]
  end

Loading

Validation: make docs-check, local link and JSON checks, and Forge CI against the PR merge. Infrastructure qualification and the live demo capture bind the deployed controller, runtime, project policy, and recorded examples to their tested versions.