TEST(875-revalidate): bridge fix

[don-petry]

Validation idea for the discussion→dispatch redispatch bridge (#963 / PR #971). Proposal: add a lightweight per-repo health badge that summarizes the latest feature-ideation run status and last-enhanced Idea timestamp, surfaced in the org profile README so operators can see at a glance whether the single-idea enhancement path is healthy without opening the Actions tab. This is a throwaway discussion created solely to confirm the redispatch bridge no longer crashes on discussion:created events.

[github-actions[bot]]

Enhancement: Per-Repo Feature-Ideation Health Badge

Sharper Problem Framing

The feature-ideation pipeline now spans three event paths (weekly cron, single-idea discussion:created dispatch, and backlog enhancement sweep), each with its own failure modes. Today, the only way to confirm the pipeline is healthy is to open the Actions tab, visually scan run history, or wait for the daily fleet-monitor to surface a failure as an issue. There is no ambient, at-a-glance signal. This is a classic observability gap: the existing health monitors (daily-pr-review-health, actions-fleet-monitor, docs-health-check) all produce reactive artefacts (issues, step summaries) rather than a persistent status surface. A health badge would bridge that gap — a continuously-updated visual indicator that operators can check from the org README without navigating to the Actions tab.

Prior Art & Competitive Signal

Approach	How it works	Limitations
GitHub native workflow badge (actions/workflows/X/badge.svg)	Shows pass/fail of the last run on the default branch. Zero setup.	Binary pass/fail only — no timestamp, no run count, no per-path breakdown. Cannot distinguish "last cron succeeded but last single-idea dispatch failed."
shields.io dynamic endpoint (Schneegans/dynamic-badges-action)	A post-run step writes a JSON payload ({schemaVersion, label, message, color}) to a GitHub Gist. shields.io renders the badge from the Gist URL.	Requires a PAT with gist:write scope. Adds an external dependency (shields.io uptime). One badge per Gist file, so multi-metric dashboards need multiple Gist files or a custom endpoint.
Repo-local SVG badge (e.g., Build-A-Badge)	Generates an SVG file and commits it to the repo. No external service dependency.	Produces a commit per update — noisy for a weekly workflow. Pollutes git history.
Agentic observability platforms (AgentOps, Langfuse, Arize Phoenix, OpenSearch Agent Health)	Full trace-level observability for autonomous agents — cost tracking, latency, tool failures, anomaly detection. Enterprise-grade but heavy.	Overkill for a badge. These are valuable for the pr-review engine's multi-tier pipeline but not for a binary "is ideation healthy?" signal.

Key insight: GitHub's native badge is the lowest-friction option but it is too coarse — it cannot express "last enhanced Idea timestamp" or distinguish per-event-path health. The shields.io Gist approach adds one workflow step and one secret but delivers rich, customisable content.

Options Table

Option	Implementation	Pros	Cons	Recommended?
A. Native workflow badge only	Add  to org README	Zero maintenance, no secrets, works today	Binary pass/fail; no timestamp; cannot show single-idea vs cron health separately	For MVP
B. shields.io Gist endpoint	Add a post-run step that writes {label, message, color} JSON to a Gist via Schneegans/dynamic-badges-action; embed shields.io badge in org README	Rich content (timestamp, count, color-coded severity); one-step addition to existing workflow	Needs a gist:write PAT; depends on shields.io uptime; Gist is public by default (fine for status data, but worth noting)	For v1
C. Composite dashboard page	A dedicated scripts/ideation-health-dashboard.sh that queries the workflow-runs API, builds an HTML/MD summary, and commits it as a GitHub Pages page or wiki entry	Full control; can aggregate all agent workflows, not just ideation	Significant implementation effort; commit noise or Pages hosting; over-scoped for the stated problem	Defer
D. Embed in fleet-monitor output	Extend fleet_monitor.sh / fleet_report.sh to include a feature-ideation section in the daily fleet report issue	Reuses existing infrastructure; no new workflow	Not a badge — still reactive (issue-based); not visible from org README	Complement, not replace

Risks & Unknowns

1. Gist PAT scope creep. The gist:write PAT can read/write all Gists on the account. Mitigate: use the machine-user bot account (DON_PETRY_BOT) whose PAT already exists for cross-repo operations, and limit the Gist to a single known ID.
2. shields.io availability. shields.io has had intermittent outages (see their status page history). Mitigate: the badge degrades gracefully — a broken image is annoying but not harmful. Consider self-hosted shields if this becomes a frequent problem.
3. Org profile README location. The .github-private/profile/README.md is the member-only org overview. This repo currently has no profile/ directory. Creating one is trivial but it is a new artefact to maintain.
4. Badge staleness. If the weekly cron is disabled or the workflow is broken for weeks, the badge will show stale data. Mitigate: include the timestamp in the badge message (e.g., "✓ Jun 27") so staleness is self-evident.
5. Multi-path granularity. A single badge cannot easily convey "cron OK, single-idea failed." Consider two badges (one per path) or a compound message like "cron ✓ · dispatch ✗."

Phased Validation / Pilot Path

Phase 0 — Baseline (no code):
Manually check the Actions tab for the last 4 feature-ideation runs. Record how long it takes and how many clicks. This is the "before" measurement.

Phase 1 — Native badge MVP (1 PR):
Add the GitHub-native workflow badge to the repo README.md. This works today with zero infrastructure. Validates that the team actually looks at it.

Phase 2 — Rich badge via Gist (1 PR):
Add a post-run step to the feature-ideation reusable workflow that writes a JSON payload to a Gist. The payload includes: status (pass/fail/partial), last_run (ISO timestamp), last_enhanced_idea (Discussion number + timestamp), and color (green/yellow/red). Embed the shields.io badge in the org profile README.

Phase 3 — Multi-path breakdown (1 PR):
Split into two badges: "Ideation Cron" and "Ideation Dispatch." Add a third "Last Enhanced" badge showing the most recent Discussion number and date.

Phase 4 — Fleet-wide badge row (future):
Extend the pattern to pr-review, dev-lead, fleet-monitor, and initiative-driver workflows. The org profile README becomes a lightweight operations dashboard.

Success Metrics

Metric	Target	How to measure
Time-to-awareness of a broken ideation run	< 30 seconds (vs. ~2 min navigating Actions tab)	Operator self-report after Phase 1 pilot
Badge freshness	Updated within 10 min of every ideation run	Timestamp in badge message vs. workflow run completion time
False-positive rate	0 — badge should never show red when the run succeeded	Compare badge state to workflow conclusion via API spot-checks
Adoption signal	Badge referenced in at least 1 incident post-mortem or standup within 4 weeks	Search Discussions/issues for badge mentions