docs: reconcile public GitHub PR state

[YoneRai12]

Scope

• Reconciles current GitHub PR state after the previous dependency drain.
• Records that gh, GitHub API, and public pull-list HTML all show 43 open PRs.
• Explains that the count increased because new security/runtime PRs fix(core): bound surface run result memory growth #204 through fix: prevent yonerai CLI crash on malformed --api-origin #213 were opened after PR docs: Web依存PRの終了結果を記録 #203.
• Records current fix(core): restore require_core_access on main v1 routers #142, docs: update security PR backlog triage #195, and docs: Web依存PRの終了結果を記録 #203 state.
• Adds docs/maintenance/PUBLIC_GITHUB_STATE_RECONCILIATION_2026_05_21.md.

Validation

• git diff --check passed.
• Changed-file secret scan: no secret values found; token hits are existing explanatory wording only.
• Changed-file local path / username / hostname scan: no hits.
• Changed-file hidden Unicode scan: no hits.
• Changed-file mojibake scan: no four-question-mark sequence and no replacement characters.
• src/cogs/ora.py: unchanged.
• reference_clawdbot: untouched.

Non-claims

This does not claim production readiness, shipping completion, official cloud completion, hybrid completion, full security backlog completion, full dependency backlog completion, persistent memory, Google login, Discord gateway completion, Tools/MCP completion, provider ecosystem completion, or src/cogs/ora.py resolution.

Traceability

• Prior merged PRs referenced: docs: clean public PR text hygiene #197, docs: reconcile PR backlog state #198, docs: standardize release note style #199, docs: add public file index #200, docs: inventory large codebase features #201, docs: 依存PRトリアージを更新 #202, docs: Web依存PRの終了結果を記録 #203.
• New incoming open PR range observed: fix(core): bound surface run result memory growth #204-fix: prevent yonerai CLI crash on malformed --api-origin #213.

[gemini-code-assist]

Code Review

This pull request introduces a new maintenance document for public GitHub state reconciliation and updates the existing triage documentation. The review identified potential issues with the gh pr list and gh api commands, noting that the current limit of 100 may lead to inaccurate pull request counts as the backlog grows. Increasing these limits to 1000 is recommended to ensure accuracy.

[gemini-code-assist]

The --limit 100 flag in the gh pr list command will cause an incorrect count if the number of open pull requests exceeds 100. Consider increasing this limit to a higher value (e.g., 1000) to ensure the count remains accurate as the backlog grows.

Suggested change

	- GitHub source of truth: `gh pr list --state open --limit 100 --json number --jq length`
	- gh pr list --state open --limit 1000 --json number --jq length

[gemini-code-assist]

The --limit 100 flag in the gh pr list command will cause an incorrect count if the number of open pull requests exceeds 100. Consider increasing this limit to a higher value (e.g., 1000) to ensure the count remains accurate as the backlog grows.

Suggested change

	- `gh pr list --state open --limit 100 --json number --jq length`: `43`
	- gh pr list --state open --limit 1000 --json number --jq length: 43

[gemini-code-assist]

The gh api command using per_page=100 only returns the first page of results, which will lead to an incorrect count if there are more than 100 open pull requests. It is recommended to use gh pr list with a sufficiently high limit, as done in the previous line, for a more robust count.

Suggested change

	- `gh api "/repos/YoneRai12/YonerAI/pulls?state=open&per_page=100" --jq length`: `43`
	- gh pr list --state open --limit 1000 --json number --jq length: 43