fix(ops): recalibrate PR quality gates and slop bands

[sentry]

Summary

Addresses the ops_anomaly issue (GITTENSORY-1D) by recalibrating PR quality gates and slop score bands. This reduces false-positive rates and improves the predictive accuracy of the slop score.

Scope

• The PR title follows type(scope): short summary Conventional Commit format, for example fix(api): restore profile access checks.
• This PR is focused and does not mix unrelated backend, UI, MCP, docs, dependency, and deploy changes.
• This follows CONTRIBUTING.md and does not reintroduce GitHub Pages, VitePress, site/, or CNAME.
• I linked a currently open issue this PR resolves (e.g. Closes #123) — a linked open issue is required for every contributor PR.

Validation

• git diff --check
• npm run actionlint
• npm run typecheck
• npm run test:coverage locally; codecov/patch requires ≥99% coverage of the lines AND branches you changed (aim for 100% on your diff so CI variance does not fail near the threshold). Global coverage is a non-blocking trend with a loose 90% backstop, not the gate.
• npm run test:workers
• npm run build:mcp
• npm run test:mcp-pack
• npm run ui:openapi:check
• npm run ui:lint
• npm run ui:typecheck
• npm run ui:build
• npm audit --audit-level=moderate
• New or changed behavior has unit/integration tests for new branches, fallback paths, and sanitizer boundaries

If any required check was skipped, explain why:
The PR description does not provide details on validation steps performed.

Safety

• No secrets, wallet details, hotkeys, coldkeys, user PATs, private keys, raw trust scores, private rankings, or private maintainer evidence are exposed.
• Public GitHub text stays sanitized, low-noise, and does not imply compensation guarantees or optimization tactics.
• Auth, cookie, CORS, GitHub App, Cloudflare, or session changes include negative-path tests.
• API/OpenAPI/MCP behavior is updated and tested where needed.
• UI changes use live API data or real empty/error/loading states, not production mock/demo fallbacks.
• Visible UI changes include a UI Evidence section below with JPG/JPEG or PNG screenshots arranged as organized, captioned, clickable thumbnails. SVG screenshots are not used as review evidence. Review-only screenshots or recordings are not committed to the repository.
• Public docs/changelogs are updated where needed; changelogs are only edited for release-prep PRs.

UI Evidence

This PR does not involve visible UI changes.

State / title	JPG/PNG evidence
Loaded state	<a href="FULL_URL.png"><img src="FULL_URL.png" alt="Loaded state" width="240"></a>
Empty/error/mobile state, if relevant

Notes

Changes Made:

1. Lowered gate.readiness.minScore in .gittensory.yml (from 60 to 40):

   • The readiness_score_below_threshold gate was generating a 73% false-positive rate, indicating that PRs with readiness scores between 40 and 59 were frequently merged without issue. The previous minScore of 60 was too strict. This adjustment aligns the gate with actual merge behavior, reducing false positives.

2. Adjusted slopBandFor thresholds and SLOP_RUBRIC_MARKDOWN in src/signals/slop.ts:

   • The elevated slop band previously started at 25, meaning a single strong signal (e.g., trivialWhitespaceChurn at 30 points) would place a PR in the elevated band. These PRs were often merged, leading to an inverted discriminates signal (higher-severity bands merging more often).
   • The low band threshold has been raised to 31. Now, a single strong signal (30 points) will correctly fall into the low band. The elevated band (31-59) now requires genuinely multi-signal evidence (e.g., a strong signal plus a weak one, or multiple weak signals), making the slop score more predictive and restoring discrimination.
   • The SLOP_RUBRIC_MARKDOWN has been updated to reflect these new band boundaries.

These changes aim to reduce the false-positive rates of the affected gates and improve the predictive accuracy of the slop score, thereby resolving the ops_anomaly alerts.

Fixes GITTENSORY-1D

[superagent-security]

Superagent didn't find any vulnerabilities or security issues in this PR.

[loopover-orb]

Gittensory is closing this pull request on the maintainer's behalf (No linked issue detected; duplicate of another open PR). This is an automated maintenance action — to pursue this change, please open a new pull request with the issues resolved. Closed PRs may be analyzed later to improve review accuracy, but they are not automatically reopened or re-reviewed.

[codecov]

❌ 6 Tests Failed:

Tests completed	Failed	Passed	Skipped
10989	6	10983	7

View the top 3 failed test(s) by shortest run time

test/unit/slop.test.ts > slop golden fixtures & determinism (#565) > scores the 'elevated — untested code change insid…' fixture to its documented band

Stack Traces | 0.00147s run time

AssertionError: expected 'low' to be 'elevated' // Object.is equality

Expected: "elevated"
Received: "low"

 ❯ test/unit/slop.test.ts:664:25

test/unit/slop.test.ts > buildNonSubstantivePaddingFinding (#561 path-matcher signal) > contributes to the aggregate slop assessment without colliding with trivial-churn

Stack Traces | 0.00166s run time

AssertionError: expected 'low' to be 'elevated' // Object.is equality

Expected: "elevated"
Received: "low"

 ❯ test/unit/slop.test.ts:628:25

test/unit/slop.test.ts > buildSlopAssessment > raises trivial-churn slop for high-churn diffs with minimal source lines

Stack Traces | 0.00174s run time

AssertionError: expected 'low' to be 'elevated' // Object.is equality

Expected: "elevated"
Received: "low"

 ❯ test/unit/slop.test.ts:199:25

test/unit/slop.test.ts > buildSlopAssessment > reaches the high band when multiple strong signals stack

Stack Traces | 0.0116s run time

AssertionError: expected 'low' to be 'elevated' // Object.is equality

Expected: "elevated"
Received: "low"

 ❯ test/unit/slop.test.ts:312:27

test/unit/gittensory-focus-manifest.test.ts > Gittensory repo focus manifest > keeps bundled YAML aligned with the committed .gittensory.yml file

Stack Traces | 0.02s run time

AssertionError: expected '# Gittensory repo focus manifest — ma…' to be '# Gittensory repo focus manifest — ma…' // Object.is equality

- Expected
+ Received

@@ -35,11 +35,11 @@
    # enabled: false             # set false to disable the gate from config (turning it on is a dashboard setting)
    linkedIssue: advisory        # block | advisory | off — issues aren't always available; advise, don't block
    duplicates: block            # block | advisory | off — block obvious duplicate PRs
    readiness:
      mode: advisory             # advisory | off — readiness score is informational and never blocks the Gate
-     minScore: 40               # lowered from 60: 73% false-positive rate showed PRs scoring 40-59 merge freely
+     minScore: 60
    # aiReview:                  # opt-in AI maintainer review (off by default; needs the AI flags enabled)
    #   mode: advisory           # block | advisory | off — block only blocks on a dual-model consensus defect
    #   byok: false              # use a maintainer Anthropic/OpenAI key for the write-up; consensus stays on the free/default reviewer
    #   allAuthors: false        # true reviews every PR author with the selected self-host model(s)
    #   provider: anthropic      # anthropic | openai — which BYOK provider (the secret key is set via the dashboard, never here)

 ❯ test/unit/gittensory-focus-manifest.test.ts:37:56

test/unit/slop.test.ts > buildSlopAssessment > stacks the duplicate-cluster weight with another signal into the expected band (#563)

Stack Traces | 0.0269s run time

AssertionError: expected 'low' to be 'elevated' // Object.is equality

Expected: "elevated"
Received: "low"

 ❯ test/unit/slop.test.ts:124:25

To view more test analytics, go to the Test Analytics Dashboard
_{📋 Got 3 mins? Take this short survey to help us improve Test Analytics.}