EXTENSIONS

GitHub pull-request and file-commit operations. Octokit-backed PR creation, merging, and fan-out across repos, plus gh-CLI-backed commitFile (branch creation + single-file commit) and openPullRequest (PR opening from an existing head→base pair) for one-shot file updates without a local checkout or token. dryRun supported on commitFile and openPullRequest.

Dry-run-first GitHub pull request lifecycle methods for agent workflows.

Reconstructs detailed GitHub pull-request feedback threads and bounded diff context for deterministic review and response workflows.

Generate safe, validated browser test plans from GitHub pull requests using a configurable target application and @mgreten/cli-agent.

Build and validate Mere recipes and package the canonical MereLinux recipe delivery workflow. Invokes mere directly without a shell wrapper; installed profile smoke tests compose with @jeremy/mere-shell.

Build and validate the Mere package-manager source tree through fixed, cancellable Zig commands, and package its fresh-branch delivery workflows. Does not download Mere releases, manage a Mere root, build recipes, publish artifacts, or provide credentials.

Narrow GitHub.com same-repository pull-request boundary: preflight, plan, apply, and read-back verification. Draft is requested per packet rather than fixed by the adapter. No merge, release, repository administration, PR update, or arbitrary endpoint capability.

Submit an already-validated Git commit as a draft GitHub pull request using the Graphite CLI, then independently verify with the GitHub CLI that the pull request points at the validated SHA, branch and base and is a draft.

Drift detection and change proposal for GitOps-managed Tailscale ACLs. Extends @john/tailscale-acl with `drift` (compare the live tailnet policy against a policy.hujson file, ignoring comments and key ordering) and `propose` (stage an ACL change as a reviewable pull request, writing HuJSON verbatim so comments survive). Neither method writes to the tailnet — the GitOps pipeline stays the sole writer.

Composition lifecycle for a Graphite (gt) multi-PR stack — validate a declared linear plan, finalize one-commit units, cascade restacks, pin a composed head, and submit gated, idempotent, ordered draft PRs.