pharos-watch

Diagnose and fix failed Pharos GitHub Actions, merge-gate, deploy-cloudflare, pages-release, or rebuild-pages runs. Use when a workflow failed, a push/merge gate fails, or the user asks to retrigger and iterate until CI/deploy clears.

Run the standard Pharos release path when asked to commit in logical/thematic batches, publish through the protected main pull-request gate, or watch the production deployment. Use for release prep, final publish, deployment monitoring, and production handoff after local work is complete.

Generate a weekly changelog entry from git history. Collects commits for a date range, filters noise, clusters by theme, writes an editorial summary, and outputs a ChangelogEntry file. Default behavior stops for review; pass --commit to also commit.

Audit and repair Pharos documentation against the codebase. Use for documentation update passes, verified-doc drift, source-path/doc-sync failures, methodology/doc routing updates, or requests to verify docs without trusting existing prose.

Coordinate the full Pharos stablecoin addition process from eligibility through validation. Use when adding a new tracked stablecoin, promoting a pre-launch asset, or auditing whether an addition is complete.

Drain the Pharos Yield Intelligence coverage-audit queue into reviewed source coverage, documented intentional gaps, or watchlisted deferrals. Use monthly after `yield-coverage-audit` runs, after yield coverage drops, or when promoting queue candidates such as `native-exact-pool`, `lending-allowlist`, `source-family-adapter`, `stale-auto-lending-override`, or `quarantine-ready-to-restore`.

Use when asked to update pre-launch stablecoin data, add milestones, refresh launch phases, or check for promotions. Runs weekly to keep the upcoming stablecoins module current.

Verify `geckoId` values for tracked stablecoins in the Pharos stablecoin dashboard by cross-checking `shared/data/stablecoins/coins/*.json` against DefiLlama metadata and CoinGecko contract-address resolution. Use when adding a stablecoin, auditing price mismatches, or investigating missing or incorrect CoinGecko prices.

Verify and populate one tracked stablecoin's metadata (collateral, peg mechanism, jurisdiction, links, geckoId, contracts, proofOfReserves) in `shared/data/stablecoins/coins/*.json`. Use when adding a coin, filling metadata gaps, or auditing one coin's entry.

Write, update, or refresh AI editorial summaries for stablecoin detail pages, including draining the queue from `npm run candidates:ai-summaries` after scoring changes or on a monthly cadence.

Drain the annotation-candidates queue (from `npm run candidates:annotations`) into shared/data/annotations/curated-annotations.ts. Use weekly during active event periods, monthly otherwise.

Discover missing stablecoin deployments in the Pharos dashboard by comparing DefiLlama chain-level supply data against entries in `shared/data/stablecoins/coins/*.json`, then populate verified contracts via CoinGecko and explorer checks. Use when auditing chain coverage, backfilling missing deployments, or batch-enriching tracked stablecoins.

Populate missing `contracts` entries for a tracked stablecoin in the Pharos dashboard from CoinGecko `detail_platforms` data while preserving curated addresses and using only chain IDs already present in `shared/lib/chains/index.ts`. Use when adding a stablecoin or filling known chain gaps in `shared/data/stablecoins/coins/*.json`.

Use when asked to update Pharos funding donations data, or on a ~weekly cadence to keep /funding current. Researches inbound transfers to the funding wallet across supported chains, resolves ENS, and appends rows to shared/data/funding/donations.json with user approval.

Add explicit resilience overrides (`chainTier`, `deploymentModel`, `collateralQuality`, `custodyModel`) where `inferResilienceDefaults()` is too optimistic. Use when adding a stablecoin or auditing report-card accuracy.

Research and populate the `genius` (U.S. GENIUS Act compliance) field for a tracked stablecoin. Use when adding or auditing GENIUS status, pathway, or disclosures in `shared/data/stablecoins/coins/*.json`.

Research and populate EU MiCA compliance data (the `mica` field) for a tracked stablecoin in the Pharos dashboard. Use when adding or auditing MiCA authorization status, token type, competent authority, or issuer authorization in `shared/data/stablecoins/coins/*.json`.

Generate a weekly changelog entry from git history. Collects commits for a date range, filters noise, clusters by theme, writes an editorial summary, and outputs a ChangelogEntry file. Default behavior stops for review; pass --commit to also commit.

Use when asked to update Pharos funding donations data, or on a ~weekly cadence to keep /funding current. Researches inbound transfers to the funding wallet across supported chains, resolves ENS, and appends rows to shared/data/funding/donations.json with user approval.

Use when asked to update pre-launch stablecoin data, add milestones, refresh launch phases, or check for promotions. Runs weekly to keep the upcoming stablecoins module current.

Use when asked to write, update, or add AI editorial summaries for stablecoin detail pages. Also use when a new stablecoin is added to the tracked list and needs a summary, or when existing summaries need refreshing.

Research and populate U.S. GENIUS Act compliance data (the `genius` field) for a tracked stablecoin. Use when adding or auditing GENIUS applicability, authorization status, issuer pathway, regulator fields, enforcement/foreign-exception posture, or reserve/redemption disclosure in `shared/data/stablecoins/coins/*.json`.

Discover missing chain deployments using DefiLlama supply data, then populate contract addresses via CoinGecko + block explorer verification. Run across all tracked stablecoins or a subset.

Populate smart contract addresses for a stablecoin using CoinGecko detail_platforms data. Uses only chain IDs already present in CHAIN_META and merges without overwriting existing curated data. Run per-coin or batch.

Research and populate reserve composition data for a single stablecoin. Use when asked to add reserves data for a specific coin, or when batch-populating reserve compositions.

Research and classify stablecoins for resilience sub-factor overrides (chainTier, deploymentModel, collateralQuality, custodyModel). Run after types/defaults are implemented to identify coins needing explicit overrides.

Use when asked to verify, populate, or audit a single tracked stablecoin's detail fields (collateral, peg mechanism, jurisdiction, links, geckoId, contracts, proof of reserves, or Mint Authority review context). Run per-coin to fill gaps or validate existing data in `shared/data/stablecoins/coins/*.json`.

Research and populate `reserves` data for a tracked stablecoin in the Pharos dashboard. Use when adding or auditing reserve composition in `shared/data/stablecoins/coins/*.json`, especially for report-card quality, dependency-risk linking, or reserve-based resilience scoring.

Research and populate EU MiCA compliance data (the `mica` field) for a tracked stablecoin. Use when adding or auditing MiCA authorization status, token type, competent authority, or issuer authorization in `shared/data/stablecoins/coins/*.json`.

Verify CoinGecko IDs for tracked stablecoins by cross-referencing our geckoId config against DefiLlama's geckoId and CoinGecko's contract-address lookup. Use when adding new stablecoins, auditing price data accuracy, or investigating missing/wrong prices.

Coordinate the full Pharos stablecoin addition process from eligibility through validation. Use when adding a new tracked stablecoin, promoting a pre-launch asset, or auditing whether an addition is complete.

Prove that a proposed active stablecoin can enter Pharos runtime data with both a fetchable price and a fetchable market-cap/circulating-supply path. Use before active additions and pre-launch promotions.