Add issue-driven blog capture and weekly draft automation

[Copilot]

Create a repeatable path from a labeled GitHub issue to a blog post draft PR. The repo now captures blog ideas as structured notes and, on a weekly schedule, turns the oldest open blog issue into a starter post for review.

• Issue capture workflow

  • Triggers on blog-labeled issues.
  • Writes the issue into an internal capture note for traceability and reuse.
  • Opens a PR so captured ideas stay reviewable in the repo flow.

• Weekly draft workflow

  • Runs every Wednesday morning UTC.
  • Selects the oldest open blog issue.
  • Generates a draft post scaffold and opens a PR for editorial review.

• Shared automation helper

  • Added a small Node script to normalize issue metadata into:
    • capture notes
    • blog draft front matter and starter content
  • Keeps the workflow YAML thin and the content shape consistent.

• Repo guidance

  • Documented the blog label workflow and weekly handoff in the website README.

Example draft shape:

---
slug: /2026-10-06-some-blog-idea
date: 2026-10-06
tags:
  - ai
  - blog
  - github-actions
---

# Some Blog Idea

This draft starts from GitHub issue #92 and turns the request into a publishable blog post outline.

• Fixes Actions to capture blog material and package into blog #92

[dfberry]

The creation of the blog post should use AI to make sure the blog post sounds personal and engaging instead of a listing of the items from the issues.

[Copilot]

The creation of the blog post should use AI to make sure the blog post sounds personal and engaging instead of a listing of the items from the issues.

Updated the weekly draft path to call GitHub Models and generate the post body in a personal, engaging voice. Commit: a60017b.

[dfberry]

The blog generation should be an agentic workflow file with a compiled version checked in. It needs a human gate to review the generated content before it moved to undrafted.

[Copilot]

Copilot review overview

🟡 Changes recommended

An issue-selection bug (per_page: 1 defeating the PR filter), a filler draft that would publish to the live site, and two overlapping weekly draft workflows that would open duplicate PRs all need to be resolved first.

Review effort: Balanced
Findings: 3

Open (3)

• Eliminate duplicate weekly blog draft workflow · New
• Fetch more than one issue before filtering out PRs · New
• Remove accidental fallback draft from published blog content · New

What changed in this PR

This PR adds automation to turn labeled GitHub issues into blog post drafts for the Docusaurus-based personal site under website/. It introduces an issue-capture workflow, a weekly draft workflow, a shared Node helper that normalizes issue metadata into capture notes and blog front matter, and README guidance. Notably, it adds two parallel implementations of the weekly draft step: a hand-written workflow (draft-weekly-blog-post.yml) backed by the Node script + GitHub Models, and a gh-aw agentic workflow (draft-weekly-blog-post.md + compiled .lock.yml).

Changes:

• Add capture-blog-ideas.yml (on blog-labeled issues) and draft-weekly-blog-post.yml (weekly) plus a gh-aw agentic variant, all opening PRs.
• Add .github/scripts/blog-automation.mjs to render capture notes and blog draft front matter/body (with GitHub Models call and a static fallback).
• Document the workflow in website/README.md; include a sample blog file.

File	Description
.github/​scripts/​blog-automation.mjs	Core helper: slugify, excerpt, capture/draft markdown rendering, model call with fallback.
.github/​workflows/​capture-blog-ideas.yml	Captures blog-labeled issues into notes and opens a PR.
.github/​workflows/​draft-weekly-blog-post.yml	Weekly node-script draft workflow (contains the per_page selection bug).
.github/​workflows/​draft-weekly-blog-post.md	gh-aw agentic source that overlaps with the .yml draft workflow.
.github/​workflows/​draft-weekly-blog-post.lock.yml	Generated gh-aw lock file (linguist-generated).
.github/​aw/​actions-lock.json	gh-aw action pin for the setup action.
.gitattributes	Marks *.lock.yml as generated.
website/​blog/​2026-10-06-ai-agentic-blog-testing.md	Appears to be an accidentally committed fallback/filler draft.
website/​README.md	Documents the blog-label capture and weekly handoff.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.