@buildinternet/releases-skills 0.51.0 → 0.53.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@buildinternet/releases-skills",
-  "version": "0.51.0",
+  "version": "0.53.0",
   "description": "Agent skills bundled with the Releases CLI. Markdown playbooks for changelog ingest, discovery, and analysis.",
   "type": "module",
   "license": "MIT",

package/skills/releases-cli/references/admin.md

@@ -49,6 +49,17 @@ releases admin source create "Claude Code" --url https://docs.anthropic.com/en/c
   --feed-url https://docs.anthropic.com/en/changelog/rss.xml
 ```
 
+Set source metadata **at create time** with `--keyword-allow` (feed keyword filter → `metadata.feedKeywordAllow`) or the general `--metadata-set key=value` (repeatable; same coercion as `source update --metadata-set`):
+
+```bash
+releases admin source create "Discord" --url https://discord.com/blog --type feed \
+  --feed-url https://discord.com/blog/rss.xml --keyword-allow changelog,patch-notes
+releases admin source create "Acme" --url https://acme.dev/changelog \
+  --metadata-set marketingFilter=true --metadata-set feedContentDepth=summary-only
+```
+
+Do this rather than a follow-up `source update --metadata-set`: `create` triggers the onboard workflow's auto-fetch, which reads the source's metadata **before** any post-create edit lands. Setting a feed filter on create keeps that first ingest filtered; setting it afterward races the auto-fetch and ingests the whole unfiltered feed.
+
 Evaluate without adding:
 
 ```bash
@@ -117,6 +128,47 @@ Notes:
 - Remote concurrency defaults to 3, capped at 5. Duplicate source fetches are detected and blocked.
 - Smart fetch backoff: sources returning no changes back off exponentially (1h → 48h); error backoff caps at 72h.
 
+### Backfill (full history)
+
+Walk every scrape window of a windowed `scrape` source and upsert the whole history at once — the turnkey replacement for bespoke per-source backfill scripts. Idempotent (dedups by synthesized URL), and **dry-run by default**:
+
+```bash
+releases admin source backfill my-source                    # preview: counts + date range, nothing written
+releases admin source backfill my-source --no-dry-run        # write (or --commit)
+releases admin source backfill my-source --max-windows 100   # walk further back (endpoint clamps 1–200, default 50)
+releases admin source backfill my-source --wait              # deep Firecrawl backfill: block until the async workflow finishes
+releases admin source backfill my-source --markdown-file page.md --commit
+cat page.md | releases admin source backfill my-source --markdown-file - --commit
+```
+
+Notes:
+
+- Accepts a slug or `src_…` ID; the CLI resolves to the typed ID before calling (the endpoint rejects bare slugs as ambiguous across orgs).
+- `--markdown-file` supplies the full-page markdown for JS-heavy / bot-blocked sources the worker can't fetch itself. Without it the endpoint falls back to Firecrawl (if enabled on the source) then a plain fetch.
+- Scrape sources only. Non-scrape sources, an unfetchable body, or a missing `ANTHROPIC_API_KEY`/`FIRECRAWL_API_KEY` come back as a clear error.
+- A dry run reports `windows`, `extracted → unique`, and the date range; it warns if it hit the window cap (raise `--max-windows`).
+- Deep Firecrawl backfills run as a durable workflow (minutes). Like `admin overview batch`, the CLI **dispatches and returns the workflow instance ID by default** (non-blocking — the agent-friendly default), then either:
+  - poll it yourself: `releases admin source backfill-status <instanceId> [--json]` (single-shot; loop on the `--json` `status` field), or
+  - pass `--wait` to block and render the report inline.
+- Non-Firecrawl / `--markdown-file` sources stay **synchronous** — the report comes back in one call regardless of `--wait`.
+
+### Re-extract (from a stored snapshot)
+
+Re-run extraction over a source's captured raw body in R2 (`released-raw`) — **no live scrape, no Firecrawl credits, deterministic input**. Use it after extraction/parse logic improves to reprocess a source's history. Sibling of `backfill`, **dry-run by default**:
+
+```bash
+releases admin source reextract my-source                          # preview from the latest snapshot
+releases admin source reextract my-source --commit                 # write (or --no-dry-run)
+releases admin source reextract my-source --snapshot-id raw_abc123 --commit   # pin a specific capture
+releases admin source reextract my-source --max-windows 100 --json
+```
+
+Notes:
+
+- Slug or `src_…` ID, resolved to the typed ID before calling (bare slugs rejected). Scrape sources only.
+- Omitting `--snapshot-id` uses the most recent capture; the report's `snapshot` block names which one was used.
+- Actionable errors surface as-is: `no_snapshot`/`snapshot_not_found` (404, none stored / wrong id), `snapshot_expired` (410, body past the 90-day R2 lifecycle — re-scrape to capture fresh), missing `RAW_SNAPSHOTS`/`ANTHROPIC_API_KEY` (503).
+
 ### Poll (cheap change detection)
 
 ```bash
@@ -153,10 +205,14 @@ releases admin org update vercel --category developer-tools
 releases admin org link vercel --platform github --handle vercel
 releases admin org tag add vercel react serverless
 releases admin org alias add anthropic claude.ai claude.com
-releases admin org refresh vercel                         # fetch all sources + regenerate overview
+releases admin source fetch --org vercel                  # fetch all of an org's active sources
+releases admin org delete vercel                          # reversible tombstone soft-delete
+releases admin org delete vercel --hard --yes             # permanent purge + FK cascade
 ```
 
-`org refresh` flags: `--max <n>` (per-source cap, default 20), `--concurrency <n>`, `--window <days>`, `--dry-run`, `--skip-overview`, `--json`.
+There is no `org refresh` command. To refresh an org: fetch its sources with `releases admin source fetch --org <slug>` (see **Fetch** above), then regenerate the overview with the `overview` subcommands — `releases admin overview inputs <slug>` → generate the body → `releases admin overview update <slug>` (or `releases admin overview batch` for a server-side sweep). Overview generation is agent-driven; no single command does both.
+
+`org delete` soft-deletes by default (a reversible tombstone). `--hard` purges the row and cascade-deletes every dependent source, release, fetch-log, changelog file/chunk, summary, media asset, and webhook subscription; it prompts for a slug typeback unless `--yes` is passed (required in non-TTY/scripted contexts). You can pass a slug or an `org_…` ID either way — the CLI resolves to the typed ID the destructive path requires.
 
 ## Products
 
@@ -167,6 +223,8 @@ releases admin product create "Next.js" --org vercel --url https://nextjs.org
 releases admin product create "Stripe Node" --org stripe --kind sdk
 releases admin product list vercel
 releases admin product list openai --kind sdk           # filter by taxonomy
+releases admin product list                             # every product, all orgs (adds an Org column)
+releases admin product list --kind sdk --json           # cross-org kind audit (CLI↔MCP list_catalog parity)
 releases admin product update nextjs --description "React framework for production"
 releases admin product update stripe-node --kind sdk    # classify
 releases admin product update stripe-node --no-kind     # clear