Summary

Replace the dual-context list `["build", "docs-link-check"]` from #11 with `["docs-link-check"]` only.

Why #11 didn't work

#11 was based on a wrong assumption: that `required_status_checks` accepts an OR-list ("any one must pass"). It's actually AND-semantics — every entry has to pass. So after #11 applied:

• docs(todo): track lychee 'No files found' warn from deploy link check jackin#180 has `Docs / build` ✓, no `docs-link-check` ✗ → blocked, missing `docs-link-check`.
• ci(docs): rename build job to docs-link-check for unique status context jackin#181 (rename PR) has `Docs / docs-link-check` ✓, no `build` ✗ → blocked, missing `build`.

A PR's branch only carries one or the other name, so AND-semantics makes the dual-context rule unsatisfiable. `--admin` doesn't help either — the ruleset has `current_user_can_bypass: never` and no `bypass_actors` configured (intentional strict enforcement).

Approach — narrow, then natural cascade

Drop `"build"` and keep only `"docs-link-check"`. After this applies:

1. #181 unblocks immediately — it already has `Docs / docs-link-check` green from CI.
2. Merge #181 — `main` now has the renamed job committed; every future push produces `docs-link-check`.
3. Sync #180 with main — rebase or merge `main` into the PR branch so its CI run produces `docs-link-check` too.
4. Merge #180.

No admin override, no enforcement window where the rule is off, no `bypass_actors` weakening. The rule simply hops to its target context and PRs naturally adapt on rebase.

Apply plan to expect

```
~ resource "github_repository_ruleset" "protect_main" {
~ rules {
~ required_status_checks {
- required_check { context = "build" }
- required_check { context = "docs-link-check" }
+ required_check { context = "docs-link-check" }
}
}
}
Plan: 0 to add, 1 to change, 0 to destroy.
```

(The diff might show both `docs-link-check` entries because Terraform recreates the set; the net effect is one entry remaining.)

Test plan

• `tofu fmt -check` clean.
• `tofu validate` clean.
• Pre-commit secret scan clean.
• After `tofu apply` on your machine: `gh api repos/jackin-project/jackin/rulesets/14746904 --jq '.rules[] | select(.type=="required_status_checks") | .parameters.required_status_checks'` shows only `docs-link-check`.
• ci(docs): rename build job to docs-link-check for unique status context jackin#181 unblocks; merge it.
• docs(todo): track lychee 'No files found' warn from deploy link check jackin#180 rebased to new main, produces `docs-link-check`, merges.

🤖 Generated with Claude Code