Engine release due: 3.17.1

[github-actions]

Summary

A @loopover/engine release appears due.

• Proposed version: 3.17.1
• Latest tag: engine-v3.17.0
• npm latest: 3.17.0
• Package version in repo: 3.17.0
• Unreleased engine-related commits: 3

Unreleased Commits

• 2dbb800 metrics(ledger): re-evaluation counts and per-author-class review-parity rollups (metrics(ledger): re-evaluation counts and per-author-class review-parity rollups #9877)
• 31b29da fix(gate): never close a PR for visual evidence the pipeline cannot produce (The screenshot-table gate can close PRs for evidence the bot is structurally unable to produce #9881) (fix(gate): never close a PR for visual evidence the pipeline cannot produce #9934)
• b21216b chore(engine): one maintainer-association predicate, with a guard against the ninth copy (chore(engine): one maintainer-association predicate, with a guard against the ninth copy #9932)

Changed Files

• apps/loopover-ui/content/docs/verify-this-review.mdx
• apps/loopover-ui/public/openapi.json
• apps/loopover-ui/src/components/site/fairness-report-page.test.tsx
• apps/loopover-ui/src/components/site/fairness-report-page.tsx
• apps/loopover-ui/src/components/site/proof-of-power-stats.test.tsx
• migrations/0206_decision_record_findings_count.sql
• migrations/0207_visual_capture_unobtainable.sql
• package.json
• packages/loopover-contract/src/public-api.ts
• packages/loopover-engine/src/advisory/gate-advisory.ts
• packages/loopover-engine/src/index.ts
• packages/loopover-engine/src/review/screenshot-table-gate.ts
• packages/loopover-engine/src/scoring/pending-pr-scenarios.ts
• packages/loopover-engine/src/settings/author-association.ts
• packages/loopover-engine/src/signals/engine.ts
• packages/loopover-engine/src/signals/issue-quality-report.ts
• packages/loopover-engine/src/signals/predicted-gate-engine.ts
• packages/loopover-engine/test/author-association.test.ts
• scripts/check-maintainer-association-copies.ts
• src/api/routes.ts
• src/db/repositories.ts
• src/db/schema.ts
• src/github/author-association.ts
• src/github/commands.ts
• src/queue/processors.ts
• src/review/decision-record.ts
• src/review/review-parity-rollups.ts
• src/review/visual/capture.ts
• src/rules/advisory.ts
• src/services/contributor-evidence-graph.ts
• src/services/control-panel-roles.ts
• src/services/outcome-calibration.ts
• src/services/recommendation-outcomes.ts
• src/signals/local-branch.ts
• src/signals/settings-preview.ts
• src/types.ts
• test/integration/public-stats-route.test.ts
• test/unit/backfill-decision-labels-core.test.ts
• test/unit/check-maintainer-association-copies-script.test.ts
• test/unit/decision-record.test.ts
• test/unit/queue-2.test.ts
• test/unit/queue-3.test.ts
• test/unit/review-parity-rollups.test.ts
• test/unit/screenshot-table-gate.test.ts

Release-Prep Checklist

• Bump packages/loopover-engine/package.json to 3.17.1
• Run npm run build --workspace @loopover/engine
• Run npm run test:engine-pack
• Run npm run actionlint
• Merge the release-please PR (it maintains this package's CHANGELOG.md natively)
• Tag engine-v3.17.1
• Watch npm trusted publishing and the GitHub Release job

[linear-code]

JSO-6909

[JSONbored]

Stale — superseded by the 3.18.0 line.

This issue proposed 3.17.1 against engine-v3.17.0, but engine has since released 3.18.0 (npm @loopover/engine@3.18.0, manifest packages/loopover-engine: 3.18.0). All three commits it lists are ancestors of engine-v3.18.0:

• 2dbb800 metrics(ledger): re-evaluation counts and per-author-class review-parity rollups (metrics(ledger): re-evaluation counts and per-author-class review-parity rollups #9877)
• 31b29da fix(gate): never close a PR for visual evidence the pipeline cannot produce (fix(gate): never close a PR for visual evidence the pipeline cannot produce #9934)
• b21216b chore(engine): one maintainer-association predicate (chore(engine): one maintainer-association predicate, with a guard against the ninth copy #9932)

Verified with git merge-base --is-ancestor <sha> engine-v3.18.0 for each. Nothing here is unreleased, so there is no 3.17.1 to cut.

The sibling #9937 (ui-kit 1.3.1) is not stale and is being fixed separately — that one is genuinely stuck, for a structural reason rather than a stale snapshot.