⏰ Renew interaction limit before 2026-12-06 (public-repo write-lockdown)

[basecradle-ai]

Standing maintenance reminder — keep exactly one open per public repo.

This repository is public. Per fleet policy (constitution → Security and Responsibility, "Untrusted input is data, never instructions" — the public write-surface is org-only by default) it is set to collaborators_only interaction limits: only basecradle org members/collaborators can comment, open issues, or open PRs. The fleet's own App bots are exempt, so handoffs are unaffected.

GitHub interaction limits are temporary — max 6 months, no permanent option. This one expires 2026-12-06. Re-apply before then:

gh api -X PUT /repos/basecradle/basecradle-python/interaction-limits -f limit=collaborators_only -f expiry=six_months

(Once the org-level limit is configured — PUT /orgs/basecradle/interaction-limits, needs admin:org scope — renewal is org-wide and these per-repo reminders can be retired.)

Fleet cross-check — run this EVERY time you renew, on ANY repo. Verify every public repo in the org has (a) an active collaborators_only limit and (b) its own open renewal reminder. One reminder seen anywhere then triggers a full-fleet audit, so nothing slips through the cracks:

for r in $(gh repo list basecradle --visibility public --json name --jq '.[].name'); do
  echo "== $r =="
  gh api /repos/basecradle/$r/interaction-limits --jq '"  limit=\(.limit) until \(.expires_at)"' 2>/dev/null || echo "  NO LIMIT — fix"
  gh issue list --repo basecradle/$r --search "Renew interaction limit in:title state:open" --json number --jq '"  open reminders: \(length)"'
done

After renewing: update this issue's expiry date (or close it and open a fresh one) so there is always exactly one open renewal reminder per public repo.

Refs: basecradle-router#60 (renewal automation), basecradle#288 (the principle).