v1.134.0

fix: close FuSaOps's own traceability gaps (#73) — all 29 orphan functions tagged, all 7 untested requirements closed. Function-tag coverage 89%→99%, requirement→test coverage 100% (426/426).

v1.133.0

fix: audit findings — stale docs, tool-count inconsistency, undocumented commands

Fixes from a 2026-07-27 deep audit (#74, #75).

#74 — false auth claim, five-vs-six inconsistency, stale tables

• docs/tool-safety-manual.md: corrected the false "the web dashboard has no
  authentication" claim — fusaops serve --auth user:pass (HTTP Basic Auth,
  with an optional --auth-ro read-only role) genuinely exists.
• README.md Install section: added jfusa, changed "bundles all five" to
  "bundles all six."
• README.md "Bundled tools" tables: updated to the actual current tags —
  go-FuSa v0.33.4, cpp-FuSa v0.14.3, c-FuSa v0.5.42, rust-FuSa v0.3.8,
  py-FuSa v0.2.6, java-FuSa v0.4.5, spec v1.11.
• CLAUDE.md: architecture table expanded from 11 packages to all ~38;
  "future tools" language replaced with the current six-language reality.
  fusaops.go's package doc comment updated to match.

#75 — docs/commands/ and README cover only 9/46 subcommands

• Added 24 new docs/commands/*.md pages (comp, hooks, impact, disposition,
  pr, verify, sign, qualify, release, safety-case, sci, sas, tara, fmea,
  vuln, template, hara, vv, metrics, badge, slsa, capabilities, req,
  coverage), bringing documented commands from 9 to 33.
• README.md: new "Compliance, evidence, and workflow commands" section
  gives every previously-unmentioned subcommand a one-line description and
  example.
• cmd/fusaops/main.go: package doc comment now includes comp.

Full Changelog: v1.132.0...v1.133.0

v1.132.0

docs: new docs/getting-started.md — step-by-step guide for applying FuSaOps to a project (zero-config scan, config file, CI gate, regression-only gating, dashboard, deeper safety evidence). Linked from README right after the intro.

v1.131.0

feat: x-FuSa spec v1.11.0 — new §1.4.1 requirement annotation completeness (function-level tag placement, func-coverage gate, dangling-ID detection, scan-path completeness MUST)

v1.130.1

Coverage expansion: server/multi.go ListenAndServe, Serve, and runScheduler now at 100% (up from 0%); runRelease manifest save error branch covered; overall statement coverage 95.3% → 95.5%.

v1.130.0

fix: Windows CI — gofmt and unix-permission t.Skip in five more gap tests (comp, fleet, sbom, cmd/fusaops, doctemplate)

FuSaOps v1.129.0

Fix Windows CI: gofmt + unix-permission t.Skip in adapter/scan gap tests

FuSaOps v1.128.0

Coverage expansion — scan/sbom/adapter/sci (6 new gap test files)

• scan: 94.7% → 100.0% — walk-error propagation via unreadable subdir
• sbom: 94.8% → 100.0% — RenderToFile stdout fallback, JSON/SPDX encode errors, em-dash for version-less packages, same-name/different-version sort fallthrough
• adapter: 94.2% → 97.9% — Detect/Applicable walk errors, Check/Qualify/cpfusa ReadFile errors (runner deletes output), SBOM bad-JSON Unmarshal error
• sci: +2 branches — Language suffix [lang] and SHA256 line in renderText

Overall statement coverage: 95.3% (95.4% after rebuild).

Full Changelog: v1.127.0...v1.128.0

FuSaOps v1.79.0

Docs: spec v1.10.11 snapshot — all-tool safety features, latest versions

• SpecVersion bumped to "1.10.11" — captures the four safety features (HLR/LLR decomposition, tool qualification display, MC/DC coverage, V&V independence) now implemented across all six x-FuSa tools.
• x-fusa-spec.md v1.10.11: §11 snapshot updated to go-FuSa v0.33.0 · cpp-FuSa v0.14.0 · c-FuSa v0.5.37 · rust-FuSa v0.3.2 · py-FuSa v0.2.1 · java-FuSa v0.4.1. §14 changelog entry added.
• README.md: bundled-tool version table updated to latest releases.

FuSaOps v1.78.0

Maximize test coverage and requirement annotations.