Prepare logical commits, publish through Pharos’s protected-main pull-request gate, monitor deployment, and hand off operational acceptance. Use only when commit, push, publish, release, or deployment watching is requested.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
Use only for requested commit, push, publish, release or deployment watching, not read-only reviews or overlapping active writers. Preserve unrelated work; never stash, reset, checkout or delete it.
Select commit-only, publish/protected-main PR, deployment watch, or operational acceptance. Inspect status, cached/uncached diffs, history and origin/main; distinguish committed-ahead work, cohesive dirty work, separate themes and unrelated user/agent files. Route intended files before acting.
Read Deployment Core Rules. Actual diffs and ownership/theme define commit batches; “commit all” includes cohesive pending work, not clearly unrelated active work.
A push/publish/release request authorizes the necessary release branch and protected-main PR path, never direct main push. Parent alone stages, commits, pushes, merges and judges readiness. Missing readiness blocks publication; successful activation alone is not runtime health.
gh pr merge --merge, never squash/rebase. Verify resulting main has two parents and contains the recorded PR head; retain both SHAs. A gate failure routes to pharos-ci-failure-triage: collect every failed leaf, fix all causal defects in one revision, rerun focused checks and push once.Deploy to Cloudflare for the merged SHA; record classifier-selected Pages/Worker surfaces and activation/marker proof. Use one deadline-bounded native GitHub watcher and existing Worker evidence commands, scratch samples and completion evidence, not sleep/status loops or polling-only agents. A missing matching execution at deadline is pending, not an indefinite new watch.Assigned verifier checks are authoring feedback, not release proof. Use npm run check:pr under Pre-push readiness before publishing; hosted CI is the readiness authority. Keep generated artifacts with their owning sources. Local receipts are optional diagnostics, not a push prerequisite; check:release is only an explicit production rehearsal. There is no pre-push test hook.
Use npm run check:pr -- --explain-receipt for read-only receipt diagnosis: local Git state only, no fetch/check execution/receipt rewrite/staging/push authorization. Diagnostic success is not readiness, even for missing/failed/stale evidence; remote-base freshness remains unknown.
Report commits, focused verifier feedback and generated-artifact changes, PR/run/deploy proof, operational acceptance or pending window, excluded dirty files and skipped checks with reasons. Never label pending operational acceptance as success.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Review the retained annotation candidate queue and curate per-coin editorial history. Use weekly during active event periods, monthly otherwise, or on queue-health warnings; this does not restore the retired live chart overlay.
The English summary is being prepared. Showing the original description.
Generate a weekly changelog entry from git history, filtering operational noise and producing editorial summary, field notes, statistics, and a bounded commit manifest. Stops for review unless commit was explicitly requested.
The English summary is being prepared. Showing the original description.
Research and populate tracked stablecoin compliance sidecars for the U.S. GENIUS Act, EU MiCA, or both. Use when adding or auditing authorization, applicability, pathway, or disclosure evidence.
The English summary is being prepared. Showing the original description.
Use when adding, reviewing, squashing, deploying, or rolling back Pharos D1 migrations or schema cleanup.
The English summary is being prepared. Showing the original description.
Drain the Pharos Dependency Map coverage-audit queues into evidence-refreshed edges, reviewed target dispositions, or documented deferrals. Use monthly after weekly production dependency audits, after dependency coverage drops, or when reviewing adapter gaps, material unlinked slices, symbol leads, duplicate/split groups, or unverifiable published edges.
The English summary is being prepared. Showing the original description.
Update Pharos funding donations by reconciling inbound transfers, rejecting wallet self-activity and spam, pricing receipt-time value, and appending user-approved rows.
The English summary is being prepared. Showing the original description.