feat: add issue 26-04 (April 2026)

Publish the April 2026 magazine issue with content source, final PDF, README entry, and issues.json index update.

Author: VdustR

.claude/commands/magazine-collect.md

@@ -74,6 +74,12 @@ Issue identifier: $ARGUMENTS (if not provided, derive from current date — the
 | [#wg-ai-coding](https://chatbotgang.slack.com/archives/C08RN012FUN) | `C08RN012FUN` | AI-assisted development, coding agents, LLM tooling |
 | [#ref-design-system-sharing](https://chatbotgang.slack.com/archives/C01Q5QJCQTT) | `C01Q5QJCQTT` | Design system references, component patterns, UI/UX |
 | [#wg-design-system](https://chatbotgang.slack.com/archives/C069AKSL67N) | `C069AKSL67N` | Design system working group, implementation discussions |
+| [#proj-ai-lab](https://chatbotgang.slack.com/archives/C0A3WC5K9HR) | `C0A3WC5K9HR` | AI lab experiments — extract technical patterns, model usage, and tooling insights only |
+| [#prod-pillar-ai-solution](https://chatbotgang.slack.com/archives/C04QWM5BV7F) | `C04QWM5BV7F` | AI solution product pillar — extract technical/architectural discussions only, skip product feature updates |
+| [#proj-ai-the-aibility-team](https://chatbotgang.slack.com/archives/C08BG036EKD) | `C08BG036EKD` | AI-bility project — extract engineering practices and AI-assisted development patterns, skip product features |
+| [#team-eng-caac-frontend](https://chatbotgang.slack.com/archives/C04EHG9K0JK) | `C04EHG9K0JK` | CAAC frontend team — engineering discussions, internal decisions, technical project updates |
+
+**Filtering reminder for product/project channels** (`#proj-*`, `#prod-pillar-*`): these channels mix technical and product content. Apply the same filter as Phase 3 — keep tooling, architecture, DX, AI-assisted development patterns; skip product features, UI changes, business logic, release notes for end users.
 
 ### 2.2 Additional User Sources
 Ask the user for additional news sources beyond the defaults:

.claude/commands/magazine-edit.md

@@ -46,7 +46,7 @@ This is a **magazine**, not a software project. Approach it like a real art dire
 
 **Goal**: Read the collected content and define the issue's narrative arc.
 
-### 1.1 Read Content File
+### 1.1 Read Content Files
 
 **FIRST ACTION**: Read `{YY-MM}/content.md` (produced by `/magazine-collect`).
 
@@ -58,12 +58,16 @@ No content file found at {YY-MM}/content.md.
 Run /magazine-collect {YY-MM} first to gather content.
 ```
 
-Extract from the content file:
-- Issue metadata (ID, date range)
-- All sections and their content
-- Approved outline and headlines
-- **Suggested Image Concept** and **Visual Opportunities** per topic (guides Phase 4 asset production)
-- Clawd's Corner content (if present)
+**Multi-file content structure** (newer issues): if `content.md` is small and contains a "Content Index" table pointing to per-section files under `{YY-MM}/content/`, treat `content.md` as the index/outline-only file and read every file it lists (typically `content/ecosystem-news.md`, `content/feature-stories.md`, `content/project-insights.md`, `content/looking-ahead-events.md`, etc.). The split exists because the full content exceeds the editor's read-window — read the parts in sequence rather than re-merging them.
+
+**Single-file content structure** (older issues, e.g., 25-12 through 26-03): `content.md` contains everything inline; read just that file.
+
+Extract from all content files:
+- Issue metadata (ID, date range) — from `content.md` Meta section
+- Approved outline and headlines — from `content.md` Approved Outline section
+- All section content (Ecosystem News, Feature Stories, Project Insights, Looking Ahead, Events, Clawd's Corner) — from `content/*.md` if split, otherwise from `content.md`
+- **Suggested Image Concept** and **Visual Opportunities** / image briefs per topic (guides Phase 4 asset production)
+- **Editorial decisions in Meta / Research Assets** (e.g., per-issue overrides like "use `codex` CLI for image generation instead of `/cl-nanobanana`") — these override default Required Skills
 
 ### 1.2 Editorial Direction
 
@@ -224,7 +228,7 @@ By this phase, the creative direction is already confirmed through mockups. This
 ### 5.1 HTML Generation
 
 **Invoke `/frontend-design` skill** with:
-- The content from `{YY-MM}/content.md`
+- The content from `{YY-MM}/content.md` **plus all `{YY-MM}/content/*.md` files if the issue uses the split structure** (see Phase 1.1)
 - The confirmed visual direction per topic from Phase 2
 - The pacing plan from Phase 3
 - All generated visual assets from Phase 4

26-04/26-04.pdf

@@ -0,0 +1,83 @@
+# Frontend Technology Digest - 26-04
+
+## Meta
+
+- **Issue**: 26-04
+- **Date Range**: April 2026
+- **Sections**: Ecosystem News, Project Insights, Feature Story, Looking Ahead, Events & Announcements
+- **Collected**: 2026-05-04
+- **Research depth**: 15 topics researched, 4 deep-dives completed
+- **Source channels** (Slack): #team-eng-frontend-sharing, #team-eng-frontend, #wg-ai-coding, #ref-design-system-sharing, #wg-design-system, #proj-ai-lab, #prod-pillar-ai-solution, #proj-ai-the-aibility-team, #team-eng-caac-frontend (322 messages, 13 expanded threads)
+- **Source repos** (GitHub, April 2026): Grazioso (386 PRs, 65.0% AI-coauthored), Zeffiroso (159 PRs, 47.8%), Vivace (26 PRs, 88.5%), Polifonia (21 PRs, 69.2%)
+- **Editorial theme**: April was the month the AI-first dev environment stopped being a thesis and started being the floor — Anthropic shipped the infrastructure (Managed Agents, Routines, Opus 4.7), the team rewrote its own conventions to match (PR template deleted, .vscode/ tombstoned, skills-first migration), and the wider ecosystem scrambled to keep up (Codex parity, Gemini Enterprise Agent Platform, Vercel breach via AI tool supply chain).
+
+---
+
+## Content Index
+
+This file is the entry point. Detailed content is split into per-section files under `content/` to keep each file under the editor's read-window:
+
+| File | Section | Lines |
+|---|---|---:|
+| [content/ecosystem-news.md](content/ecosystem-news.md) | 15 ecosystem news entries (4 deep-dives + 11 standard/brief) | ~400 |
+| [content/feature-stories.md](content/feature-stories.md) | Three Feature Stories: F1 "IDE 已死", F2 Jack Lee's MAAC playbook, F3 OpenSpec rollout | ~250 |
+| [content/project-insights.md](content/project-insights.md) | Per-repo April analysis (Grazioso / Zeffiroso / Vivace / Polifonia) + cross-cutting trends | ~65 |
+| [content/looking-ahead-events.md](content/looking-ahead-events.md) | Looking Ahead, Events & Announcements (incl. brief mentions), Clawd's Corner | ~90 |
+
+**For `/magazine-edit`**: read all four content files in sequence. The Approved Outline below sets pacing, headline order, theme, and visual briefs.
+
+---
+
+## Approved Outline
+
+### Cover
+
+- **Theme**: "The dev environment goes agent-shaped" — April's stories all rhyme on the same beat: tools that used to be for humans are being rebuilt assuming the primary consumer is an agent. Managed Agents is the substrate; Skills-first is the philosophy made operational; OpenSpec is the contract layer; cl-locales / Outline MCP / public NPM packages are the internal plumbing; Codex and Gemini are the competitive scaffolding that makes the bet less risky to make.
+- **Suggested Image Concept**: A familiar dev environment (terminal + IDE + Slack) with the IDE pane visibly fading or being deconstructed — the keyboard's keys lifting away one by one — while a Claw'd-mascot's claw orchestrates several glowing agent windows that have *replaced* the IDE. Salmon/seafood color tone for Claw'd. The vibe is "the desk has been cleared and rebuilt, and you didn't notice when."
+- **Alternative Cover Concept**: Clawd at a control panel with multiple monitors — each showing a different parallel session/routine/skill running. Vibe: NASA mission control, but for a single developer. Tagline option: "April 2026 — when one developer became a fleet."
+
+### Headlines (in priority order)
+
+1. **F1: "IDE 已死" — How One PR Made April's Biggest Story Concrete** — Feature Story (philosophy)
+2. **F2: AI Becomes the Coworker With a Schedule — Jack Lee's MAAC Playbook** — Feature Story (day-to-day)
+3. **F3: OpenSpec Quietly Lands in Four Repos** — Feature Story (institution)
+4. **Claude Managed Agents: Anthropic Ships the Engine** — Ecosystem News deep-dive
+5. **Claude Opus 4.7 + The Three-Bug Postmortem** — Ecosystem News deep-dive
+6. **TypeScript 7 Beta Lands in Go** — Ecosystem News
+7. **Codex Catches Up: GPT-5.5 and the End of Single-Tool Dominance** — Ecosystem News
+8. **Vercel: Breach + IPO, Same Month, Same Cause** — Ecosystem News
+9. **The Project Insights Issue — 47–88% AI Co-Authored, by Project** — Project Insights opener
+10. **Looking Ahead: TS 7 Stable, Mythos GA, Outline as SSOT** — Looking Ahead
+
+### Section Order
+
+1. Ecosystem News (15 topics, deep-dives 1-4 first)
+2. Feature Stories — three pieces (F1 philosophy → F2 day-to-day → F3 institution); pacing: F1 dense, F2 narrative-driven with code blocks for breather, F3 structured/tabular
+3. Project Insights (4 repos + cross-cutting)
+4. Events & Announcements
+5. Looking Ahead
+6. Clawd's Corner (closer)
+
+### Cross-cutting Themes
+
+- **Theme A: AI as substrate, not assistant** — Managed Agents, Skills-first, OpenSpec, cl-locales, Outline MCP, the Vercel agent-deployment stat. The agent isn't a feature; it's the floor.
+- **Theme B: The death of the human-shaped IDE** — Skills-first, Zed 1.0, JetBrains pushback, Codex desktop / Cowork, Claude Design — five stories, one direction.
+- **Theme C: Speed-vs-security strapped together** — Vercel breach + IPO, OpenClaw CVE flood, HERMES.md billing bug, Pentagon supply-chain flagging. Agent ecosystems are growing faster than their governance.
+- **Theme D: Multi-vendor pragmatism** — Codex + Claude Code + Gemini Enterprise + Bedrock AgentCore. The era of single-tool dominance is over; portability via skills and MCP is the bet.
+
+### Research Assets
+
+- Total topics researched: **15** (4 deep-dive, 11 standard/brief)
+- Slack data: 322 messages across 9 channels (April 1-30, 2026), 13 expanded threads
+- GitHub data: 4 repos, full-month commits + PR analysis, AI co-authoring rates
+- Asset files: TBD — editor to capture screenshots from the supplementary URLs in `content/ecosystem-news.md` (Anthropic blog architecture diagrams, Wired Notion demo, HN top comments, Reddit r/ClaudeCode, Zed 1.0 announcement, Steve Yegge clip, JetBrains blog, agentskills.io carousel, Vercel attack chain visual)
+- **Image generation tool for this issue: `codex` CLI (OpenAI), NOT `/cl-nanobanana`.** Editorial decision for 26-04 — A/B test the OpenAI stack against the team's default Nano Banana workflow. `codex --help` for invocation; image gen via the underlying model (`gpt-image-1` / DALL-E 3 family). All AI-generated images for this issue should be produced through Codex; record prompts and any tool-specific quirks for the post-issue retro.
+- Suggested AI-image briefs (to be produced via `codex`):
+  - **Cover**: Clawd in a "deconstructed IDE" scene — see Cover concept above. Salmon/seafood color tone for Clawd. Pixel-art mascot, otherwise illustrative/editorial style.
+  - **F1 Feature Story opener**: Pixel-art tombstone for `.vscode/component.code-snippets` and `.vscode/launch.json` (born when each file was added, died April 18, 2026). Epitaph: *"Served humans well. Agents never called."*
+  - **F2 Feature Story opener**: Clawd seated at a calendar with "Sentry triage 09:00", "Bundle CI", "PR review" appointments visible — agent-as-coworker visual.
+  - **F3 Feature Story opener**: A grid of four repos (Vivace / Zeffiroso / Grazioso / Polifonia) with the same `/opsx` ritual happening in each — the institution-level pattern made visible.
+  - **Managed Agents**: cattle-vs-pets container metaphor; cow icon vs pet dog/cat for the stateless-vs-curated tradeoff.
+  - **Opus 4.7 postmortem**: three-bug Gantt timeline visual with the March 4 / March 26 / April 16 deploys and April 7 / April 10 / April 20 reverts.
+  - **Vercel breach**: 5-node attack chain (Roblox cheat → Lumma → Context.ai employee → OAuth app → Vercel Workspace).
+  - **Skills-first / agentskills.io carousel**: 30-platform logo grid as portability proof.