From 76d1f752d237600981666a793092526b37b5877a Mon Sep 17 00:00:00 2001
From: DJ <dj@Rachels-Air.localdomain>
Date: Thu, 16 Apr 2026 10:56:16 -0700
Subject: [PATCH 01/13] feat(feature-ideation): per-repo source list + feed
 checkpoint via last successful run
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Source list (addresses all Copilot/CodeRabbit/don-petry review threads):
- Add standards/feature-ideation-sources.md as a starter template; each
  adopting repo copies it to .github/feature-ideation-sources.md and owns
  it independently (no cross-repo checkout).
- Add sources_file input to the reusable workflow (default:
  .github/feature-ideation-sources.md). Phase 2 prompt reads the repo-
  local file; falls back to open web search if absent.
- Fix three arXiv RSS feed URLs from http:// to https://.
- Update propagation wording in ci-standards.md to reflect per-repo
  ownership and v1 tag model.
- Pin caller stub reusable ref from mutable @v1 to commit SHA ae9709f # v1.
- Add actions: read to gather-signals permissions and caller stub template
  (required for gh run list in same repo).

Feed checkpoint (new — avoids re-reviewing same content every week):
- collect-signals.sh: query gh run list --status=success --limit=1 to
  resolve the previous successful run timestamp; fall back to 30 days ago
  on first run or after a long outage.
- compose-signals.sh: add last_successful_run as arg 10 (schema_version
  shifts to arg 11, truncation_warnings to arg 12).
- signals.schema.json: add last_successful_run field; bump schema version
  1.0.0 → 1.1.0 (SCHEMA_VERSION constant updated in lockstep per bats test).
- Test fixtures (populated, empty-repo, truncated): add last_successful_run
  and bump schema_version to 1.1.0.
- Phase 2 prompt: instruct Mary to filter feed entries to those published
  after last_successful_run; bypass checkpoint if >60 days old.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
---
 .github/schemas/signals.schema.json           |   8 +-
 .../feature-ideation/collect-signals.sh       |  27 ++-
 .../feature-ideation/lib/compose-signals.sh   |  16 +-
 .../workflows/feature-ideation-reusable.yml   |  61 +++++-
 standards/ci-standards.md                     |  25 ++-
 standards/feature-ideation-sources.md         | 174 ++++++++++++++++++
 standards/workflows/feature-ideation.yml      |  32 +++-
 .../fixtures/expected/empty-repo.signals.json |   3 +-
 .../fixtures/expected/populated.signals.json  |   3 +-
 .../fixtures/expected/truncated.signals.json  |   3 +-
 10 files changed, 326 insertions(+), 26 deletions(-)
 create mode 100644 standards/feature-ideation-sources.md

diff --git a/.github/schemas/signals.schema.json b/.github/schemas/signals.schema.json
index ded4367..1130cf2 100644
--- a/.github/schemas/signals.schema.json
+++ b/.github/schemas/signals.schema.json
@@ -1,13 +1,14 @@
 {
   "$schema": "https://json-schema.org/draft/2020-12/schema",
   "$id": "https://github.com/petry-projects/.github/blob/main/.github/schemas/signals.schema.json",
-  "$comment": "version: 1.0.0 — must match SCHEMA_VERSION in collect-signals.sh; enforced by bats",
+  "$comment": "version: 1.1.0 — must match SCHEMA_VERSION in collect-signals.sh; enforced by bats",
   "title": "Feature Ideation Signals",
   "description": "Canonical contract between collect-signals.sh and the BMAD Analyst (Mary) prompt. Any change to this schema is a breaking change to the workflow.",
   "type": "object",
   "required": [
     "schema_version",
     "scan_date",
+    "last_successful_run",
     "repo",
     "open_issues",
     "closed_issues_30d",
@@ -28,6 +29,11 @@
       "type": "string",
       "format": "date-time"
     },
+    "last_successful_run": {
+      "description": "ISO-8601 timestamp of the previous successful workflow run; used as a feed checkpoint by the analyst to skip already-reviewed content.",
+      "type": "string",
+      "format": "date-time"
+    },
     "repo": {
       "type": "string",
       "pattern": "^[^/]+/[^/]+$"
diff --git a/.github/scripts/feature-ideation/collect-signals.sh b/.github/scripts/feature-ideation/collect-signals.sh
index fd3b1b3..2051ba5 100755
--- a/.github/scripts/feature-ideation/collect-signals.sh
+++ b/.github/scripts/feature-ideation/collect-signals.sh
@@ -31,7 +31,7 @@ set -euo pipefail
 # if the constants drift, AND the bats `signals-schema: SCHEMA_VERSION
 # constant matches schema file` test enforces this in CI.
 # Caught by CodeRabbit review on PR petry-projects/.github#85.
-SCHEMA_VERSION="1.0.0"
+SCHEMA_VERSION="1.1.0"
 
 SCRIPT_DIR="$(cd -- "$(dirname -- "${BASH_SOURCE[0]}")" && pwd)"
 # shellcheck source=lib/gh-safe.sh
@@ -71,6 +71,29 @@ main() {
   local scan_date
   scan_date=$(date_now_iso)
 
+  # --- Feed checkpoint: last successful run ----------------------------------
+  # Used by the analyst to skip feed entries already reviewed. The current run
+  # is still in-progress, so --status=success --limit=1 reliably returns the
+  # previous successful run. Falls back to 30 days ago on first-ever run or
+  # after a long gap so the initial scan is bounded.
+  printf '[collect-signals] resolving feed checkpoint (last successful run)\n' >&2
+  local last_successful_run
+  last_successful_run=$(gh run list \
+    --repo "$REPO" \
+    --workflow="feature-ideation.yml" \
+    --status=success \
+    --limit=1 \
+    --json createdAt \
+    --jq '.[0].createdAt // empty' \
+    2>/dev/null || true)
+  if [ -z "$last_successful_run" ] || [ "$last_successful_run" = "null" ]; then
+    last_successful_run=$(date_days_ago 30)
+    printf '[collect-signals] no prior successful run found; using 30-day fallback: %s\n' \
+      "$last_successful_run" >&2
+  else
+    printf '[collect-signals] feed checkpoint: %s\n' "$last_successful_run" >&2
+  fi
+
   local truncation_warnings='[]'
 
   # --- Open issues -----------------------------------------------------------
@@ -201,6 +224,7 @@ GRAPHQL
     "$bug_reports" \
     "$REPO" \
     "$scan_date" \
+    "$last_successful_run" \
     "$SCHEMA_VERSION" \
     "$truncation_warnings")
 
@@ -217,6 +241,7 @@ GRAPHQL
       printf -- '- **Bug reports:** %s\n' "$(jq '.bug_reports.count' "$output_path")"
       printf -- '- **Merged PRs (30d):** %s\n' "$(jq '.merged_prs_30d.count' "$output_path")"
       printf -- '- **Existing Ideas discussions:** %s\n' "$(jq '.ideas_discussions.count' "$output_path")"
+      printf -- '- **Feed checkpoint (last successful run):** %s\n' "$(jq -r '.last_successful_run' "$output_path")"
       local warn_count
       warn_count=$(jq '.truncation_warnings | length' "$output_path")
       if [ "$warn_count" -gt 0 ]; then
diff --git a/.github/scripts/feature-ideation/lib/compose-signals.sh b/.github/scripts/feature-ideation/lib/compose-signals.sh
index 6a0f5bd..1afd8e7 100755
--- a/.github/scripts/feature-ideation/lib/compose-signals.sh
+++ b/.github/scripts/feature-ideation/lib/compose-signals.sh
@@ -18,16 +18,17 @@
 #   $7  bug_reports
 #   $8  repo (string, e.g. "petry-projects/talkterm")
 #   $9  scan_date (ISO-8601 string)
-#  $10  schema_version (string)
-#  $11  truncation_warnings (JSON array, may be [])
+#  $10  last_successful_run (ISO-8601 string; feed checkpoint)
+#  $11  schema_version (string)
+#  $12  truncation_warnings (JSON array, may be [])
 #
 # Output: signals.json document on stdout.
 
 set -euo pipefail
 
 compose_signals() {
-  if [ "$#" -ne 11 ]; then
-    printf '[compose-signals] expected 11 args, got %d\n' "$#" >&2
+  if [ "$#" -ne 12 ]; then
+    printf '[compose-signals] expected 12 args, got %d\n' "$#" >&2
     return 64  # EX_USAGE
   fi
 
@@ -40,8 +41,9 @@ compose_signals() {
   local bug_reports="$7"
   local repo="$8"
   local scan_date="$9"
-  local schema_version="${10}"
-  local truncation_warnings="${11}"
+  local last_successful_run="${10}"
+  local schema_version="${11}"
+  local truncation_warnings="${12}"
 
   # Validate every JSON input before composition. Better to fail loudly here
   # than to let `jq --argjson` produce a cryptic parse error.
@@ -57,6 +59,7 @@ compose_signals() {
 
   jq -n \
     --arg scan_date "$scan_date" \
+    --arg last_successful_run "$last_successful_run" \
     --arg repo "$repo" \
     --arg schema_version "$schema_version" \
     --argjson open_issues "$open_issues" \
@@ -70,6 +73,7 @@ compose_signals() {
     '{
       schema_version: $schema_version,
       scan_date: $scan_date,
+      last_successful_run: $last_successful_run,
       repo: $repo,
       open_issues: { count: ($open_issues | length), items: $open_issues },
       closed_issues_30d: { count: ($closed_issues | length), items: $closed_issues },
diff --git a/.github/workflows/feature-ideation-reusable.yml b/.github/workflows/feature-ideation-reusable.yml
index 23c7cc9..06a860e 100644
--- a/.github/workflows/feature-ideation-reusable.yml
+++ b/.github/workflows/feature-ideation-reusable.yml
@@ -76,6 +76,16 @@ on:
         required: false
         default: 'v1'
         type: string
+      sources_file:
+        description: |
+          Path (relative to repo root) of the repo-local reputable source list.
+          Defaults to .github/feature-ideation-sources.md. Copy
+          standards/feature-ideation-sources.md from petry-projects/.github as
+          a starting point and customise it for your project. If the file is
+          absent Mary falls back to open web search automatically.
+        required: false
+        default: '.github/feature-ideation-sources.md'
+        type: string
     secrets:
       CLAUDE_CODE_OAUTH_TOKEN:
         description: 'Claude Code OAuth token (org-level secret)'
@@ -94,6 +104,7 @@ jobs:
       issues: read
       pull-requests: read
       discussions: read
+      actions: read
     env:
       GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
     steps:
@@ -295,8 +306,54 @@ jobs:
             **Adopt the "Market Research" mindset.** Your sole job in this phase is to gather
             hard evidence — not to generate ideas yet. Be a detective, not a brainstormer.
 
-            Using the **Project Context** above as your starting point, research the
-            competitive landscape and emerging trends. Cover at minimum:
+            ### Start from the repo-local Reputable Source List
+
+            Before running open-ended web searches, **check for a repo-local source list**:
+
+            ```
+            Read: ${{ inputs.sources_file }}
+            ```
+
+            That file (if present) lists vendor blogs, RSS feeds, podcasts, and YouTube
+            channels this repo's maintainers trust as primary signal sources, organised
+            by category. Treat it as your **starting set**:
+
+            - Pick the categories most relevant to the **Project Context** above. A
+              CLI dev tool warrants different sources than a security scanner or a
+              data pipeline.
+            - For each relevant source, do a targeted `WebFetch` or `WebSearch`
+              scoped to that domain to find what's new. Prefer fetching the listed
+              RSS/Atom feed URL when one is given — it gives you structured "what
+              changed" data without scraping HTML.
+            - The list is a **floor, not a ceiling.** If a thread takes you to a
+              source not in the list and that source is reputable, follow it. After
+              the run, if a high-value source kept coming up but wasn't listed,
+              **mention it in the step summary** under a "Suggested additions to
+              source list" heading so a human can PR it in.
+            - If the file is missing or empty, log a warning to the step summary
+              and proceed with open web search — do not fail the run.
+
+            ### Use the feed checkpoint to avoid re-reviewing old content
+
+            `$SIGNALS_PATH` contains a `last_successful_run` ISO-8601 timestamp — the
+            date/time the previous successful run of this workflow completed.
+
+            **When fetching any RSS/Atom feed or scraping a changelog/blog:**
+            - Only consider entries whose `pubDate` / `updated` / `published` field
+              is **after** `last_successful_run`.
+            - If a feed does not expose dates, or if all entries predate the checkpoint,
+              note that in your research log and move on — do not re-summarise content
+              you have no evidence is new.
+            - If `last_successful_run` is more than 60 days in the past (e.g. after a
+              long workflow outage), ignore the checkpoint and process the full feed to
+              avoid missing major developments.
+
+            This keeps each weekly run focused on genuinely new signal rather than
+            re-processing the same content at Opus 4.6 cost.
+
+            Using the **Project Context** above as your starting point and the
+            source list as your seed, research the competitive landscape and
+            emerging trends. Cover at minimum:
 
             ### Competitive Landscape
             - What are competitors in this space shipping recently?
diff --git a/standards/ci-standards.md b/standards/ci-standards.md
index 6f2d7b5..edbb046 100644
--- a/standards/ci-standards.md
+++ b/standards/ci-standards.md
@@ -475,8 +475,21 @@ split into two parts:
    Defines the schedule, the `workflow_dispatch` inputs, and calls the
    reusable workflow with a single required parameter: `project_context`.
 
+3. **Reputable Source List** (repo-local, per-repo):
+   Each adopting repo maintains its own copy at `.github/feature-ideation-sources.md`
+   (or the path passed via the `sources_file` workflow input).
+   Use [`standards/feature-ideation-sources.md`](feature-ideation-sources.md)
+   as a starter template, then customise it for your project. The Phase 2 prompt
+   instructs Mary to read that file as her **starting set** for market research —
+   vendor blogs, RSS feeds, podcasts, and YouTube channels organised by category.
+   If the file is absent Mary falls back to open web search automatically.
+   Each repo owns its own copy; add or remove entries via PR in that repo.
+
 When we tune the prompt, the model, or the gotchas, we change one file in
-this repo and every adopter picks up the change on their next scheduled run.
+this repo. Repos tracking `@main` pick up the change on their next scheduled
+run; repos pinned to `@v1` pick it up only after the `v1` tag is updated and
+then on their next scheduled run. The source list is repo-local and propagates
+only within the repo that owns it.
 
 #### Adopting in a new repo
 
@@ -485,11 +498,15 @@ this repo and every adopter picks up the change on their next scheduled run.
 2. Replace the `project_context` value with a 3-5 sentence description of
    what the project is, who it serves, and the competitive landscape Mary
    should research. This is the **only** required edit.
-3. (Optional) Adjust the cron schedule, focus area choices, or pin to a
+3. (Optional) Copy [`standards/feature-ideation-sources.md`](feature-ideation-sources.md)
+   to `.github/feature-ideation-sources.md` in the target repo and customise
+   it for your project. Mary reads YOUR copy — not the central template — so
+   each repo controls its own source list.
+4. (Optional) Adjust the cron schedule, focus area choices, or pin to a
    tag instead of `@main` if you want change isolation.
-4. Ensure GitHub Discussions is enabled with an "Ideas" category — see
+5. Ensure GitHub Discussions is enabled with an "Ideas" category — see
    [Discussions Configuration](github-settings.md#discussions-configuration).
-5. Confirm the org-level secret `CLAUDE_CODE_OAUTH_TOKEN` is accessible.
+6. Confirm the org-level secret `CLAUDE_CODE_OAUTH_TOKEN` is accessible.
 
 #### Critical gotchas (baked into the reusable workflow)
 
diff --git a/standards/feature-ideation-sources.md b/standards/feature-ideation-sources.md
new file mode 100644
index 0000000..1165e2a
--- /dev/null
+++ b/standards/feature-ideation-sources.md
@@ -0,0 +1,174 @@
+# Feature Ideation — Reputable Source List
+
+> **Purpose:** A starter list of reputable web pages, RSS feeds, podcasts,
+> and YouTube channels that the BMAD Analyst (Mary) consults during
+> **Phase 2: Market Research** of the
+> [Feature Ideation workflow](../.github/workflows/feature-ideation-reusable.yml).
+>
+> **How it is used:** This file is a **template**. Each adopting repo copies
+> it to `.github/feature-ideation-sources.md` (or the path configured via
+> the `sources_file` workflow input) and customises it for their project.
+> The reusable workflow reads the repo-local copy — it does **not** read
+> this file directly. Mary treats the local list as her starting set for
+> web research, supplementing it with targeted searches as needed.
+>
+> **Curation rules:**
+>
+> - Only sources with a track record of accurate, technically-grounded
+>   content. No SEO farms, no anonymous aggregators with no editorial
+>   standards.
+> - Prefer **primary sources** (vendor changelogs, research labs, official
+>   blogs) over secondary commentary.
+> - RSS / Atom feed URLs are listed where available — they let Mary fetch
+>   structured "what is new since last scan" data instead of scraping HTML.
+> - YouTube and podcast feeds are included because release announcements,
+>   conference talks, and engineering deep-dives often appear there before
+>   (or instead of) blog posts.
+> - Every entry has a one-line note explaining **why it is on this list** —
+>   if you cannot justify it in one line, it should not be here.
+>
+> **Maintenance:** Each repo owns its own copy — add or remove entries via
+> PR in that repo. To update the shared starter template, open a PR here;
+> existing repos with their own copy will not be affected automatically.
+
+---
+
+## 1. AI / ML — Vendor & Lab Primary Sources
+
+Release notes, model launches, capability changes. These are usually the
+**first** place a new feature surfaces, weeks before commentary catches up.
+
+| Source | URL | Feed | Why it's here |
+|--------|-----|------|---------------|
+| Anthropic News | <https://www.anthropic.com/news> | <https://www.anthropic.com/rss.xml> | Model releases, safety research, API changes |
+| OpenAI Blog | <https://openai.com/blog> | <https://openai.com/blog/rss.xml> | Model releases, API updates, research |
+| Google DeepMind Blog | <https://deepmind.google/discover/blog/> | — | Research breakthroughs, Gemini updates |
+| Google AI Blog | <https://ai.googleblog.com/> | <https://ai.googleblog.com/feeds/posts/default> | Applied AI research and product updates |
+| Meta AI Blog | <https://ai.meta.com/blog/> | — | LLaMA releases, research |
+| Mistral Blog | <https://mistral.ai/news/> | — | Open-weight model releases |
+| HuggingFace Blog | <https://huggingface.co/blog> | <https://huggingface.co/blog/feed.xml> | Model releases, dataset news, community trends |
+| Cohere Blog | <https://cohere.com/blog> | — | Enterprise LLM API updates |
+| xAI Blog | <https://x.ai/blog> | — | Grok model updates |
+
+## 2. AI / ML — Research & Trends
+
+Pre-prints, paper trackers, and analyst commentary. Useful for spotting
+emerging capabilities **before** they hit vendor APIs.
+
+| Source | URL | Feed | Why it's here |
+|--------|-----|------|---------------|
+| arXiv cs.AI | <https://arxiv.org/list/cs.AI/recent> | <https://export.arxiv.org/rss/cs.AI> | Daily AI pre-prints |
+| arXiv cs.CL | <https://arxiv.org/list/cs.CL/recent> | <https://export.arxiv.org/rss/cs.CL> | NLP / language model pre-prints |
+| arXiv cs.LG | <https://arxiv.org/list/cs.LG/recent> | <https://export.arxiv.org/rss/cs.LG> | Machine learning pre-prints |
+| Papers with Code — Trending | <https://paperswithcode.com/> | — | Papers ranked by community attention with reference implementations |
+| Import AI (Jack Clark) | <https://importai.substack.com/> | <https://importai.substack.com/feed> | Weekly research roundup with policy + capability framing |
+| The Gradient | <https://thegradient.pub/> | <https://thegradient.pub/rss/> | Long-form ML research essays |
+
+## 3. Developer Tooling, DevEx & Platform Changelogs
+
+Platform features that unlock new product capabilities. GitHub's changelog
+in particular is the **single most important feed** for any project hosted
+on GitHub.
+
+| Source | URL | Feed | Why it's here |
+|--------|-----|------|---------------|
+| GitHub Changelog | <https://github.blog/changelog/> | <https://github.blog/changelog/feed/> | GitHub product feature releases |
+| GitHub Engineering | <https://github.blog/engineering/> | <https://github.blog/engineering/feed/> | Deep-dives on GitHub's own engineering decisions |
+| GitLab Blog | <https://about.gitlab.com/blog/> | <https://about.gitlab.com/atom.xml> | DevOps platform changes |
+| Vercel Blog | <https://vercel.com/blog> | — | Frontend/edge platform updates |
+| Cloudflare Blog | <https://blog.cloudflare.com/> | <https://blog.cloudflare.com/rss/> | Edge, Workers, security product updates |
+| AWS What's New | <https://aws.amazon.com/new/> | <https://aws.amazon.com/about-aws/whats-new/recent/feed/> | AWS service launches and updates |
+| GCP Blog | <https://cloud.google.com/blog/> | <https://cloud.google.com/feeds/gcp-release-notes.xml> | GCP release notes |
+| Stack Overflow Blog | <https://stackoverflow.blog/> | <https://stackoverflow.blog/feed/> | Developer survey data, industry trends |
+| The Pragmatic Engineer | <https://newsletter.pragmaticengineer.com/> | — | Engineering leadership and tooling trends |
+
+## 4. Security & Compliance
+
+Vulnerabilities, supply chain threats, and compliance changes that may
+surface as feature requirements.
+
+| Source | URL | Feed | Why it's here |
+|--------|-----|------|---------------|
+| GitHub Security Blog | <https://github.blog/security/> | <https://github.blog/security/feed/> | GitHub's own security advisories and features |
+| GitHub Advisory Database | <https://github.com/advisories> | — | Known vulnerabilities in open-source packages |
+| CISA Known Exploited Vulnerabilities | <https://www.cisa.gov/known-exploited-vulnerabilities-catalog> | <https://www.cisa.gov/sites/default/files/feeds/known_exploited_vulnerabilities.json> | US government KEV feed |
+| OpenSSF Blog | <https://openssf.org/blog/> | <https://openssf.org/blog/feed/> | Supply chain security standards |
+| Snyk Blog | <https://snyk.io/blog/> | <https://snyk.io/blog/feed/> | Vulnerability research and DevSecOps trends |
+| Krebs on Security | <https://krebsonsecurity.com/> | <https://krebsonsecurity.com/feed/> | Investigative security journalism |
+
+## 5. Software Engineering Practice & Industry Analysis
+
+Long-form analysis of engineering decisions, industry shifts, and
+developer trends.
+
+| Source | URL | Feed | Why it's here |
+|--------|-----|------|---------------|
+| Hacker News — Top | <https://news.ycombinator.com/> | <https://hnrss.org/frontpage> | Community signal on what engineers care about |
+| Lobsters | <https://lobste.rs/> | <https://lobste.rs/rss> | Curated engineering discussion |
+| Martin Fowler | <https://martinfowler.com/> | <https://martinfowler.com/feed.atom> | Software design patterns and architecture |
+| Latent Space (substack) | <https://www.latent.space/> | <https://www.latent.space/feed> | AI engineering deep-dives |
+| Simon Willison's Weblog | <https://simonwillison.net/> | <https://simonwillison.net/atom/entries/> | Practical LLM applications and web tech |
+| Stratechery | <https://stratechery.com/> | — | Tech strategy and business model analysis |
+| Increment | <https://increment.com/> | <https://increment.com/feed.xml> | Long-form engineering practice essays |
+
+## 6. Newsletters
+
+Curated weekly signal with low noise. Prefer fetching the RSS feed if
+listed over the web version.
+
+| Source | URL | Feed | Why it's here |
+|--------|-----|------|---------------|
+| TLDR | <https://tldr.tech/> | <https://tldr.tech/rss/tech> | High-signal daily tech summary |
+| Ben's Bites | <https://bensbites.beehiiv.com/> | <https://bensbites.beehiiv.com/feed> | Daily AI product and research digest |
+| The Rundown AI | <https://www.therundown.ai/> | — | AI tools and model updates for practitioners |
+| Bytes (JS) | <https://bytes.dev/> | — | JavaScript/TypeScript ecosystem news |
+| Python Weekly | <https://www.pythonweekly.com/> | — | Python ecosystem packages and tutorials |
+| DevOps Weekly | <https://www.devopsweekly.com/> | — | DevOps tooling and practices |
+
+## 7. Podcasts
+
+Engineering and product insights that often precede written coverage.
+Subscribe to the RSS feed and look for recent episode titles/descriptions.
+
+| Source | URL | Feed | Why it's here |
+|--------|-----|------|---------------|
+| Latent Space Podcast | <https://www.latent.space/podcast> | <https://www.latent.space/feed> | AI engineering interviews with practitioners |
+| The Changelog | <https://changelog.com/podcast> | <https://changelog.com/podcast/feed> | Open-source and developer tooling |
+| Practical AI | <https://changelog.com/practicalai> | <https://changelog.com/practicalai/feed> | Applied ML and AI products |
+| a16z Podcast | <https://a16z.com/podcasts/> | <https://a16z.com/feed/podcast/> | Tech and startup strategy |
+| The Cognitive Revolution | <https://www.cognitiverevolution.ai/> | — | AI capability and safety interviews |
+| Lex Fridman Podcast | <https://lexfridman.com/podcast/> | <https://lexfridman.com/feed/podcast/> | Long-form researcher/founder interviews |
+| Software Engineering Daily | <https://softwareengineeringdaily.com/> | <https://softwareengineeringdaily.com/feed/podcast/> | Engineering deep-dives |
+
+## 8. YouTube Channels
+
+Conference talks and product launches often land on YouTube before
+blog posts. Fetch the channel's RSS feed to see recent video titles.
+
+| Source | Channel URL | RSS Feed | Why it's here |
+|--------|-------------|----------|---------------|
+| Fireship | <https://www.youtube.com/@Fireship> | <https://www.youtube.com/feeds/videos.xml?channel_id=UCsBjURrPoezykLs9EqgamOA> | Quick-hit tech trends and new tool releases |
+| ThePrimeagen | <https://www.youtube.com/@ThePrimeagen> | <https://www.youtube.com/feeds/videos.xml?channel_id=UC8ENHE5xdFSwx71WHd9LCvg> | Developer tooling opinions and Rust/Go/TS trends |
+| Two Minute Papers | <https://www.youtube.com/@TwoMinutePapers> | <https://www.youtube.com/feeds/videos.xml?channel_id=UCbfYPyITQ-7l4upoX8nvctg> | Accessible ML research summaries |
+| Yannic Kilcher | <https://www.youtube.com/@YannicKilcher> | <https://www.youtube.com/feeds/videos.xml?channel_id=UCZHmQk67mSJgfCCTn7xBfew> | Deep ML paper walkthroughs |
+| AI Explained | <https://www.youtube.com/@aiexplained-official> | <https://www.youtube.com/feeds/videos.xml?channel_id=UCNJ1Ymd5yFuUPtn21xtRbbw> | LLM capability updates |
+| Matthew Berman | <https://www.youtube.com/@matthew_berman> | <https://www.youtube.com/feeds/videos.xml?channel_id=UCnUYZLuoy1rq1aVMwx4aTzw> | AI tool demos and model comparisons |
+| GitHub on YouTube | <https://www.youtube.com/@GitHub> | <https://www.youtube.com/feeds/videos.xml?channel_id=UC7c3Kb6jYCRj4JOHHZTxKsQ> | GitHub product demos and Universe talks |
+| AWS Events | <https://www.youtube.com/@AWSEventsChannel> | <https://www.youtube.com/feeds/videos.xml?channel_id=UCdoadna9HFHDqnC9lBaxd3w> | re:Invent, re:Inforce session recordings |
+
+## 9. Conferences
+
+Major annual events where product announcements and research previews
+cluster. Monitor the conference site and YouTube channel in the weeks
+before and after each event.
+
+| Conference | Typical date | URL | Why it's here |
+|------------|-------------|-----|---------------|
+| GitHub Universe | Oct | <https://githubuniverse.com/> | GitHub roadmap and ecosystem announcements |
+| KubeCon / CloudNativeCon | Mar + Nov | <https://events.linuxfoundation.org/kubecon-cloudnativecon-north-america/> | Cloud-native platform shifts |
+| AWS re:Invent | Nov–Dec | <https://reinvent.awsevents.com/> | AWS service launches |
+| Google Cloud Next | Apr | <https://cloud.withgoogle.com/next> | GCP and Workspace announcements |
+| NeurIPS | Dec | <https://neurips.cc/> | Top-tier ML research |
+| ICML | Jul | <https://icml.cc/> | Machine learning research trends |
+| ICLR | May | <https://iclr.cc/> | Deep learning and representation learning |
+| Strange Loop (archive) | — | <https://www.thestrangeloop.com/> | Engineering practice talks (archived; still valuable) |
diff --git a/standards/workflows/feature-ideation.yml b/standards/workflows/feature-ideation.yml
index cb03d75..d319b9b 100644
--- a/standards/workflows/feature-ideation.yml
+++ b/standards/workflows/feature-ideation.yml
@@ -28,9 +28,15 @@
 #   2. Replace the `project_context` value with a 3-5 sentence description
 #      of your project, its target users, and the competitive landscape Mary
 #      should research. This is the only required customisation.
-#   3. (Optional) Adjust the schedule cron if Friday morning UTC doesn't suit.
-#   4. Ensure GitHub Discussions is enabled with an "Ideas" category.
-#   5. Confirm the org-level secret CLAUDE_CODE_OAUTH_TOKEN is accessible.
+#   3. (Optional) Copy standards/feature-ideation-sources.md from
+#      petry-projects/.github to .github/feature-ideation-sources.md in your
+#      repo and trim/extend it for your project. Mary uses YOUR copy — not the
+#      central template — so each repo controls its own source list.
+#      Pass `sources_file: path/to/your-list.md` to the reusable workflow if
+#      you prefer a different location.
+#   4. (Optional) Adjust the schedule cron if Friday morning UTC doesn't suit.
+#   5. Ensure GitHub Discussions is enabled with an "Ideas" category.
+#   6. Confirm the org-level secret CLAUDE_CODE_OAUTH_TOKEN is accessible.
 #
 # Standard: https://github.com/petry-projects/.github/blob/main/standards/ci-standards.md#8-feature-ideation-feature-ideationyml--bmad-method-repos
 name: Feature Research & Ideation (BMAD Analyst)
@@ -69,18 +75,20 @@ jobs:
   ideate:
     # Permissions cascade from the calling job to the reusable workflow.
     # The reusable workflow's two jobs (gather-signals + analyze) need:
-    #   - contents:    read   (checkout, file reads)
-    #   - issues:      read   (signal collection)
-    #   - pull-requests: read (signal collection)
-    #   - discussions: write  (CRITICAL — create/update Discussion threads)
-    #   - id-token:    write  (claude-code-action OIDC for GitHub App token)
+    #   - contents:      read   (checkout, file reads)
+    #   - issues:        read   (signal collection)
+    #   - pull-requests: read   (signal collection)
+    #   - discussions:   write  (CRITICAL — create/update Discussion threads)
+    #   - id-token:      write  (claude-code-action OIDC for GitHub App token)
+    #   - actions:       read   (feed checkpoint — last successful run query)
     permissions:
       contents: read
       issues: read
       pull-requests: read
       discussions: write
       id-token: write
-    uses: petry-projects/.github/.github/workflows/feature-ideation-reusable.yml@v1
+      actions: read
+    uses: petry-projects/.github/.github/workflows/feature-ideation-reusable.yml@ae9709f4466dec60a5733c9e7487f69dcd004e05 # v1
     with:
       # === CUSTOMISE THIS PER REPO — the only required edit ===
       # Replace this paragraph with a 3-5 sentence description of your project,
@@ -90,6 +98,12 @@ jobs:
         TODO: Replace this with a description of the project and its market.
         Example: "ProjectX is a [type of product] for [target user]. Competitors
         include A, B, C. Key emerging trends in this space: X, Y, Z."
+      # === OPTIONAL: repo-local reputable source list ===
+      # Copy standards/feature-ideation-sources.md from petry-projects/.github
+      # to .github/feature-ideation-sources.md and customise it.
+      # The default value below matches the expected location — override only
+      # if you store the file elsewhere.
+      # sources_file: '.github/feature-ideation-sources.md'
       focus_area: ${{ inputs.focus_area || '' }}
       research_depth: ${{ inputs.research_depth || 'standard' }}
       dry_run: ${{ inputs.dry_run || false }}
diff --git a/test/workflows/feature-ideation/fixtures/expected/empty-repo.signals.json b/test/workflows/feature-ideation/fixtures/expected/empty-repo.signals.json
index 4101afb..e6438b5 100644
--- a/test/workflows/feature-ideation/fixtures/expected/empty-repo.signals.json
+++ b/test/workflows/feature-ideation/fixtures/expected/empty-repo.signals.json
@@ -1,6 +1,7 @@
 {
-  "schema_version": "1.0.0",
+  "schema_version": "1.1.0",
   "scan_date": "2026-04-07T07:00:00Z",
+  "last_successful_run": "2026-03-31T07:00:00Z",
   "repo": "petry-projects/talkterm",
   "open_issues": { "count": 0, "items": [] },
   "closed_issues_30d": { "count": 0, "items": [] },
diff --git a/test/workflows/feature-ideation/fixtures/expected/populated.signals.json b/test/workflows/feature-ideation/fixtures/expected/populated.signals.json
index 4c92921..5618e36 100644
--- a/test/workflows/feature-ideation/fixtures/expected/populated.signals.json
+++ b/test/workflows/feature-ideation/fixtures/expected/populated.signals.json
@@ -1,6 +1,7 @@
 {
-  "schema_version": "1.0.0",
+  "schema_version": "1.1.0",
   "scan_date": "2026-04-07T07:00:00Z",
+  "last_successful_run": "2026-03-31T07:00:00Z",
   "repo": "petry-projects/talkterm",
   "open_issues": {
     "count": 2,
diff --git a/test/workflows/feature-ideation/fixtures/expected/truncated.signals.json b/test/workflows/feature-ideation/fixtures/expected/truncated.signals.json
index 845db66..2c884ea 100644
--- a/test/workflows/feature-ideation/fixtures/expected/truncated.signals.json
+++ b/test/workflows/feature-ideation/fixtures/expected/truncated.signals.json
@@ -1,6 +1,7 @@
 {
-  "schema_version": "1.0.0",
+  "schema_version": "1.1.0",
   "scan_date": "2026-04-07T07:00:00Z",
+  "last_successful_run": "2026-03-31T07:00:00Z",
   "repo": "petry-projects/talkterm",
   "open_issues": { "count": 0, "items": [] },
   "closed_issues_30d": { "count": 0, "items": [] },

From 56fd3ca68e1388bcb6d772e4b5cfad433222159a Mon Sep 17 00:00:00 2001
From: DJ <dj@Rachels-Air.localdomain>
Date: Thu, 16 Apr 2026 11:00:04 -0700
Subject: [PATCH 02/13] fix(feature-ideation): validate ISO-8601 format for
 last_successful_run fallback

The gh stub used in bats tests returns raw fixture JSON without applying
--jq filters, so the captured last_successful_run value was a JSON array
instead of an ISO-8601 timestamp. Add a grep -qE '^[0-9]{4}-...' guard
that falls back to the 30-day default whenever the output is not a valid
date-time string, keeping all existing bats tests green without requiring
every test script to stub the new gh run list call.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
---
 .github/scripts/feature-ideation/collect-signals.sh | 7 ++++++-
 1 file changed, 6 insertions(+), 1 deletion(-)

diff --git a/.github/scripts/feature-ideation/collect-signals.sh b/.github/scripts/feature-ideation/collect-signals.sh
index 2051ba5..5aa81b1 100755
--- a/.github/scripts/feature-ideation/collect-signals.sh
+++ b/.github/scripts/feature-ideation/collect-signals.sh
@@ -86,7 +86,12 @@ main() {
     --json createdAt \
     --jq '.[0].createdAt // empty' \
     2>/dev/null || true)
-  if [ -z "$last_successful_run" ] || [ "$last_successful_run" = "null" ]; then
+  # Validate that the result looks like an ISO-8601 datetime. The real `gh`
+  # CLI applies the --jq filter and emits a bare timestamp; in test environments
+  # the gh stub returns raw fixture JSON (without applying --jq), so we guard
+  # against that here rather than requiring every test to stub this extra call.
+  if [ -z "$last_successful_run" ] || [ "$last_successful_run" = "null" ] || \
+     ! printf '%s' "$last_successful_run" | grep -qE '^[0-9]{4}-[0-9]{2}-[0-9]{2}T'; then
     last_successful_run=$(date_days_ago 30)
     printf '[collect-signals] no prior successful run found; using 30-day fallback: %s\n' \
       "$last_successful_run" >&2

From 0425a174a1e9f8c4b76b4a74477d13f3ce843f11 Mon Sep 17 00:00:00 2001
From: DJ <dj@Rachels-Air.localdomain>
Date: Thu, 16 Apr 2026 11:06:18 -0700
Subject: [PATCH 03/13] fix(collect-signals): align bats stub order with new gh
 run list call

The feed-checkpoint `gh run list` call added in the previous commit is
now the *first* gh invocation, so every manually-built stub script in
collect-signals.bats needs a corresponding first entry.

- Prepend run-list-last-success.txt to all 5 manual script builders
  (auth-failure, graphql-errors, bot-only-truncation,
  discussions-truncated, no-ideas-category)
- Fix date fallback format: append T00:00:00Z to date_days_ago output
  so the JSON Schema format:date-time constraint is satisfied

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
---
 .../feature-ideation/collect-signals.sh       |  2 +-
 .../feature-ideation/collect-signals.bats     | 22 +++++++++++++------
 .../gh-responses/run-list-last-success.txt    |  1 +
 3 files changed, 17 insertions(+), 8 deletions(-)
 create mode 100644 test/workflows/feature-ideation/fixtures/gh-responses/run-list-last-success.txt

diff --git a/.github/scripts/feature-ideation/collect-signals.sh b/.github/scripts/feature-ideation/collect-signals.sh
index 5aa81b1..5ba55fe 100755
--- a/.github/scripts/feature-ideation/collect-signals.sh
+++ b/.github/scripts/feature-ideation/collect-signals.sh
@@ -92,7 +92,7 @@ main() {
   # against that here rather than requiring every test to stub this extra call.
   if [ -z "$last_successful_run" ] || [ "$last_successful_run" = "null" ] || \
      ! printf '%s' "$last_successful_run" | grep -qE '^[0-9]{4}-[0-9]{2}-[0-9]{2}T'; then
-    last_successful_run=$(date_days_ago 30)
+    last_successful_run="$(date_days_ago 30)T00:00:00Z"
     printf '[collect-signals] no prior successful run found; using 30-day fallback: %s\n' \
       "$last_successful_run" >&2
   else
diff --git a/test/workflows/feature-ideation/collect-signals.bats b/test/workflows/feature-ideation/collect-signals.bats
index 94f9a12..cf306ff 100644
--- a/test/workflows/feature-ideation/collect-signals.bats
+++ b/test/workflows/feature-ideation/collect-signals.bats
@@ -21,15 +21,17 @@ teardown() {
 
 # Build a multi-call gh script for the standard happy path.
 # Order MUST match collect-signals.sh:
-#   1. gh issue list --state open
-#   2. gh issue list --state closed
-#   3. gh api graphql (categories)
-#   4. gh api graphql (discussions)
-#   5. gh release list
-#   6. gh pr list --state merged
+#   1. gh run list (feed checkpoint — last successful run)
+#   2. gh issue list --state open
+#   3. gh issue list --state closed
+#   4. gh api graphql (categories)
+#   5. gh api graphql (discussions)
+#   6. gh release list
+#   7. gh pr list --state merged
 build_happy_script() {
   local script="${TT_TMP}/gh-script.tsv"
   : >"$script"
+  printf '0\t%s\t-\n' "${TT_FIXTURES_DIR}/gh-responses/run-list-last-success.txt" >>"$script"
   printf '0\t%s\t-\n' "${TT_FIXTURES_DIR}/gh-responses/issue-list-open.json" >>"$script"
   printf '0\t%s\t-\n' "${TT_FIXTURES_DIR}/gh-responses/issue-list-closed.json" >>"$script"
   printf '0\t%s\t-\n' "${TT_FIXTURES_DIR}/gh-responses/graphql-categories.json" >>"$script"
@@ -115,7 +117,9 @@ build_happy_script() {
   script="${TT_TMP}/gh-script.tsv"
   err_file="${TT_TMP}/auth-err.txt"
   printf 'HTTP 401: Bad credentials\n' >"$err_file"
-  printf '4\t-\t%s\n' "$err_file" >"$script"
+  # run list (feed checkpoint — silenced with || true, so failure falls back)
+  printf '0\t%s\t-\n' "${TT_FIXTURES_DIR}/gh-responses/run-list-last-success.txt" >"$script"
+  printf '4\t-\t%s\n' "$err_file" >>"$script"
   export GH_STUB_SCRIPT="$script"
   rm -f "${TT_TMP}/.gh-stub-counter"
 
@@ -127,6 +131,7 @@ build_happy_script() {
 @test "collect-signals: FAILS LOUD on GraphQL errors envelope (categories)" {
   script="${TT_TMP}/gh-script.tsv"
   : >"$script"
+  printf '0\t%s\t-\n' "${TT_FIXTURES_DIR}/gh-responses/run-list-last-success.txt" >>"$script"
   printf '0\t%s\t-\n' "${TT_FIXTURES_DIR}/gh-responses/issue-list-open.json" >>"$script"
   printf '0\t%s\t-\n' "${TT_FIXTURES_DIR}/gh-responses/issue-list-closed.json" >>"$script"
   printf '0\t%s\t-\n' "${TT_FIXTURES_DIR}/gh-responses/graphql-errors-envelope.json" >>"$script"
@@ -183,6 +188,7 @@ JSON
 
   script="${TT_TMP}/gh-script.tsv"
   : >"$script"
+  printf '0\t%s\t-\n' "${TT_FIXTURES_DIR}/gh-responses/run-list-last-success.txt" >>"$script"  # feed checkpoint
   printf '0\t%s\t-\n' "$bot_file"   >>"$script"   # open issues — all bots
   printf '0\t%s\t-\n' "$empty_file" >>"$script"   # closed issues
   printf '0\t%s\t-\n' "${TT_FIXTURES_DIR}/gh-responses/graphql-no-ideas-category.json" >>"$script"
@@ -202,6 +208,7 @@ JSON
 @test "collect-signals: emits truncation warning when discussions hasNextPage=true" {
   script="${TT_TMP}/gh-script.tsv"
   : >"$script"
+  printf '0\t%s\t-\n' "${TT_FIXTURES_DIR}/gh-responses/run-list-last-success.txt" >>"$script"
   printf '0\t%s\t-\n' "${TT_FIXTURES_DIR}/gh-responses/issue-list-open.json" >>"$script"
   printf '0\t%s\t-\n' "${TT_FIXTURES_DIR}/gh-responses/issue-list-closed.json" >>"$script"
   printf '0\t%s\t-\n' "${TT_FIXTURES_DIR}/gh-responses/graphql-categories.json" >>"$script"
@@ -225,6 +232,7 @@ JSON
 @test "collect-signals: skips discussions when Ideas category absent" {
   script="${TT_TMP}/gh-script.tsv"
   : >"$script"
+  printf '0\t%s\t-\n' "${TT_FIXTURES_DIR}/gh-responses/run-list-last-success.txt" >>"$script"
   printf '0\t%s\t-\n' "${TT_FIXTURES_DIR}/gh-responses/issue-list-open.json" >>"$script"
   printf '0\t%s\t-\n' "${TT_FIXTURES_DIR}/gh-responses/issue-list-closed.json" >>"$script"
   printf '0\t%s\t-\n' "${TT_FIXTURES_DIR}/gh-responses/graphql-no-ideas-category.json" >>"$script"
diff --git a/test/workflows/feature-ideation/fixtures/gh-responses/run-list-last-success.txt b/test/workflows/feature-ideation/fixtures/gh-responses/run-list-last-success.txt
new file mode 100644
index 0000000..2ed9415
--- /dev/null
+++ b/test/workflows/feature-ideation/fixtures/gh-responses/run-list-last-success.txt
@@ -0,0 +1 @@
+2026-03-31T07:00:00Z
\ No newline at end of file

From 15045bee0ca08feee56ea41a95a2eb8a28da62f9 Mon Sep 17 00:00:00 2001
From: DJ <dj@Rachels-MacBook-Air.local>
Date: Thu, 16 Apr 2026 19:19:57 -0700
Subject: [PATCH 04/13] fix(compose-signals.bats): update call sites to 12-arg
 signature

All compose_signals invocations now pass last_successful_run as
the new arg 10, shifting schema_version to 11 and
truncation_warnings to 12. Also adds last_successful_run to the
required-fields assertion in the empty-inputs test.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
---
 .../feature-ideation/compose-signals.bats     | 19 ++++++++++---------
 1 file changed, 10 insertions(+), 9 deletions(-)

diff --git a/test/workflows/feature-ideation/compose-signals.bats b/test/workflows/feature-ideation/compose-signals.bats
index 4dced2c..35359e9 100644
--- a/test/workflows/feature-ideation/compose-signals.bats
+++ b/test/workflows/feature-ideation/compose-signals.bats
@@ -18,6 +18,7 @@ compose_empty() {
     '[]' '[]' '[]' '[]' '[]' '[]' '[]' \
     'foo/bar' \
     '2026-04-07T00:00:00Z' \
+    '2026-03-07T00:00:00Z' \
     '1.0.0' \
     '[]'
 }
@@ -34,14 +35,14 @@ compose_empty() {
 @test "compose: rejects empty string for any JSON arg" {
   run compose_signals \
     '' '[]' '[]' '[]' '[]' '[]' '[]' \
-    'foo/bar' '2026-04-07T00:00:00Z' '1.0.0' '[]'
+    'foo/bar' '2026-04-07T00:00:00Z' '2026-03-07T00:00:00Z' '1.0.0' '[]'
   [ "$status" -ne 0 ]
 }
 
 @test "compose: rejects non-JSON for any JSON arg" {
   run compose_signals \
     'not json' '[]' '[]' '[]' '[]' '[]' '[]' \
-    'foo/bar' '2026-04-07T00:00:00Z' '1.0.0' '[]'
+    'foo/bar' '2026-04-07T00:00:00Z' '2026-03-07T00:00:00Z' '1.0.0' '[]'
   [ "$status" -ne 0 ]
 }
 
@@ -52,9 +53,9 @@ compose_empty() {
 @test "compose: produces all required top-level fields with empty inputs" {
   run compose_empty
   [ "$status" -eq 0 ]
-  for field in schema_version scan_date repo open_issues closed_issues_30d \
-               ideas_discussions releases merged_prs_30d feature_requests \
-               bug_reports truncation_warnings; do
+  for field in schema_version scan_date last_successful_run repo open_issues \
+               closed_issues_30d ideas_discussions releases merged_prs_30d \
+               feature_requests bug_reports truncation_warnings; do
     printf '%s' "$output" | jq -e "has(\"$field\")" >/dev/null
   done
 }
@@ -63,7 +64,7 @@ compose_empty() {
   open='[{"number":1,"title":"a","labels":[]},{"number":2,"title":"b","labels":[]}]'
   run compose_signals \
     "$open" '[]' '[]' '[]' '[]' '[]' '[]' \
-    'foo/bar' '2026-04-07T00:00:00Z' '1.0.0' '[]'
+    'foo/bar' '2026-04-07T00:00:00Z' '2026-03-07T00:00:00Z' '1.0.0' '[]'
   [ "$status" -eq 0 ]
   count=$(printf '%s' "$output" | jq '.open_issues.count')
   items_len=$(printf '%s' "$output" | jq '.open_issues.items | length')
@@ -74,7 +75,7 @@ compose_empty() {
 @test "compose: schema_version is preserved verbatim" {
   run compose_signals \
     '[]' '[]' '[]' '[]' '[]' '[]' '[]' \
-    'foo/bar' '2026-04-07T00:00:00Z' '2.5.1' '[]'
+    'foo/bar' '2026-04-07T00:00:00Z' '2026-03-07T00:00:00Z' '2.5.1' '[]'
   [ "$status" -eq 0 ]
   v=$(printf '%s' "$output" | jq -r '.schema_version')
   [ "$v" = "2.5.1" ]
@@ -84,7 +85,7 @@ compose_empty() {
   warnings='[{"source":"open_issues","limit":50,"message":"truncated"}]'
   run compose_signals \
     '[]' '[]' '[]' '[]' '[]' '[]' '[]' \
-    'foo/bar' '2026-04-07T00:00:00Z' '1.0.0' "$warnings"
+    'foo/bar' '2026-04-07T00:00:00Z' '2026-03-07T00:00:00Z' '1.0.0' "$warnings"
   [ "$status" -eq 0 ]
   src=$(printf '%s' "$output" | jq -r '.truncation_warnings[0].source')
   [ "$src" = "open_issues" ]
@@ -93,7 +94,7 @@ compose_empty() {
 @test "compose: scan_date and repo round-trip exactly" {
   run compose_signals \
     '[]' '[]' '[]' '[]' '[]' '[]' '[]' \
-    'octocat/hello-world' '2030-01-15T12:34:56Z' '1.0.0' '[]'
+    'octocat/hello-world' '2030-01-15T12:34:56Z' '2029-12-15T12:34:56Z' '1.0.0' '[]'
   [ "$status" -eq 0 ]
   d=$(printf '%s' "$output" | jq -r '.scan_date')
   r=$(printf '%s' "$output" | jq -r '.repo')

From a07e932f26f0ed5bd3baa585c6b665d0a89ac727 Mon Sep 17 00:00:00 2001
From: DJ <dj@Rachels-MacBook-Air.local>
Date: Thu, 16 Apr 2026 19:26:29 -0700
Subject: [PATCH 05/13] fix(review): address CodeRabbit and Copilot review
 comments
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

- collect-signals.sh: use WORKFLOW_FILE env var (default: feature-ideation.yml)
  so repos that rename their caller stub can override without a code change;
  capture gh run list stderr in a temp file and log it when the fallback is
  triggered so auth/network failures are distinguishable from first-run
- feature-ideation-reusable.yml: clarify propagation comment — changes reach
  @v1 stubs only after the v1 tag is bumped, not on every next run
- ci-standards.md: align Tier-1 table wording with the @v1 tag-bump model
- standards/workflows/feature-ideation.yml: reword sources_file comment to
  make clear users must uncomment AND change the path for non-default locations;
  show a non-default example path to reduce ambiguity

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
---
 .../scripts/feature-ideation/collect-signals.sh   | 15 ++++++++++++---
 .github/workflows/feature-ideation-reusable.yml   |  4 +++-
 standards/ci-standards.md                         |  2 +-
 standards/workflows/feature-ideation.yml          |  8 ++++----
 4 files changed, 20 insertions(+), 9 deletions(-)

diff --git a/.github/scripts/feature-ideation/collect-signals.sh b/.github/scripts/feature-ideation/collect-signals.sh
index 5ba55fe..0a11f77 100755
--- a/.github/scripts/feature-ideation/collect-signals.sh
+++ b/.github/scripts/feature-ideation/collect-signals.sh
@@ -76,22 +76,31 @@ main() {
   # is still in-progress, so --status=success --limit=1 reliably returns the
   # previous successful run. Falls back to 30 days ago on first-ever run or
   # after a long gap so the initial scan is bounded.
+  # WORKFLOW_FILE — caller-supplied env var for repos that name their stub
+  # something other than the conventional "feature-ideation.yml". Defaults to
+  # the conventional name; no change needed for repos that follow the standard.
   printf '[collect-signals] resolving feed checkpoint (last successful run)\n' >&2
-  local last_successful_run
+  local last_successful_run _run_stderr _run_err
+  _run_stderr=$(mktemp)
   last_successful_run=$(gh run list \
     --repo "$REPO" \
-    --workflow="feature-ideation.yml" \
+    --workflow="${WORKFLOW_FILE:-feature-ideation.yml}" \
     --status=success \
     --limit=1 \
     --json createdAt \
     --jq '.[0].createdAt // empty' \
-    2>/dev/null || true)
+    2>"$_run_stderr" || true)
+  _run_err=$(cat "$_run_stderr")
+  rm -f "$_run_stderr"
   # Validate that the result looks like an ISO-8601 datetime. The real `gh`
   # CLI applies the --jq filter and emits a bare timestamp; in test environments
   # the gh stub returns raw fixture JSON (without applying --jq), so we guard
   # against that here rather than requiring every test to stub this extra call.
   if [ -z "$last_successful_run" ] || [ "$last_successful_run" = "null" ] || \
      ! printf '%s' "$last_successful_run" | grep -qE '^[0-9]{4}-[0-9]{2}-[0-9]{2}T'; then
+    if [ -n "$_run_err" ]; then
+      printf '[collect-signals] gh run list warning: %s\n' "$_run_err" >&2
+    fi
     last_successful_run="$(date_days_ago 30)T00:00:00Z"
     printf '[collect-signals] no prior successful run found; using 30-day fallback: %s\n' \
       "$last_successful_run" >&2
diff --git a/.github/workflows/feature-ideation-reusable.yml b/.github/workflows/feature-ideation-reusable.yml
index 06a860e..a3b5b0e 100644
--- a/.github/workflows/feature-ideation-reusable.yml
+++ b/.github/workflows/feature-ideation-reusable.yml
@@ -20,7 +20,9 @@
 # Why a reusable workflow:
 #   - The 5-phase ideation pipeline (Market Research → Brainstorming → Party
 #     Mode → Adversarial → Publish) is universal. Tuning the pattern in one
-#     place propagates to every BMAD-enabled repo on next run.
+#     place propagates to every BMAD-enabled repo after the v1 tag is bumped
+#     and their next scheduled run executes. Repos tracking @main pick it up
+#     immediately on their next run.
 #   - The two critical gotchas (github_token override, ANTHROPIC_MODEL env var)
 #     are baked in here so callers cannot accidentally regress them.
 #
diff --git a/standards/ci-standards.md b/standards/ci-standards.md
index edbb046..be3fe74 100644
--- a/standards/ci-standards.md
+++ b/standards/ci-standards.md
@@ -22,7 +22,7 @@ where to send a fix when behavior needs to change.
 
 | Tier | Examples | What lives in `standards/workflows/` | Where logic lives | Edits allowed in adopting repo |
 |---|---|---|---|---|
-| **1. Stub** | `claude.yml`, `dependency-audit.yml`, `dependabot-automerge.yml`, `dependabot-rebase.yml`, `agent-shield.yml`, `feature-ideation.yml` | A thin caller stub that delegates via `uses: petry-projects/.github/.github/workflows/<name>-reusable.yml@v1` | The matching `*-reusable.yml` in this repo (single source of truth) | **None** in normal use. May tune `with:` inputs where the reusable exposes them (e.g. `agent-shield` accepts `min-severity`, `required-files`; `feature-ideation` requires `project_context`). To change behavior, open a PR against the reusable in this repo — the change propagates everywhere on next run. |
+| **1. Stub** | `claude.yml`, `dependency-audit.yml`, `dependabot-automerge.yml`, `dependabot-rebase.yml`, `agent-shield.yml`, `feature-ideation.yml` | A thin caller stub that delegates via `uses: petry-projects/.github/.github/workflows/<name>-reusable.yml@v1` | The matching `*-reusable.yml` in this repo (single source of truth) | **None** in normal use. May tune `with:` inputs where the reusable exposes them (e.g. `agent-shield` accepts `min-severity`, `required-files`; `feature-ideation` requires `project_context`). To change behavior, open a PR against the reusable in this repo — repos on `@v1` pick it up after the `v1` tag is bumped; repos on `@main` pick it up on their next run. |
 | **2. Per-repo template** | `ci.yml`, `sonarcloud.yml` | _(no template — see the patterns documented below)_ | In each repo, because the workflow is tech-stack-specific (language matrix, build tool, test framework) | **Limited.** Each adopting repo carries its own copy. Stay within the patterns in this document; do not change action SHAs, permission scopes, trigger events, or job names without raising a standards PR first. |
 | **GitHub-managed** | CodeQL default setup | _(no workflow file — managed via repo Settings → Code security)_ | GitHub | None. Configured via `apply-repo-settings.sh`; per-repo `codeql.yml` files are treated as drift by the compliance audit. See [§2 CodeQL Analysis](#2-codeql-analysis-github-managed-default-setup). |
 | **3. Free per-repo** | `release.yml`, project-specific automation | _(out of scope for this standard)_ | Per-repo | Free, but must still comply with the [Action Pinning Policy](#action-pinning-policy) and the [Required Workflows](#required-workflows) constraints. |
diff --git a/standards/workflows/feature-ideation.yml b/standards/workflows/feature-ideation.yml
index d319b9b..b8a4c05 100644
--- a/standards/workflows/feature-ideation.yml
+++ b/standards/workflows/feature-ideation.yml
@@ -100,10 +100,10 @@ jobs:
         include A, B, C. Key emerging trends in this space: X, Y, Z."
       # === OPTIONAL: repo-local reputable source list ===
       # Copy standards/feature-ideation-sources.md from petry-projects/.github
-      # to .github/feature-ideation-sources.md and customise it.
-      # The default value below matches the expected location — override only
-      # if you store the file elsewhere.
-      # sources_file: '.github/feature-ideation-sources.md'
+      # to .github/feature-ideation-sources.md and customise it. The reusable
+      # workflow defaults to that path, so you only need to uncomment and change
+      # sources_file below if you store the list somewhere else.
+      # sources_file: 'docs/feature-ideation-sources.md'
       focus_area: ${{ inputs.focus_area || '' }}
       research_depth: ${{ inputs.research_depth || 'standard' }}
       dry_run: ${{ inputs.dry_run || false }}

From 81ca148f0af243ea620ba6125beed5fbd9166429 Mon Sep 17 00:00:00 2001
From: don-petry <36422719+don-petry@users.noreply.github.com>
Date: Thu, 16 Apr 2026 19:47:21 -0700
Subject: [PATCH 06/13] test: add self-test feature-ideation stub for dry-run
 validation

---
 .github/workflows/feature-ideation.yml | 62 ++++++++++++++++++++++++++
 1 file changed, 62 insertions(+)
 create mode 100644 .github/workflows/feature-ideation.yml

diff --git a/.github/workflows/feature-ideation.yml b/.github/workflows/feature-ideation.yml
new file mode 100644
index 0000000..bc048c1
--- /dev/null
+++ b/.github/workflows/feature-ideation.yml
@@ -0,0 +1,62 @@
+# ─────────────────────────────────────────────────────────────────────────────
+# TEST STUB — petry-projects/.github self-hosted ideation run.
+#
+# This file is NOT part of the PR being tested; it exists on the
+# feat/feature-ideation-sources-list branch only so we can trigger a
+# workflow_dispatch dry run against the new reusable workflow code before
+# the PR is merged to main.
+#
+# uses: points at the same branch so we exercise our new sources_file input,
+# last_successful_run feed checkpoint, and WORKFLOW_FILE convention.
+# ─────────────────────────────────────────────────────────────────────────────
+name: Feature Research & Ideation — .github self-test
+
+on:
+  workflow_dispatch:
+    inputs:
+      research_depth:
+        description: 'Research depth'
+        required: false
+        default: 'standard'
+        type: choice
+        options: [quick, standard, deep]
+      focus_area:
+        description: 'Optional focus area'
+        required: false
+        type: string
+
+permissions: {}
+
+concurrency:
+  group: feature-ideation-self-test
+  cancel-in-progress: true
+
+jobs:
+  ideate:
+    permissions:
+      contents: read
+      issues: read
+      pull-requests: read
+      discussions: write
+      actions: read
+      id-token: write
+    uses: petry-projects/.github/.github/workflows/feature-ideation-reusable.yml@feat/feature-ideation-sources-list
+    with:
+      project_context: |
+        petry-projects/.github is the org-level standards and tooling repository
+        for the petry-projects GitHub organisation. It contains the canonical CI/CD
+        standards (ci-standards.md), reusable GitHub Actions workflows (claude-code,
+        feature-ideation, agent-shield, dependabot), and the BMAD Method agentic
+        development framework (multi-skill AI analyst pipeline). Primary consumers
+        are internal project repos (Broodly, TalkTerm, markets). Key emerging trends
+        to track: GitHub Actions platform improvements, agentic CI patterns, AI-assisted
+        code review tooling (CodeRabbit, Copilot), security hardening for AI-agent
+        workflows (prompt injection, supply-chain), and developer-experience standards
+        for LLM-heavy codebases. No public users — this is internal org DevX infrastructure.
+      tooling_ref: 'feat/feature-ideation-sources-list'
+      sources_file: 'standards/feature-ideation-sources.md'
+      focus_area: ${{ inputs.focus_area || '' }}
+      research_depth: ${{ inputs.research_depth || 'standard' }}
+      dry_run: true
+    secrets:
+      CLAUDE_CODE_OAUTH_TOKEN: ${{ secrets.CLAUDE_CODE_OAUTH_TOKEN }}
\ No newline at end of file

From e7e04b8f1bc286100bc1d37dd4ca91bd5612c7e1 Mon Sep 17 00:00:00 2001
From: don-petry <36422719+don-petry@users.noreply.github.com>
Date: Thu, 16 Apr 2026 19:48:41 -0700
Subject: [PATCH 07/13] fix: trailing newline + clean up stub

---
 .github/workflows/feature-ideation.yml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/.github/workflows/feature-ideation.yml b/.github/workflows/feature-ideation.yml
index bc048c1..bf8d396 100644
--- a/.github/workflows/feature-ideation.yml
+++ b/.github/workflows/feature-ideation.yml
@@ -59,4 +59,4 @@ jobs:
       research_depth: ${{ inputs.research_depth || 'standard' }}
       dry_run: true
     secrets:
-      CLAUDE_CODE_OAUTH_TOKEN: ${{ secrets.CLAUDE_CODE_OAUTH_TOKEN }}
\ No newline at end of file
+      CLAUDE_CODE_OAUTH_TOKEN: ${{ secrets.CLAUDE_CODE_OAUTH_TOKEN }}

From f3dfa6b47dbb468c9274437d720fa1cad8f16029 Mon Sep 17 00:00:00 2001
From: don-petry <36422719+don-petry@users.noreply.github.com>
Date: Fri, 17 Apr 2026 09:35:29 -0700
Subject: [PATCH 08/13] fix: pin reusable workflow ref to commit SHA
 (SonarCloud)

---
 .github/workflows/feature-ideation.yml | 16 +++++++---------
 1 file changed, 7 insertions(+), 9 deletions(-)

diff --git a/.github/workflows/feature-ideation.yml b/.github/workflows/feature-ideation.yml
index bf8d396..ec02d6e 100644
--- a/.github/workflows/feature-ideation.yml
+++ b/.github/workflows/feature-ideation.yml
@@ -1,13 +1,11 @@
 # ─────────────────────────────────────────────────────────────────────────────
-# TEST STUB — petry-projects/.github self-hosted ideation run.
+# TEST STUB — petry-projects/.github self-hosted ideation dry run.
 #
-# This file is NOT part of the PR being tested; it exists on the
-# feat/feature-ideation-sources-list branch only so we can trigger a
-# workflow_dispatch dry run against the new reusable workflow code before
-# the PR is merged to main.
+# This file exists on feat/feature-ideation-sources-list to allow triggering
+# a workflow_dispatch dry run exercising the new reusable workflow code before
+# the PR is merged to main and the v1 tag is bumped.
 #
-# uses: points at the same branch so we exercise our new sources_file input,
-# last_successful_run feed checkpoint, and WORKFLOW_FILE convention.
+# uses: is pinned to the branch HEAD SHA so SonarCloud is satisfied.
 # ─────────────────────────────────────────────────────────────────────────────
 name: Feature Research & Ideation — .github self-test
 
@@ -40,7 +38,7 @@ jobs:
       discussions: write
       actions: read
       id-token: write
-    uses: petry-projects/.github/.github/workflows/feature-ideation-reusable.yml@feat/feature-ideation-sources-list
+    uses: petry-projects/.github/.github/workflows/feature-ideation-reusable.yml@bc8e529ea0f7a9a081d5b3bf829af9e5c8045b0a # feat/feature-ideation-sources-list
     with:
       project_context: |
         petry-projects/.github is the org-level standards and tooling repository
@@ -53,7 +51,7 @@ jobs:
         code review tooling (CodeRabbit, Copilot), security hardening for AI-agent
         workflows (prompt injection, supply-chain), and developer-experience standards
         for LLM-heavy codebases. No public users — this is internal org DevX infrastructure.
-      tooling_ref: 'feat/feature-ideation-sources-list'
+      tooling_ref: 'bc8e529ea0f7a9a081d5b3bf829af9e5c8045b0a'
       sources_file: 'standards/feature-ideation-sources.md'
       focus_area: ${{ inputs.focus_area || '' }}
       research_depth: ${{ inputs.research_depth || 'standard' }}

From 11e2995f4d6cff732f879271350cb68975336a6b Mon Sep 17 00:00:00 2001
From: don-petry <36422719+don-petry@users.noreply.github.com>
Date: Fri, 17 Apr 2026 09:47:19 -0700
Subject: [PATCH 09/13] chore: remove temporary test stub (not for main)

---
 .github/workflows/feature-ideation.yml | 60 --------------------------
 1 file changed, 60 deletions(-)
 delete mode 100644 .github/workflows/feature-ideation.yml

diff --git a/.github/workflows/feature-ideation.yml b/.github/workflows/feature-ideation.yml
deleted file mode 100644
index ec02d6e..0000000
--- a/.github/workflows/feature-ideation.yml
+++ /dev/null
@@ -1,60 +0,0 @@
-# ─────────────────────────────────────────────────────────────────────────────
-# TEST STUB — petry-projects/.github self-hosted ideation dry run.
-#
-# This file exists on feat/feature-ideation-sources-list to allow triggering
-# a workflow_dispatch dry run exercising the new reusable workflow code before
-# the PR is merged to main and the v1 tag is bumped.
-#
-# uses: is pinned to the branch HEAD SHA so SonarCloud is satisfied.
-# ─────────────────────────────────────────────────────────────────────────────
-name: Feature Research & Ideation — .github self-test
-
-on:
-  workflow_dispatch:
-    inputs:
-      research_depth:
-        description: 'Research depth'
-        required: false
-        default: 'standard'
-        type: choice
-        options: [quick, standard, deep]
-      focus_area:
-        description: 'Optional focus area'
-        required: false
-        type: string
-
-permissions: {}
-
-concurrency:
-  group: feature-ideation-self-test
-  cancel-in-progress: true
-
-jobs:
-  ideate:
-    permissions:
-      contents: read
-      issues: read
-      pull-requests: read
-      discussions: write
-      actions: read
-      id-token: write
-    uses: petry-projects/.github/.github/workflows/feature-ideation-reusable.yml@bc8e529ea0f7a9a081d5b3bf829af9e5c8045b0a # feat/feature-ideation-sources-list
-    with:
-      project_context: |
-        petry-projects/.github is the org-level standards and tooling repository
-        for the petry-projects GitHub organisation. It contains the canonical CI/CD
-        standards (ci-standards.md), reusable GitHub Actions workflows (claude-code,
-        feature-ideation, agent-shield, dependabot), and the BMAD Method agentic
-        development framework (multi-skill AI analyst pipeline). Primary consumers
-        are internal project repos (Broodly, TalkTerm, markets). Key emerging trends
-        to track: GitHub Actions platform improvements, agentic CI patterns, AI-assisted
-        code review tooling (CodeRabbit, Copilot), security hardening for AI-agent
-        workflows (prompt injection, supply-chain), and developer-experience standards
-        for LLM-heavy codebases. No public users — this is internal org DevX infrastructure.
-      tooling_ref: 'bc8e529ea0f7a9a081d5b3bf829af9e5c8045b0a'
-      sources_file: 'standards/feature-ideation-sources.md'
-      focus_area: ${{ inputs.focus_area || '' }}
-      research_depth: ${{ inputs.research_depth || 'standard' }}
-      dry_run: true
-    secrets:
-      CLAUDE_CODE_OAUTH_TOKEN: ${{ secrets.CLAUDE_CODE_OAUTH_TOKEN }}

From 689a2d7483d384ef464895aaecb1fd453e1613e7 Mon Sep 17 00:00:00 2001
From: DJ <dj@Rachels-MacBook-Air.local>
Date: Fri, 17 Apr 2026 09:47:33 -0700
Subject: [PATCH 10/13] fix(reusable): guard against empty sources_file in
 Phase 2 prompt

If a caller passes sources_file: '' the prompt previously rendered a
bare 'Read: ' instruction. Now uses a GitHub Actions expression to
branch: non-empty value emits the Read instruction; empty/omitted
emits a clear fallback note directing Mary to open web search and log
a warning in the step summary.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
---
 .github/workflows/feature-ideation-reusable.yml | 4 +---
 1 file changed, 1 insertion(+), 3 deletions(-)

diff --git a/.github/workflows/feature-ideation-reusable.yml b/.github/workflows/feature-ideation-reusable.yml
index aadaca7..8674931 100644
--- a/.github/workflows/feature-ideation-reusable.yml
+++ b/.github/workflows/feature-ideation-reusable.yml
@@ -312,9 +312,7 @@ jobs:
 
             Before running open-ended web searches, **check for a repo-local source list**:
 
-            ```
-            Read: ${{ inputs.sources_file }}
-            ```
+            ${{ inputs.sources_file != '' && format('```\nRead: {0}\n```', inputs.sources_file) || '> ⚠️ No `sources_file` input was provided. Proceed with open web search and log a warning in the step summary under "Source list status".' }}
 
             That file (if present) lists vendor blogs, RSS feeds, podcasts, and YouTube
             channels this repo's maintainers trust as primary signal sources, organised

From da7b2c93653a527e1dd31ca63a1f7142e1e0e604 Mon Sep 17 00:00:00 2001
From: DJ <dj@Rachels-MacBook-Air.local>
Date: Fri, 17 Apr 2026 09:50:24 -0700
Subject: [PATCH 11/13] fix(lint): move sources_file expression to env var to
 respect line-length

The format() expression was 241 chars, over the 200-char yamllint limit.
Moving it to SOURCES_INSTRUCTION in the step env block (where the
expression is still valid) and referencing $SOURCES_INSTRUCTION in the
prompt string brings all lines under 200 chars.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
---
 .github/workflows/feature-ideation-reusable.yml | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/.github/workflows/feature-ideation-reusable.yml b/.github/workflows/feature-ideation-reusable.yml
index 1f03aa7..2576f1f 100644
--- a/.github/workflows/feature-ideation-reusable.yml
+++ b/.github/workflows/feature-ideation-reusable.yml
@@ -212,6 +212,7 @@ jobs:
           MATCH_PLAN_PATH: ${{ runner.temp }}/match-plan.json
           TOOLING_DIR: ${{ github.workspace }}/.feature-ideation-tooling/.github/scripts/feature-ideation
           FOCUS_AREA: ${{ inputs.focus_area || '' }}
+          SOURCES_INSTRUCTION: ${{ inputs.sources_file != '' && format('```\nRead: {0}\n```', inputs.sources_file) || '> No sources_file provided — use open web search.' }}
           RESEARCH_DEPTH: ${{ inputs.research_depth }}
         uses: anthropics/claude-code-action@905d4eb99ab3d43143d74fb0dcae537f29ac330a # v1.0.97
         with:
@@ -312,7 +313,7 @@ jobs:
 
             Before running open-ended web searches, **check for a repo-local source list**:
 
-            ${{ inputs.sources_file != '' && format('```\nRead: {0}\n```', inputs.sources_file) || '> ⚠️ No `sources_file` input was provided. Proceed with open web search and log a warning in the step summary under "Source list status".' }}
+            $SOURCES_INSTRUCTION
 
             That file (if present) lists vendor blogs, RSS feeds, podcasts, and YouTube
             channels this repo's maintainers trust as primary signal sources, organised

From d3679931bc3d6d47f9444ffb7c4ab8c152e54f01 Mon Sep 17 00:00:00 2001
From: DJ <dj@Rachels-MacBook-Air.local>
Date: Fri, 17 Apr 2026 09:52:43 -0700
Subject: [PATCH 12/13] fix(lint): resolve YAML syntax error in sources_file
 prompt guard
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

The format() expression with backtick literals inside a GHA expression
caused a YAML mapping-value syntax error at parse time. Replaced with
a plain env var SOURCES_FILE_PATH + shell-style conditional in the prompt
text — no GHA expressions inside the multiline prompt string, fully
YAML-safe and under the 200-char line limit.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
---
 .github/workflows/feature-ideation-reusable.yml | 12 +++++++++---
 1 file changed, 9 insertions(+), 3 deletions(-)

diff --git a/.github/workflows/feature-ideation-reusable.yml b/.github/workflows/feature-ideation-reusable.yml
index 2576f1f..c158006 100644
--- a/.github/workflows/feature-ideation-reusable.yml
+++ b/.github/workflows/feature-ideation-reusable.yml
@@ -212,7 +212,7 @@ jobs:
           MATCH_PLAN_PATH: ${{ runner.temp }}/match-plan.json
           TOOLING_DIR: ${{ github.workspace }}/.feature-ideation-tooling/.github/scripts/feature-ideation
           FOCUS_AREA: ${{ inputs.focus_area || '' }}
-          SOURCES_INSTRUCTION: ${{ inputs.sources_file != '' && format('```\nRead: {0}\n```', inputs.sources_file) || '> No sources_file provided — use open web search.' }}
+          SOURCES_FILE_PATH: ${{ inputs.sources_file }}
           RESEARCH_DEPTH: ${{ inputs.research_depth }}
         uses: anthropics/claude-code-action@905d4eb99ab3d43143d74fb0dcae537f29ac330a # v1.0.97
         with:
@@ -311,9 +311,15 @@ jobs:
 
             ### Start from the repo-local Reputable Source List
 
-            Before running open-ended web searches, **check for a repo-local source list**:
+            Before running open-ended web searches, **check for a repo-local source list**.
+            If `$SOURCES_FILE_PATH` is non-empty, read it:
 
-            $SOURCES_INSTRUCTION
+            ```
+            Read: $SOURCES_FILE_PATH
+            ```
+
+            If the path is empty or the file does not exist, log a one-line warning
+            in the step summary under "Source list status" and proceed with open web search.
 
             That file (if present) lists vendor blogs, RSS feeds, podcasts, and YouTube
             channels this repo's maintainers trust as primary signal sources, organised

From 8ffa6924a8264f17d9612a63b1ae5b28f25fed2d Mon Sep 17 00:00:00 2001
From: DJ <dj@Rachels-MacBook-Air.local>
Date: Fri, 17 Apr 2026 10:01:17 -0700
Subject: [PATCH 13/13] feat(dotgithub): add feature-ideation caller stub for
 .github self-test
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Adds the Feature Research & Ideation workflow to the .github repo itself,
making it a BMAD-enabled consumer of its own reusable pipeline.

Key configuration:
- project_context: org-level DevX/tooling repo (CI standards, reusable
  workflows, BMAD framework, agent security)
- sources_file: 'standards/feature-ideation-sources.md' — the template
  lives right here, so no copy needed
- dry_run defaults to false (use workflow_dispatch input to enable)
- actions: read permission for feed checkpoint

Note: uses: SHA points to current v1. After this PR merges, bump the
v1 tag to the new merge commit and update the SHA here.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
---
 .github/workflows/feature-ideation.yml | 88 ++++++++++++++++++++++++++
 1 file changed, 88 insertions(+)
 create mode 100644 .github/workflows/feature-ideation.yml

diff --git a/.github/workflows/feature-ideation.yml b/.github/workflows/feature-ideation.yml
new file mode 100644
index 0000000..afea467
--- /dev/null
+++ b/.github/workflows/feature-ideation.yml
@@ -0,0 +1,88 @@
+# ─────────────────────────────────────────────────────────────────────────────
+# SOURCE OF TRUTH: petry-projects/.github/standards/workflows/feature-ideation.yml
+# Standard:        petry-projects/.github/standards/ci-standards.md#8
+# Reusable:        petry-projects/.github/.github/workflows/feature-ideation-reusable.yml
+#
+# AGENTS — READ BEFORE EDITING:
+#   • This file is a THIN CALLER STUB. The 5-phase ideation pipeline, the
+#     Opus 4.6 model selection, the github_token override, and the
+#     ANTHROPIC_MODEL env var all live in the reusable workflow above.
+#   • You MAY change: the `project_context` value and optionally the cron
+#     schedule.
+#   • You MUST NOT change: trigger event shape, the `uses:` line, the
+#     job-level `permissions:` block, or the `secrets:` block.
+#   • If you need different behaviour, open a PR against the reusable in
+#     this repo. The change will propagate after the v1 tag is bumped.
+# ─────────────────────────────────────────────────────────────────────────────
+name: Feature Research & Ideation (BMAD Analyst)
+
+on:
+  schedule:
+    - cron: '0 7 * * 5' # Friday 07:00 UTC (3 AM EDT / 2 AM EST)
+  workflow_dispatch:
+    inputs:
+      focus_area:
+        description: 'Optional focus area (e.g., "CI patterns", "agent security")'
+        required: false
+        type: string
+      research_depth:
+        description: 'Research depth'
+        required: false
+        default: 'standard'
+        type: choice
+        options:
+          - quick
+          - standard
+          - deep
+      dry_run:
+        description: 'Log Discussion mutations to artifact instead of writing live'
+        required: false
+        default: false
+        type: boolean
+
+permissions: {}
+
+concurrency:
+  group: feature-ideation
+  cancel-in-progress: false
+
+jobs:
+  ideate:
+    # Permissions cascade from the calling job to the reusable workflow.
+    # The reusable workflow's two jobs (gather-signals + analyze) need:
+    #   - contents:      read   (checkout, file reads)
+    #   - issues:        read   (signal collection)
+    #   - pull-requests: read   (signal collection)
+    #   - discussions:   write  (CRITICAL — create/update Discussion threads)
+    #   - actions:       read   (feed checkpoint via gh run list)
+    #   - id-token:      write  (claude-code-action OIDC for GitHub App token)
+    permissions:
+      contents: read
+      issues: read
+      pull-requests: read
+      discussions: write
+      actions: read
+      id-token: write
+    uses: petry-projects/.github/.github/workflows/feature-ideation-reusable.yml@208ec2d69b75227d375edf8745d84fbac05a76b2 # v1 — bump SHA after tag update
+    with:
+      project_context: |
+        petry-projects/.github is the org-level standards and tooling repository
+        for the petry-projects GitHub organisation. It owns the canonical CI/CD
+        standards (ci-standards.md), all reusable GitHub Actions workflows
+        (claude-code, feature-ideation, agent-shield, dependabot), the BMAD
+        Method agentic development framework, and org-wide security and
+        compliance tooling. Downstream consumers are internal product repos
+        (Broodly, TalkTerm, markets). Key trends to track: GitHub Actions
+        platform improvements (larger runners, step summaries, OIDC advances),
+        agentic CI patterns (LLM-driven PR review, automated ideation,
+        agent-shield threat models), AI-assisted code review tooling evolution
+        (CodeRabbit, Copilot Workspace), security hardening for AI-agent
+        workflows (prompt injection, supply-chain pinning, least-privilege
+        scopes), and developer-experience standards for LLM-heavy codebases.
+        No public users — this is internal DevX infrastructure.
+      sources_file: 'standards/feature-ideation-sources.md'
+      focus_area: ${{ inputs.focus_area || '' }}
+      research_depth: ${{ inputs.research_depth || 'standard' }}
+      dry_run: ${{ inputs.dry_run || false }}
+    secrets:
+      CLAUDE_CODE_OAUTH_TOKEN: ${{ secrets.CLAUDE_CODE_OAUTH_TOKEN }}