Add maintainer loop (orchestrator + triage skills)

[adityash8]

Maintainer Loop — last run 2026-06-21 UTC

Run #95

Landed this run

(nothing)

Needs owner

(nothing)

In flight

(nothing)

Deferred / closed

(nothing)

---

All clear — no open PRs or issues.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
llmx	Error		Jun 16, 2026 6:16am

[gemini-code-assist]

Code Review

This pull request introduces two Claude Code skills (github-project-triage and maintainer-orchestrator) along with a markdown guide to establish an autonomous, cloud-based maintainer loop for the repositories. The loop is designed to triage issues and PRs, auto-merge low-risk changes, escalate complex tasks, and record state in a durable ledger issue. The review feedback correctly points out that the GitHub API does not support a duplicate state reason or a duplicate_of parameter for closing issues, which would cause API errors. The reviewer suggests updating the instructions to close duplicate ledgers with state_reason: not_planned and adding a comment linking to the surviving ledger.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

[gemini-code-assist]

The GitHub REST and GraphQL APIs do not support state_reason: duplicate or a duplicate_of parameter for issues. The only valid values for state_reason when closing an issue are completed and not_planned. Attempting to use duplicate will result in an API error. Please update the instructions to close duplicate ledgers as not_planned and post a comment referencing the canonical ledger issue.

Suggested change

	open ledger, close the rest as duplicates (`state_reason: duplicate` with
	`duplicate_of` set to the survivor), and continue on the survivor. If none exists, create it, ensure the
	open ledger, close the rest as duplicates (close with state_reason: not_planned and
	a comment linking to the survivor), and continue on the survivor. If none exists, create it, ensure the

[gemini-code-assist]

The GitHub REST/GraphQL API does not support state_reason: duplicate or a duplicate_of parameter. To close an issue as a duplicate, it should be closed with state_reason: not_planned and a comment should be posted linking to the canonical ledger issue. Please update this section to reflect the correct API behavior.

Suggested change

	Close duplicate ledgers via the connector/REST API so `state_reason: duplicate`
	(+ `duplicate_of`) sticks — verified working. Note `gh issue close --reason`
	accepts only `completed`/`not_planned`, so if you must use `gh`, close with
	`not_planned` and a comment linking the survivor instead.
	Close duplicate ledgers via the connector/REST API or gh with state_reason: not_planned
	and leave a comment linking to the survivor ledger. Note that the GitHub API does not natively
	support a duplicate state reason or a duplicate_of field.