ci(coverage): set the coverage baseline at measured current (91%)

[stranske]

Why this file matters

Without config/coverage-baseline.json, tools/coverage_trend.py reports baseline_status: absent and computes no delta — and Maint Coverage Guard has nothing to compare against. A coverage regression in this repo is currently undetectable.

The number

Measured 91.02% from this repo's own coverage payload, floored to 91, with warn_drop: 1.0 absorbing run-to-run jitter.

Set at measured current, not at an aspiration — deliberately. Both failure directions are live in this fleet right now:

repo	baseline	real	effect
Fine-Art-Archive	25	81.45%	56 points low — cannot fail
Workflows	85	76.72%	8 points high — red on arrival

A baseline above reality gets switched off; one far below it never fires. Same defect, opposite directions.

Keyed line

Both coverage_trend.py and coverage_guard.py accept line or coverage, with line taking precedence. That mismatch was itself a live defect until stranske/Workflows#3251, under which this repo's trend silently scored 0.0.

It's a ratchet

Raise it as coverage rises. It is not a target, and it should never be lowered to make a run pass.

🤖 Generated with Claude Code

[coderabbitai]

Warning

Review limit reached

Next included review available in 47 minutes.

View limit details

Limit details: You’ve used the included review currently available. Your 83 included PR review attempts over the past 7 days set your current allowance at 1 review per hour.

Your organization has reached its usage spending cap. Adjust your spending cap in the billing tab.

Learn how review limits work.

Review configuration:

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: 946bfd68-8f52-41f3-90fd-67441c36a919

📥 Commits

Reviewing files that changed from the base of the PR and between cf0c3c0 and a705bf1.

📒 Files selected for processing (1)

• config/coverage-baseline.json

---

_{Comment @coderabbitai help to get the list of available commands.}

[agents-workflows-bot]

Workflow source needed

PR #930 needs either a linked GitHub issue or one valid non-issue Workflow Source before PR metadata automation can manage it safely.

Please do one of:

• Add <!-- meta:issue:123 --> or a normal Closes #123 / Related to #123 line.
• Check one Workflow Source option in the PR body.
• Add a hidden marker such as <!-- workflow-source:local_request -->, <!-- workflow-source:manual_remote -->, <!-- workflow-source:review_followup -->, <!-- workflow-source:sync_campaign -->, or <!-- workflow-source:dependabot -->.
• Add a workflow source label such as workflow:source-direct-pr, workflow:source-local-request, workflow:source-review-followup, workflow:source-sync, or workflow:no-automation.

Once a valid source is present, this warning will not be reposted.

[github-actions]

Workflow state fingerprint for Agents Gate Followups. Do not edit.

[github-actions]

Workflow state fingerprint for Agents Verifier. Do not edit.