pipeline: autonomous operation — shortlist stage, auto modes, daily-pipeline orchestrator

- daily-finds: feed-first fetch strategy (fetch: feed + feedUrl), cadence-aware
  scanning, new score-and-shortlist stage (shortlist: true, up to 12/day, top
  1-3 flagged as review candidates), Amazon affiliate lookup for shortlisted
  physical products, and authority to apply mechanical sources.json maintenance
  (skip dead sources, demote dormant ones, record working fetch paths) instead
  of logging recommendations nobody executes.
- build-bundle: auto mode (no confirmation gate when unattended) and a 'weekly'
  date-based catch mode so shortlisted finds never sit invisible for weeks.
- cluster-bundles: auto mode.
- build-review: hero.ts registration step removed (heroes auto-discovered from
  hero.<ext>); mandatory fact-check against the product's own site in auto
  mode; amazonLink carry-through; auto mode publishes and logs instead of
  pausing twice for approval.
- New daily-pipeline skill: capture → bundle → reviews → pick of the day →
  build → commit → push → digest, with granular per-stage commits. This is the
  entrypoint for scheduled runs.
- Project CLAUDE.md documenting the pipeline and its foot-gun conventions.

.claude/skills/cluster-bundles/SKILL.md

@@ -43,7 +43,9 @@ When choosing which items to repeat: only repeat a find when the second theme ge
 
 ### 4. Confirm with the user
 
-Before writing any files, show a compact plan:
+**Autonomous mode** (`auto` argument, or running unattended — e.g. via `/daily-pipeline` or a scheduled/headless session): skip the confirmation; hold yourself to the same bar, write the bundles, and record the full plan (clusters, overlaps, uncovered finds) in the log entry so the user can review and veto afterwards. When torn between a bold theme and a safe one, take the safe one.
+
+Otherwise, before writing any files, show a compact plan:
 
 ```
 Cluster A — "<theme>" (N items)