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.
See how to installReview the instructions the agent will receive before you install.
Read docs/editorial-style.md; its release-note register governs prose. Read Blog Publishing §Changelog and reference.md for the output context and editorial models.
Every entry covers exactly one ISO week: from is a Monday, to is the following Sunday (from + 6 days), both inclusive UTC calendar days. Never write a partial, multi-week, or off-weekday range, and never derive to as “today” on a non-Sunday; check:editorial-content rejects anything else.
Accept an optional ISO week (any date inside the target week) and --commit only when the user authorized a commit. Without week, target the current week when today (UTC) is Sunday, otherwise the most recently completed Monday–Sunday week. If the target week already has an entry, revise that file instead of creating a second one. If one or more complete weeks lie between the newest entry and the target, report the gap and write one entry per missing week.
from and to as inclusive UTC calendar days (derive today in UTC too). Collect newest-first, non-merge commits with eight-character hashes:git log --no-merges --abbrev=8 --since="<from> 00:00:00 +0000" --until="<to> 23:59:59 +0000" --format="%h %s"
[skip ci], documentation-cleanup, and revert-of-revert noise from both analysis and the manifest. Scan subject frequencies first so new dominant automation wording is not mistaken for product work. If more than half is filtered, warn the reviewer.fieldNotes; and a summary item per cluster with a 2–4 word noun label, allowed tag from shared/types/editorial-content.ts, ≤220-character description, and methodology href when applicable.stats.totalCommits to the full filtered count. Store only the newest min(totalCommits, 20) filtered commits, unchanged and newest-first; git history remains the archive.Create src/data/changelogs/<to>.json with the ChangelogEntry shape. Before writing, confirm the Monday–Sunday range, non-overlap with neighbouring entries, field-note length, summary tags/descriptions, headline length, commit hashes, manifest cap, source-backed numbers, and existing methodology routes.
Regenerate rather than hand-edit the barrel and refresh the Markdown fixture:
node --import tsx scripts/maintenance/generate-changelog-registry.ts
npm run check:generated-artifacts -- --only=changelog-registry
npm run check:editorial-content
npm run refresh:markdown-fixtures
npm run typecheck
npm test -- scripts/__tests__/generate-changelog-registry.test.ts
npm test -- scripts/__tests__/generate-markdown-exports.test.ts
Run npm run check:stablecoin-data only when citing registry counts. Default handoff reports the path, headline, field notes, labels/tags, total commits, filtered count, and warnings, then stops for review. If --commit was authorized and checks pass, commit only the entry, generated barrel, and refreshed fixture as one changelog change; use pharos-release-runner for publication.
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.
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.
Draft a short, prioritized questionnaire for a collaborating stablecoin team when public evidence cannot resolve important Pharos data or confidence gaps.
The English summary is being prepared. Showing the original description.