docs: add WCEU 2026 talk asset pack#751
Conversation
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
|
Warning Review limit reached
More reviews will be available in 22 minutes and 8 seconds. Learn how PR review limits work. Your organization has run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Repository YAML (base), Organization UI (inherited) Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (3)
📝 WalkthroughWalkthroughThis PR introduces a comprehensive asset pack for a 25-minute WordCamp Europe 2026 talk on GitHub governance and control planes. It adds 22 new markdown documents covering talk structure, a complete 20-slide deck specification, NotebookLM research prompts, and website planning materials. ChangesWCEU 2026 Talk Asset Pack
Estimated code review effort🎯 2 (Simple) | ⏱️ ~12 minutes Possibly related PRs
Suggested labels
Suggested reviewers
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
coderabbitai
Bot
added
priority:normal
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request introduces the WordCamp Europe 2026 Talk Asset Pack, which contains a comprehensive set of planning, research, and content assets such as slide briefs, a 25-minute talk outline, NotebookLM prompts, and a mini-site plan. The talk details the evolution of a central .github repository into installable plugin packs for AI coding tools. The review feedback highlights a minor naming convention inconsistency where references to docs/override-policy.md should be updated to uppercase (docs/OVERRIDE_POLICY.md) to align with the repository's standards for documentation files.
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.
| | 15 | [slide-08-multi-platform-parity.md](../slides/slide-08-multi-platform-parity.md) | Multi-platform parity | `plugins/lightspeed-github-ops/*.json`, `skills/SKILL_REGISTRY.json` | | ||
| | 16 | [slide-09-quality-and-release-gates.md](../slides/slide-09-quality-and-release-gates.md) | Quality and release | `docs/RELEASE_PROCESS.md`, `docs/TESTING.md`, `.github/workflows/` | | ||
| | 17 | [slide-10-metrics-and-governance-outcomes.md](../slides/slide-10-metrics-and-governance-outcomes.md) | Metrics and governance | `docs/METRICS.md`, `docs/GOVERNANCE_REVISION_LOG.md` | | ||
| | 18 | [slide-11-lessons-and-anti-patterns.md](../slides/slide-11-lessons-and-anti-patterns.md) | Lessons learned | `docs/override-policy.md`, `instructions/spec-driven-workflow.instructions.md` | |
There was a problem hiding this comment.
According to the repository's general rules, documentation and governance files in the docs/ directory must use UPPERCASE naming with underscores (e.g., OVERRIDE_POLICY.md). Please update the reference to docs/override-policy.md to docs/OVERRIDE_POLICY.md to maintain consistency with this naming convention.
Suggested change:
| 18 | [slide-11-lessons-and-anti-patterns.md](../slides/slide-11-lessons-and-anti-patterns.md) | Lessons learned | `docs/OVERRIDE_POLICY.md`, `instructions/spec-driven-workflow.instructions.md` |References
- Documentation and governance files in the
docs/directory must use UPPERCASE naming with underscores (e.g.,GOVERNANCE_REVISION_LOG.md), as the lowercase-with-hyphens naming convention applies to other asset types and not todocs/files.
| - Pair each anti-pattern with a mitigation. | ||
|
|
||
| ## Evidence anchors | ||
|
|
There was a problem hiding this comment.
According to the repository's general rules, documentation and governance files in the docs/ directory must use UPPERCASE naming with underscores (e.g., OVERRIDE_POLICY.md). Please update the reference to docs/override-policy.md to docs/OVERRIDE_POLICY.md to maintain consistency with this naming convention.
Suggested change:
- `docs/OVERRIDE_POLICY.md`References
- Documentation and governance files in the
docs/directory must use UPPERCASE naming with underscores (e.g.,GOVERNANCE_REVISION_LOG.md), as the lowercase-with-hyphens naming convention applies to other asset types and not todocs/files.
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Note
Due to the large number of review comments, Critical severity comments were prioritized as inline comments.
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (2)
wceu-2026/website/page-copy-starter.md (1)
33-33:⚠️ Potential issue | 🟡 Minor | ⚡ Quick winAdd trailing newline at end of file.
Markdown files should end with a blank line for POSIX compliance and consistent diff behaviour.
🎯 Proposed fix
This work was significantly inspired by `github/awesome-copilot`, whose open practices and examples helped shape our approach. +🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@wceu-2026/website/page-copy-starter.md` at line 33, Add a single trailing newline character at the end of the Markdown file so the file ends with a blank line (POSIX-compliant) to ensure consistent diffs and tooling behavior; simply edit the file and place one newline after the last line of content.wceu-2026/website/mini-site-plan.md (1)
48-48:⚠️ Potential issue | 🟡 Minor | ⚡ Quick winAdd trailing newline at end of file.
Markdown files should end with a blank line for POSIX compliance and consistent diff behaviour.
🎯 Proposed fix
"This work was informed and inspired by `github/awesome-copilot` and the wider open-source Copilot ecosystem." +🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@wceu-2026/website/mini-site-plan.md` at line 48, Add a single trailing newline at the end of the Markdown file mini-site-plan.md so the file ends with a blank line (POSIX-compliant EOF); simply open mini-site-plan.md and ensure there is one empty line after the last line of content.
🟠 Major comments (21)
wceu-2026/references/repo-source-index.md-1-6 (1)
1-6:⚠️ Potential issue | 🟠 Major | ⚡ Quick winMissing required frontmatter fields! 🎯
This reference index needs the complete set of frontmatter fields. Add
file_type,version,tags,status,stability, anddomainto match the repository standards.📋 Proposed fix to add missing frontmatter fields
--- +file_type: "documentation" title: "Repo Source Index" description: "Curated source index for talk claims. Only references files inside lightspeedwp/.github." +version: "1.0" last_updated: "2026-05-28" owners: ["Ash Shaw"] +tags: ["reference", "index", "sources", "wceu-2026"] +status: "active" +stability: "stable" +domain: "documentation" ---As per coding guidelines: "All
.mdfiles in this repository should include YAML frontmatter with required fields: file_type, title, description, version, last_updated, owners, tags, status, stability, domain".🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@wceu-2026/references/repo-source-index.md` around lines 1 - 6, The YAML frontmatter for repo-source-index.md is missing required fields; update the existing frontmatter block (the lines starting with --- and the current keys title, description, last_updated, owners) to also include file_type, version, tags, status, stability, and domain, ensuring each is a valid YAML key with appropriate values (e.g., file_type: "reference", version: "1.0.0" or similar, tags: [ ... ], status: "draft|published", stability: "stable|experimental", domain: "wceu-2026" ) and keep the last_updated and owners keys intact; preserve proper YAML formatting and quoting where needed.wceu-2026/notebooklm/source-ingestion-checklist.md-1-6 (1)
1-6:⚠️ Potential issue | 🟠 Major | ⚡ Quick winMissing required frontmatter fields! 🎯
Let's round out this frontmatter with the missing required fields:
file_type,version,tags,status,stability, anddomain.📋 Proposed fix to add missing frontmatter fields
--- +file_type: "documentation" title: "NotebookLM Source Ingestion Checklist" description: "Checklist to ensure NotebookLM only ingests approved repository sources for this talk." +version: "1.0" last_updated: "2026-05-28" owners: ["Ash Shaw"] +tags: ["notebooklm", "checklist", "sources", "wceu-2026"] +status: "active" +stability: "stable" +domain: "research" ---As per coding guidelines: "All
.mdfiles in this repository should include YAML frontmatter with required fields: file_type, title, description, version, last_updated, owners, tags, status, stability, domain".🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@wceu-2026/notebooklm/source-ingestion-checklist.md` around lines 1 - 6, The frontmatter block for NotebookLM Source Ingestion Checklist is missing required YAML fields; update the top YAML frontmatter (the existing keys title, description, last_updated, owners) to also include the required keys file_type, version, tags, status, stability, and domain with appropriate values (e.g., file_type: "checklist", semantic version for version, an array for tags, an allowed status string, stability level, and a domain string) so the file conforms to repository guidelines and validation; ensure the keys are present at the top of the file and formatted as YAML.wceu-2026/README.md-1-6 (1)
1-6:⚠️ Potential issue | 🟠 Major | ⚡ Quick winMissing required frontmatter fields! 🎯
Your frontmatter's looking a bit sparse, mate. According to the coding guidelines, all
.mdfiles must include these fields:file_type,title,description,version,last_updated,owners,tags,status,stability, anddomain. You've gottitle,description,last_updated, andownerssorted, but you're missing the rest.The validation script (as shown in the context snippets) will flag this and generate warnings, so let's get these added before merge!
📋 Proposed fix to add missing frontmatter fields
--- +file_type: "documentation" title: "WCEU 2026 Talk Asset Pack" description: "Working assets for the WordCamp Europe 2026 talk on evolving lightspeedwp/.github into an installable AI-ops and governance plugin platform." +version: "1.0" last_updated: "2026-05-28" owners: ["Ash Shaw"] +tags: ["wceu-2026", "talk", "conference", "documentation"] +status: "active" +stability: "stable" +domain: "documentation" ---As per coding guidelines: "All
.mdfiles in this repository should include YAML frontmatter with required fields: file_type, title, description, version, last_updated, owners, tags, status, stability, domain".🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@wceu-2026/README.md` around lines 1 - 6, The frontmatter in README.md is missing required fields causing validation warnings; update the YAML frontmatter block (the existing --- title/description/last_updated/owners section) to include the missing keys file_type, version, tags, status, stability, and domain, populate them with appropriate values (e.g., file_type: "doc", version: "1.0.0", tags: ["wceu","talk"], status: "draft" or "published", stability: "experimental" or "stable", domain: "events" or appropriate), keep the existing title/description/last_updated/owners entries unchanged, and ensure the frontmatter remains valid YAML bounded by the same --- delimiters so the repository validation script recognizes all required fields.wceu-2026/talk-outline-25min.md-1-6 (1)
1-6:⚠️ Potential issue | 🟠 Major | ⚡ Quick winMissing required frontmatter fields! 🎯
Last one! Your talk outline needs the full set of frontmatter fields. Add
file_type,version,tags,status,stability, anddomainto complete the metadata.📋 Proposed fix to add missing frontmatter fields
--- +file_type: "documentation" title: "Talk Outline (25 Minutes)" description: "Speaker outline for WCEU 2026: from central .github governance repo to installable AI-ops plugin packs." +version: "1.0" last_updated: "2026-05-28" owners: ["Ash Shaw"] +tags: ["talk", "outline", "wceu-2026", "conference"] +status: "active" +stability: "stable" +domain: "documentation" ---As per coding guidelines: "All
.mdfiles in this repository should include YAML frontmatter with required fields: file_type, title, description, version, last_updated, owners, tags, status, stability, domain".🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@wceu-2026/talk-outline-25min.md` around lines 1 - 6, The frontmatter block at the top of wceu-2026/talk-outline-25min.md is missing required fields; update the YAML frontmatter (the top --- block) to include the fields file_type, version, tags, status, stability, and domain in addition to the existing title, description, last_updated, and owners; ensure each new field uses appropriate values (e.g., file_type: "talk-outline", version: "1.0", tags: ["ai-ops","governance"], status: "draft" or "final", stability: "experimental" or "stable", domain: "conference") so the file complies with the repository rule that all .md files include those required frontmatter keys.wceu-2026/notebooklm/deep-research-prompt.md-1-6 (1)
1-6:⚠️ Potential issue | 🟠 Major | ⚡ Quick winMissing required frontmatter fields! 🎯
Same story here—your frontmatter needs the full complement of required fields. Add
file_type,version,tags,status,stability, anddomainto keep the validation gods happy.📋 Proposed fix to add missing frontmatter fields
--- +file_type: "prompt" title: "NotebookLM Deep Research Prompt" description: "Prompt for NotebookLM to analyse the talk direction using only lightspeedwp/.github files and this wceu-2026 asset pack." +version: "1.0" last_updated: "2026-05-28" owners: ["Ash Shaw"] +tags: ["notebooklm", "research", "prompt", "wceu-2026"] +status: "active" +stability: "stable" +domain: "research" ---As per coding guidelines: "All
.mdfiles in this repository should include YAML frontmatter with required fields: file_type, title, description, version, last_updated, owners, tags, status, stability, domain".🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@wceu-2026/notebooklm/deep-research-prompt.md` around lines 1 - 6, The frontmatter in the NotebookLM Deep Research Prompt is missing required YAML keys; update the existing frontmatter block (which already contains title, description, last_updated, owners) to also include file_type, version, tags, status, stability, and domain with appropriate values (e.g., file_type: "prompt", version: "1.0.0", tags: ["research","notebooklm"], status: "draft" or "approved", stability: "experimental" or "stable", domain: "wceu-2026"); keep existing fields intact and follow the same YAML formatting style so the file validates against the repository frontmatter rules.wceu-2026/references/slide-to-source-mapping.md-1-6 (1)
1-6:⚠️ Potential issue | 🟠 Major | ⚡ Quick winMissing required frontmatter fields! 🎯
Your slide mapping's brilliant, but the frontmatter needs completing! Add
file_type,version,tags,status,stability, anddomainto align with the repository standards.📋 Proposed fix to add missing frontmatter fields
--- +file_type: "documentation" title: "Slide to Source Mapping" description: "Fast mapping from each slide to supporting repository files." +version: "1.0" last_updated: "2026-05-28" owners: ["Ash Shaw"] +tags: ["reference", "mapping", "slides", "wceu-2026"] +status: "active" +stability: "stable" +domain: "documentation" ---As per coding guidelines: "All
.mdfiles in this repository should include YAML frontmatter with required fields: file_type, title, description, version, last_updated, owners, tags, status, stability, domain".🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@wceu-2026/references/slide-to-source-mapping.md` around lines 1 - 6, The frontmatter is missing required YAML fields: add file_type, version, tags, status, stability, and domain to the existing frontmatter block (keeping title, description, last_updated, and owners intact); ensure tags and owners are YAML lists, version follows semantic format (e.g., "1.0.0"), and the new fields are placed in the top YAML block so the parser recognizes them for slide-to-source-mapping.md.wceu-2026/website/page-copy-starter.md-1-6 (1)
1-6:⚠️ Potential issue | 🟠 Major | ⚡ Quick winMissing required frontmatter fields.
The coding guidelines mandate that all
.mdfiles include these frontmatter fields:file_type,title,description,version,last_updated,owners,tags,status,stability, anddomain. This file is missingfile_type,version,tags,status,stability, anddomain.✨ Proposed fix to add missing frontmatter fields
--- +file_type: "content" title: "Page Copy Starter" description: "Draft copy scaffolding for mini website pages based on the talk narrative." +version: "1.0.0" last_updated: "2026-05-28" owners: ["Ash Shaw"] +tags: ["wceu-2026", "website", "copy", "content"] +status: "draft" +stability: "stable" +domain: "documentation" ---As per coding guidelines: "All
.mdfiles in this repository should include YAML frontmatter with required fields: file_type, title, description, version, last_updated, owners, tags, status, stability, domain".🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@wceu-2026/website/page-copy-starter.md` around lines 1 - 6, Update the YAML frontmatter to include all required keys: file_type, version, tags, status, stability, and domain (in addition to the existing title, description, last_updated, and owners) making sure the frontmatter block remains wrapped with --- lines and values are valid YAML (use a string or list for tags/owners and sensible placeholder values like "draft" or "TBD" for version/status/stability/domain until finalized). Ensure you preserve existing fields (title, description, last_updated, owners) and add the new keys using the same key style used in the current frontmatter.wceu-2026/website/mini-site-plan.md-1-6 (1)
1-6:⚠️ Potential issue | 🟠 Major | ⚡ Quick winMissing required frontmatter fields.
The coding guidelines mandate that all
.mdfiles include these frontmatter fields:file_type,title,description,version,last_updated,owners,tags,status,stability, anddomain. This file is missingfile_type,version,tags,status,stability, anddomain.✨ Proposed fix to add missing frontmatter fields
--- +file_type: "planning" title: "Mini Website Plan" description: "Information architecture and content requirements for a mini website explaining the WCEU 2026 talk." +version: "1.0.0" last_updated: "2026-05-28" owners: ["Ash Shaw"] +tags: ["wceu-2026", "website", "planning", "content-strategy"] +status: "draft" +stability: "stable" +domain: "documentation" ---As per coding guidelines: "All
.mdfiles in this repository should include YAML frontmatter with required fields: file_type, title, description, version, last_updated, owners, tags, status, stability, domain".🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@wceu-2026/website/mini-site-plan.md` around lines 1 - 6, The frontmatter in mini-site-plan.md is missing required fields; update the YAML block that currently contains title, description, last_updated, and owners to also include file_type, version, tags, status, stability, and domain (keeping existing values for title/description/last_updated/owners), ensure tags is a list, version follows semantic format (e.g., "1.0.0"), and status/stability/domain use the repo's allowed values so the frontmatter (around the title/description/last_updated/owners entries) conforms to the required schema.wceu-2026/slides/slide-02-why-github-control-plane.md-1-6 (1)
1-6:⚠️ Potential issue | 🟠 Major | ⚡ Quick winMissing required frontmatter fields per schema and guidelines.
The frontmatter is missing several required fields:
file_type(required by.schemas/frontmatter.schema.json)version,tags,status,stability,domain(required by coding guidelines for all.mdfiles)These fields ensure proper schema validation and consistent metadata across documentation.
✨ Suggested frontmatter structure
--- +file_type: "slide" title: "Slide 02 - Why a .github Control Plane" description: "Explain why centralising standards in one .github repo was the first successful step." +version: "1.0.0" last_updated: "2026-05-28" owners: ["Ash Shaw"] +tags: ["wceu-2026", "control-plane", "talk"] +status: "draft" +stability: "stable" +domain: "documentation" ---As per coding guidelines: "All
.mdfiles in this repository should include YAML frontmatter with required fields: file_type, title, description, version, last_updated, owners, tags, status, stability, domain".🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@wceu-2026/slides/slide-02-why-github-control-plane.md` around lines 1 - 6, The frontmatter in the slide (title "Slide 02 - Why a .github Control Plane") is missing required metadata; update the YAML frontmatter at the top of the file to include the required fields: file_type, version, tags, status, stability, and domain in addition to the existing title, description, last_updated, and owners; ensure values follow repo conventions (e.g., file_type: "slide", version: "1.0.0", tags: [..], status: "draft|published", stability: "stable|experimental", domain: "wceu-2026") so the file validates against .schemas/frontmatter.schema.json and the repository coding guidelines.wceu-2026/slides/slide-03-inheritance-boundaries.md-1-6 (1)
1-6:⚠️ Potential issue | 🟠 Major | ⚡ Quick winMissing required frontmatter fields per schema and guidelines.
The frontmatter is missing several required fields:
file_type(required by.schemas/frontmatter.schema.json)version,tags,status,stability,domain(required by coding guidelines for all.mdfiles)These fields ensure proper schema validation and consistent metadata across documentation.
✨ Suggested frontmatter structure
--- +file_type: "slide" title: "Slide 03 - Inheritance Boundaries" description: "Clarify what central .github can and cannot enforce by default." +version: "1.0.0" last_updated: "2026-05-28" owners: ["Ash Shaw"] +tags: ["wceu-2026", "inheritance", "governance", "talk"] +status: "draft" +stability: "stable" +domain: "documentation" ---As per coding guidelines: "All
.mdfiles in this repository should include YAML frontmatter with required fields: file_type, title, description, version, last_updated, owners, tags, status, stability, domain".🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@wceu-2026/slides/slide-03-inheritance-boundaries.md` around lines 1 - 6, Add the required YAML frontmatter fields missing from this slide file: include file_type, version, tags, status, stability, and domain in addition to the existing title, description, last_updated, and owners; ensure the fields follow the repository schema (.schemas/frontmatter.schema.json) and coding-guidelines format (e.g., file_type: "slide", version: "1.0", tags: ["wceu","inheritance"], status: "draft" or "final", stability: "stable" or "experimental", domain: "docs" or appropriate domain) so the frontmatter for slide-03-inheritance-boundaries.md validates and matches other .md files.wceu-2026/slides/slide-07-plugin-pack-architecture.md-1-6 (1)
1-6:⚠️ Potential issue | 🟠 Major | ⚡ Quick winMissing required frontmatter fields per schema and guidelines.
The frontmatter is missing several required fields:
file_type(required by.schemas/frontmatter.schema.json)version,tags,status,stability,domain(required by coding guidelines for all.mdfiles)These fields ensure proper schema validation and consistent metadata across documentation.
✨ Suggested frontmatter structure
--- +file_type: "slide" title: "Slide 07 - Plugin Pack Architecture" description: "Break down what sits inside a plugin pack and why it matters." +version: "1.0.0" last_updated: "2026-05-28" owners: ["Ash Shaw"] +tags: ["wceu-2026", "plugin-pack", "architecture", "talk"] +status: "draft" +stability: "stable" +domain: "documentation" ---As per coding guidelines: "All
.mdfiles in this repository should include YAML frontmatter with required fields: file_type, title, description, version, last_updated, owners, tags, status, stability, domain".🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@wceu-2026/slides/slide-07-plugin-pack-architecture.md` around lines 1 - 6, Frontmatter in Slide 07 is missing required metadata fields; add the YAML keys file_type, version, tags, status, stability and domain to the existing frontmatter block alongside the existing title, description, last_updated and owners entries so it complies with .schemas/frontmatter.schema.json and the repository coding guidelines; ensure values are appropriate (e.g., file_type: "slide", version: "1.0.0", tags: [..], status: "draft|published", stability: "stable|experimental", domain: "wceu") and maintain YAML formatting and quoting consistent with the current frontmatter.wceu-2026/slides/slide-05-canonical-governance-assets.md-1-6 (1)
1-6:⚠️ Potential issue | 🟠 Major | ⚡ Quick winMissing required frontmatter fields per schema and guidelines.
The frontmatter is missing several required fields:
file_type(required by.schemas/frontmatter.schema.json)version,tags,status,stability,domain(required by coding guidelines for all.mdfiles)These fields ensure proper schema validation and consistent metadata across documentation.
✨ Suggested frontmatter structure
--- +file_type: "slide" title: "Slide 05 - Canonical Governance Assets" description: "Show the concrete governance assets that made scaling possible." +version: "1.0.0" last_updated: "2026-05-28" owners: ["Ash Shaw"] +tags: ["wceu-2026", "governance", "assets", "talk"] +status: "draft" +stability: "stable" +domain: "documentation" ---As per coding guidelines: "All
.mdfiles in this repository should include YAML frontmatter with required fields: file_type, title, description, version, last_updated, owners, tags, status, stability, domain".🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@wceu-2026/slides/slide-05-canonical-governance-assets.md` around lines 1 - 6, Add the missing required YAML frontmatter fields to the top of this markdown file: include file_type, version, tags, status, stability, and domain in the existing frontmatter block (title, description, last_updated, owners already present); ensure each field uses the repository's expected types/values (e.g., file_type: "slide", version: "1.0.0", tags: ["governance","scaling"], status: "final" or "draft", stability: "stable" or "experimental", domain: "governance") and keep the frontmatter delimiters (---) intact so schema validation accepts the file.wceu-2026/slides/slide-04-control-plane-architecture.md-1-6 (1)
1-6:⚠️ Potential issue | 🟠 Major | ⚡ Quick winMissing required frontmatter fields per schema and guidelines.
The frontmatter is missing several required fields:
file_type(required by.schemas/frontmatter.schema.json)version,tags,status,stability,domain(required by coding guidelines for all.mdfiles)These fields ensure proper schema validation and consistent metadata across documentation.
✨ Suggested frontmatter structure
--- +file_type: "slide" title: "Slide 04 - Control Plane Architecture" description: "Visualise the architecture of governance data, workflows, and standards." +version: "1.0.0" last_updated: "2026-05-28" owners: ["Ash Shaw"] +tags: ["wceu-2026", "architecture", "control-plane", "talk"] +status: "draft" +stability: "stable" +domain: "documentation" ---As per coding guidelines: "All
.mdfiles in this repository should include YAML frontmatter with required fields: file_type, title, description, version, last_updated, owners, tags, status, stability, domain".🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@wceu-2026/slides/slide-04-control-plane-architecture.md` around lines 1 - 6, Add the required YAML frontmatter fields to the existing frontmatter block (the leading --- section) so it validates against .schemas/frontmatter.schema.json and the repo guidelines: include file_type, version, tags, status, stability, and domain in addition to the existing title, description, last_updated, and owners; populate them with appropriate values (e.g., file_type: "slide", version: "1.0.0", tags: [ ... ], status: "draft|published", stability: "stable|experimental", domain: "<domain-name>") and ensure proper YAML formatting and quoting where needed and update last_updated if applicable. Ensure the final frontmatter YAML remains between the opening and closing --- markers and follows the same field naming (file_type, title, description, version, last_updated, owners, tags, status, stability, domain) required by the schema.wceu-2026/slides/slide-01-hook-and-stakes.md-1-6 (1)
1-6:⚠️ Potential issue | 🟠 Major | ⚡ Quick winMissing required frontmatter fields per schema and guidelines.
The frontmatter is missing several required fields:
file_type(required by.schemas/frontmatter.schema.json)version,tags,status,stability,domain(required by coding guidelines for all.mdfiles)These fields ensure proper schema validation and consistent metadata across documentation.
✨ Suggested frontmatter structure
--- +file_type: "slide" title: "Slide 01 - Hook and Stakes" description: "Open with the operational pain and why this matters now." +version: "1.0.0" last_updated: "2026-05-28" owners: ["Ash Shaw"] +tags: ["wceu-2026", "governance", "talk"] +status: "draft" +stability: "stable" +domain: "documentation" ---As per coding guidelines: "All
.mdfiles in this repository should include YAML frontmatter with required fields: file_type, title, description, version, last_updated, owners, tags, status, stability, domain".🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@wceu-2026/slides/slide-01-hook-and-stakes.md` around lines 1 - 6, The frontmatter for slide-01-hook-and-stakes.md is missing required YAML fields; update the existing frontmatter block (the lines with title, description, last_updated, owners) to include the required keys: file_type, version, tags, status, stability, and domain, ensuring each key is present and populated with appropriate values (e.g., file_type: "slide", version: "1.0.0", tags: [..], status: "draft", stability: "stable|experimental", domain: "wceu-2026"); keep the existing title, description, last_updated, and owners entries and ensure the whole block remains valid YAML frontmatter delimited by ---.wceu-2026/slides/slide-08-multi-platform-parity.md-1-6 (1)
1-6:⚠️ Potential issue | 🟠 Major | ⚡ Quick winMissing required frontmatter fields per schema and guidelines.
The frontmatter is missing several required fields:
file_type(required by.schemas/frontmatter.schema.json)version,tags,status,stability,domain(required by coding guidelines for all.mdfiles)These fields ensure proper schema validation and consistent metadata across documentation.
✨ Suggested frontmatter structure
--- +file_type: "slide" title: "Slide 08 - Multi-Platform Parity" description: "Explain manifest parity across Copilot, Claude Code, Codex, and Gemini." +version: "1.0.0" last_updated: "2026-05-28" owners: ["Ash Shaw"] +tags: ["wceu-2026", "multi-platform", "parity", "talk"] +status: "draft" +stability: "stable" +domain: "documentation" ---As per coding guidelines: "All
.mdfiles in this repository should include YAML frontmatter with required fields: file_type, title, description, version, last_updated, owners, tags, status, stability, domain".🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@wceu-2026/slides/slide-08-multi-platform-parity.md` around lines 1 - 6, The frontmatter for slide-08-multi-platform-parity.md is missing required YAML fields; update the top-of-file frontmatter (the existing block with title/description/last_updated/owners) to include file_type, version, tags, status, stability, and domain per the repository schema and guidelines; ensure each field is populated with appropriate values (e.g., file_type: "slide", a semantic version or draft for version, an array for tags, one of the allowed statuses, a stability level, and the domain string) so the file validates against .schemas/frontmatter.schema.json and the project conventions.wceu-2026/slides/slide-06-why-we-pivoted.md-1-6 (1)
1-6:⚠️ Potential issue | 🟠 Major | ⚡ Quick winMissing required frontmatter fields per schema and guidelines.
The frontmatter is missing several required fields:
file_type(required by.schemas/frontmatter.schema.json)version,tags,status,stability,domain(required by coding guidelines for all.mdfiles)These fields ensure proper schema validation and consistent metadata across documentation.
✨ Suggested frontmatter structure
--- +file_type: "slide" title: "Slide 06 - Why We Pivoted" description: "Explain why centralisation alone was insufficient and why a plugin model emerged." +version: "1.0.0" last_updated: "2026-05-28" owners: ["Ash Shaw"] +tags: ["wceu-2026", "pivot", "plugin-model", "talk"] +status: "draft" +stability: "stable" +domain: "documentation" ---As per coding guidelines: "All
.mdfiles in this repository should include YAML frontmatter with required fields: file_type, title, description, version, last_updated, owners, tags, status, stability, domain".🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@wceu-2026/slides/slide-06-why-we-pivoted.md` around lines 1 - 6, Add the missing required YAML frontmatter fields to this Markdown file: include file_type, version, tags, status, stability, and domain alongside the existing title, description, last_updated, and owners entries; ensure file_type matches the repository schema (e.g., "slide"), set a semantic version string for version, populate tags as an array, and choose appropriate values for status and stability and the domain per project guidelines so the file validates against .schemas/frontmatter.schema.json and the repo coding guidelines.wceu-2026/slides/slide-09-quality-and-release-gates.md-1-6 (1)
1-6:⚠️ Potential issue | 🟠 Major | ⚡ Quick winMissing required frontmatter fields across all slide files.
The coding guidelines require all
.mdfiles to include these frontmatter fields:file_type,title,description,version,last_updated,owners,tags,status,stability, anddomain. This slide (and all slides 9–16 in this cohort) only includestitle,description,last_updated, andowners.📋 Proposed frontmatter additions
--- +file_type: "slide_specification" title: "Slide 09 - Quality and Release Gates" description: "Show how validation, linting, and release workflows are enforced." +version: "1.0.0" last_updated: "2026-05-28" owners: ["Ash Shaw"] +tags: ["wceu-2026", "governance", "quality", "release", "workflows"] +status: "draft" +stability: "stable" +domain: "documentation" ---As per coding guidelines, all
.mdfiles in this repository should include YAML frontmatter with required fields: file_type, title, description, version, last_updated, owners, tags, status, stability, domain.🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@wceu-2026/slides/slide-09-quality-and-release-gates.md` around lines 1 - 6, This slide's YAML frontmatter is missing required fields per repo guidelines; update the frontmatter block in slide-09-quality-and-release-gates.md (and the same for slides 09–16 in this cohort) to include the required keys file_type, version, tags, status, stability, and domain in addition to the existing title, description, last_updated, and owners; ensure the frontmatter remains valid YAML with the leading/trailing --- markers and populate sensible values (e.g., file_type: slide, version: 1.0.0, tags: [...], status, stability, domain) so CI/linting recognizes the file.wceu-2026/slides/slide-17-issue-template-system.md-1-6 (1)
1-6:⚠️ Potential issue | 🟠 Major | ⚡ Quick winAdd missing required frontmatter fields.
The YAML frontmatter is missing several required fields according to the coding guidelines. All
.mdfiles in this repository should include:file_type,version,tags,status,stability, anddomain.As per coding guidelines: "All
.mdfiles in this repository should include YAML frontmatter with required fields: file_type, title, description, version, last_updated, owners, tags, status, stability, domain"📋 Suggested frontmatter additions
--- +file_type: "slide-specification" title: "Slide 17 - Issue Template System" description: "Explain issue template strategy and structured intake." +version: "1.0.0" last_updated: "2026-05-28" owners: ["Ash Shaw"] +tags: ["wceu-2026", "slides", "issue-templates", "governance"] +status: "draft" +stability: "stable" +domain: "github-governance" ---🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@wceu-2026/slides/slide-17-issue-template-system.md` around lines 1 - 6, The YAML frontmatter for this slide is missing required fields; update the existing frontmatter block that already contains title, description, last_updated, and owners by adding the required keys file_type, version, tags, status, stability, and domain (populate them with appropriate values for a slide, e.g., file_type: "slide", a semantic version string for version, an array for tags, status like "draft" or "final", a stability value, and the relevant domain) so the frontmatter includes all mandatory fields alongside the existing title/description/last_updated/owners.wceu-2026/slides/slide-19-ai-governance-model.md-1-6 (1)
1-6:⚠️ Potential issue | 🟠 Major | ⚡ Quick winAdd missing required frontmatter fields.
The YAML frontmatter is missing several required fields according to the coding guidelines. All
.mdfiles in this repository should include:file_type,version,tags,status,stability, anddomain.As per coding guidelines: "All
.mdfiles in this repository should include YAML frontmatter with required fields: file_type, title, description, version, last_updated, owners, tags, status, stability, domain"📋 Suggested frontmatter additions
--- +file_type: "slide-specification" title: "Slide 19 - AI Governance Model" description: "Explain policy, instruction hierarchy, and guardrails for AI-assisted delivery." +version: "1.0.0" last_updated: "2026-05-28" owners: ["Ash Shaw"] +tags: ["wceu-2026", "slides", "ai-governance", "governance"] +status: "draft" +stability: "stable" +domain: "github-governance" ---🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@wceu-2026/slides/slide-19-ai-governance-model.md` around lines 1 - 6, The YAML frontmatter for Slide 19 (the block containing title/description/last_updated/owners) is missing required fields; update that frontmatter to include file_type, version, tags, status, stability, and domain alongside the existing fields (title, description, last_updated, owners) so the header matches repository guidelines; ensure values are valid for markdown slides (e.g., file_type: "slide", a semantic version string for version, an array for tags, and appropriate status/stability/domain strings) and keep the YAML block at the top of slide-19-ai-governance-model.md.wceu-2026/slides/slide-18-pr-template-system.md-1-6 (1)
1-6:⚠️ Potential issue | 🟠 Major | ⚡ Quick winAdd missing required frontmatter fields.
The YAML frontmatter is missing several required fields according to the coding guidelines. All
.mdfiles in this repository should include:file_type,version,tags,status,stability, anddomain.As per coding guidelines: "All
.mdfiles in this repository should include YAML frontmatter with required fields: file_type, title, description, version, last_updated, owners, tags, status, stability, domain"📋 Suggested frontmatter additions
--- +file_type: "slide-specification" title: "Slide 18 - PR Template System" description: "Show PR templates as quality and release-readiness checks." +version: "1.0.0" last_updated: "2026-05-28" owners: ["Ash Shaw"] +tags: ["wceu-2026", "slides", "pr-templates", "governance"] +status: "draft" +stability: "stable" +domain: "github-governance" ---🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@wceu-2026/slides/slide-18-pr-template-system.md` around lines 1 - 6, The frontmatter for slide-18-pr-template-system.md is missing required YAML fields; update the existing frontmatter block (the top YAML between --- markers containing title, description, last_updated, owners) to add the missing keys: file_type, version, tags, status, stability, and domain; ensure you keep the existing title/description/last_updated/owners values and add sensible values for file_type (e.g., "slide"), version (semantic version or "1.0.0"), tags (array), status (e.g., "draft" or "final"), stability (e.g., "stable" or "unstable"), and domain (e.g., "wceu-2026") so the file conforms to repository frontmatter guidelines.wceu-2026/slides/slide-20-ecosystem-and-acknowledgements.md-1-6 (1)
1-6:⚠️ Potential issue | 🟠 Major | ⚡ Quick winAdd missing required frontmatter fields.
The YAML frontmatter is missing several required fields according to the coding guidelines. All
.mdfiles in this repository should include:file_type,version,tags,status,stability, anddomain.As per coding guidelines: "All
.mdfiles in this repository should include YAML frontmatter with required fields: file_type, title, description, version, last_updated, owners, tags, status, stability, domain"📋 Suggested frontmatter additions
--- +file_type: "slide-specification" title: "Slide 20 - Ecosystem and Acknowledgements" description: "Close with adoption next steps and acknowledgement of open-source inspiration." +version: "1.0.0" last_updated: "2026-05-28" owners: ["Ash Shaw"] +tags: ["wceu-2026", "slides", "ecosystem", "acknowledgements"] +status: "draft" +stability: "stable" +domain: "github-governance" ---🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@wceu-2026/slides/slide-20-ecosystem-and-acknowledgements.md` around lines 1 - 6, The YAML frontmatter for the slide titled "Slide 20 - Ecosystem and Acknowledgements" is missing required fields; update the existing frontmatter block (the top YAML under the title/description/last_updated/owners) to include file_type, version, tags, status, stability, and domain with appropriate values per repo conventions (e.g., file_type: "slide" or "md", version as a semantic or date string, tags as a list, status as draft/published, stability as experimental/stable, and domain as the relevant category) so the file includes all required frontmatter keys.
🟡 Minor comments (1)
wceu-2026/slides/slide-20-ecosystem-and-acknowledgements.md-22-22 (1)
22-22:⚠️ Potential issue | 🟡 Minor | ⚡ Quick winCapitalise "GitHub" in repository references.
The platform name should be capitalised as "GitHub" rather than "github" when referring to
GitHub/awesome-copilot. This maintains proper noun consistency and aligns with the platform's official branding.🔤 Proposed capitalisation fix
-- Include explicit thanks to `github/awesome-copilot`. +- Include explicit thanks to `GitHub/awesome-copilot`.-With thanks to `github/awesome-copilot` for the inspiration and practical patterns that helped shape this direction. +With thanks to `GitHub/awesome-copilot` for the inspiration and practical patterns that helped shape this direction.Also applies to: 34-34
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@wceu-2026/slides/slide-20-ecosystem-and-acknowledgements.md` at line 22, Update the repository reference to use the correct capitalization: replace occurrences of `github/awesome-copilot` with `GitHub/awesome-copilot` in slide-20-ecosystem-and-acknowledgements.md (also check the other occurrence noted around line 34) so the platform name is consistently capitalised as "GitHub".
🧹 Nitpick comments (14)
wceu-2026/slides/slide-02-why-github-control-plane.md (1)
45-45: 💤 Low valueConsider using en dash for numeric range.
The range "25-40" would be more typographically precise as "25–40" (en dash).
🎨 Proposed typography refinement
-- Keep on-slide text short (roughly 25-40 words total where possible). +- Keep on-slide text short (roughly 25–40 words total where possible).🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@wceu-2026/slides/slide-02-why-github-control-plane.md` at line 45, In the slide text line "Keep on-slide text short (roughly 25-40 words total where possible)", replace the hyphenated numeric range "25-40" with an en dash "25–40" (so the phrase becomes "roughly 25–40 words") to follow typographic conventions; ensure the file encoding supports the en dash character and run a quick search for other numeric ranges in the same file to apply the same replacement if present.wceu-2026/slides/slide-08-multi-platform-parity.md (1)
45-45: 💤 Low valueConsider using en dash for numeric range.
The range "25-40" would be more typographically precise as "25–40" (en dash).
🎨 Proposed typography refinement
-- Keep on-slide text short (roughly 25-40 words total where possible). +- Keep on-slide text short (roughly 25–40 words total where possible).🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@wceu-2026/slides/slide-08-multi-platform-parity.md` at line 45, In the sentence "Keep on-slide text short (roughly 25-40 words total where possible)." replace the hyphenated numeric range "25-40" with an en dash "25–40" to follow typographic convention; locate that exact string in slide-08-multi-platform-parity.md and update it so the text reads "Keep on-slide text short (roughly 25–40 words total where possible)."wceu-2026/slides/slide-07-plugin-pack-architecture.md (1)
43-43: 💤 Low valueConsider using en dash for numeric range.
The range "25-40" would be more typographically precise as "25–40" (en dash).
🎨 Proposed typography refinement
-- Keep on-slide text short (roughly 25-40 words total where possible). +- Keep on-slide text short (roughly 25–40 words total where possible).🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@wceu-2026/slides/slide-07-plugin-pack-architecture.md` at line 43, Replace the hyphenated numeric range "25-40" in the slide text "Keep on-slide text short (roughly 25-40 words total where possible)." with an en dash ("25–40") to use proper typographic punctuation; update the string in the file so the line reads "Keep on-slide text short (roughly 25–40 words total where possible)." (use the U+2013 en dash character or your project's preferred entity).wceu-2026/slides/slide-05-canonical-governance-assets.md (1)
45-45: 💤 Low valueConsider using en dash for numeric range.
The range "25-40" would be more typographically precise as "25–40" (en dash).
🎨 Proposed typography refinement
-- Keep on-slide text short (roughly 25-40 words total where possible). +- Keep on-slide text short (roughly 25–40 words total where possible).🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@wceu-2026/slides/slide-05-canonical-governance-assets.md` at line 45, Replace the ASCII hyphen in the slide text "25-40" with an en dash so it reads "25–40"; locate the occurrence in the line containing "Keep on-slide text short (roughly 25-40 words total where possible)" and update the punctuation only, preserving spacing and meaning.wceu-2026/slides/slide-01-hook-and-stakes.md (1)
43-43: 💤 Low valueConsider using en dash for numeric range.
The range "25-40" would be more typographically precise as "25–40" (en dash).
🎨 Proposed typography refinement
-- Keep on-slide text short (roughly 25-40 words total where possible). +- Keep on-slide text short (roughly 25–40 words total where possible).🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@wceu-2026/slides/slide-01-hook-and-stakes.md` at line 43, In the slide text "Keep on-slide text short (roughly 25-40 words total where possible)." replace the hyphen between the numbers with an en dash so it reads "Keep on-slide text short (roughly 25–40 words total where possible).", preserving all other punctuation and spacing.wceu-2026/slides/slide-03-inheritance-boundaries.md (1)
44-44: 💤 Low valueConsider using en dash for numeric range.
The range "25-40" would be more typographically precise as "25–40" (en dash).
🎨 Proposed typography refinement
-- Keep on-slide text short (roughly 25-40 words total where possible). +- Keep on-slide text short (roughly 25–40 words total where possible).🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@wceu-2026/slides/slide-03-inheritance-boundaries.md` at line 44, Replace the hyphenated numeric range in the slide text "Keep on-slide text short (roughly 25-40 words total where possible)." with an en dash for typographic correctness so it reads "25–40"; update the string in slide-03-inheritance-boundaries.md wherever that phrase appears (search for "roughly 25-40") to use the en dash character.wceu-2026/slides/slide-06-why-we-pivoted.md (1)
43-43: 💤 Low valueConsider using en dash for numeric range.
The range "25-40" would be more typographically precise as "25–40" (en dash).
🎨 Proposed typography refinement
-- Keep on-slide text short (roughly 25-40 words total where possible). +- Keep on-slide text short (roughly 25–40 words total where possible).🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@wceu-2026/slides/slide-06-why-we-pivoted.md` at line 43, The phrase 'Keep on-slide text short (roughly 25-40 words total where possible).' should use an en dash for the numeric range; update the exact string so it reads 'Keep on-slide text short (roughly 25–40 words total where possible).' (replace the hyphen between 25 and 40 with the Unicode en dash U+2013) to improve typographic precision.wceu-2026/slides/slide-04-control-plane-architecture.md (1)
44-44: 💤 Low valueConsider using en dash for numeric range.
The range "25-40" would be more typographically precise as "25–40" (en dash).
🎨 Proposed typography refinement
-- Keep on-slide text short (roughly 25-40 words total where possible). +- Keep on-slide text short (roughly 25–40 words total where possible).🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@wceu-2026/slides/slide-04-control-plane-architecture.md` at line 44, The range "25-40" in the sentence "Keep on-slide text short (roughly 25-40 words total where possible)." should use an en dash for typographic correctness; update that fragment to "25–40" so the line reads "Keep on-slide text short (roughly 25–40 words total where possible)." This is a straight character replacement in the slide content.wceu-2026/slides/slide-16-workflow-layer.md (1)
47-47: 💤 Low valueMissing trailing newlines across all slide files.
All slides 9–16 are missing a final newline at the end of the file. While this is a minor formatting detail, it's good practice to include a trailing newline for POSIX compliance and cleaner git diffs.
🔧 Quick fix
Simply add a blank line at the end of each slide file (after line 46/47/48 depending on the file).
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@wceu-2026/slides/slide-16-workflow-layer.md` at line 47, Add a single trailing newline at the end of each slide file missing it (slides 9–16), including wceu-2026/slides/slide-16-workflow-layer.md, so the file ends with a blank line/EOF newline (POSIX-compliant) to fix the missing final newline and clean up git diffs.wceu-2026/slides/slide-09-quality-and-release-gates.md (1)
45-46: 💤 Low valueTypographical refinement: consider using an en dash for numeric ranges.
The range "25-40" would be more typographically correct as "25–40" (en dash). This is a minor stylistic preference for technical documentation, but it does improve readability and aligns with professional typesetting conventions.
✨ Proposed typographical fix
-- Keep on-slide text short (roughly 25-40 words total where possible). +- Keep on-slide text short (roughly 25–40 words total where possible).🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@wceu-2026/slides/slide-09-quality-and-release-gates.md` around lines 45 - 46, The slide text uses a hyphenated numeric range "25-40" which should be typographically an en dash; update the line containing "- Keep on-slide text short (roughly 25-40 words total where possible)." to use "25–40" (en dash) instead of a hyphen and ensure the file remains UTF-8 encoded; also scan the same markdown for other numeric ranges to consistently replace hyphens with en dashes where appropriate.wceu-2026/slides/slide-20-ecosystem-and-acknowledgements.md (1)
48-48: 💤 Low valueConsider using en dash for number ranges.
The range "25-40" would be more typographically correct as "25–40" (en dash). This is a minor stylistic refinement that improves readability.
✨ Proposed typographical improvement
-- Keep on-slide text short (roughly 25-40 words total where possible). +- Keep on-slide text short (roughly 25–40 words total where possible).🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@wceu-2026/slides/slide-20-ecosystem-and-acknowledgements.md` at line 48, Replace the ASCII hyphen in the slide line "Keep on-slide text short (roughly 25-40 words total where possible)." by using an en dash (i.e., change "25-40" to "25–40" U+2013) to follow typographic conventions; locate the exact string "25-40" in slide-20-ecosystem-and-acknowledgements.md and make the single-character replacement, ensuring no other hyphenated words are altered.wceu-2026/slides/slide-19-ai-governance-model.md (1)
46-46: 💤 Low valueConsider using en dash for number ranges.
The range "25-40" would be more typographically correct as "25–40" (en dash). This is a minor stylistic refinement that improves readability.
✨ Proposed typographical improvement
-- Keep on-slide text short (roughly 25-40 words total where possible). +- Keep on-slide text short (roughly 25–40 words total where possible).🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@wceu-2026/slides/slide-19-ai-governance-model.md` at line 46, Replace the hyphenated range "25-40" in the slide text "Keep on-slide text short (roughly 25-40 words total where possible)." with an en dash so it reads "25–40" to improve typographic correctness; update the exact string in slide-19-ai-governance-model.md where that sentence appears.wceu-2026/slides/slide-18-pr-template-system.md (1)
45-45: 💤 Low valueConsider using en dash for number ranges.
The range "25-40" would be more typographically correct as "25–40" (en dash). This is a minor stylistic refinement that improves readability.
✨ Proposed typographical improvement
-- Keep on-slide text short (roughly 25-40 words total where possible). +- Keep on-slide text short (roughly 25–40 words total where possible).🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@wceu-2026/slides/slide-18-pr-template-system.md` at line 45, The sentence "Keep on-slide text short (roughly 25-40 words total where possible)." uses a hyphen for the range; replace "25-40" with an en dash so it reads "25–40" to follow typographic conventions—update the text in slide-18-pr-template-system.md where that exact phrase appears.wceu-2026/slides/slide-17-issue-template-system.md (1)
45-45: 💤 Low valueConsider using en dash for number ranges.
The range "25-40" would be more typographically correct as "25–40" (en dash). This is a minor stylistic refinement that improves readability.
✨ Proposed typographical improvement
-- Keep on-slide text short (roughly 25-40 words total where possible). +- Keep on-slide text short (roughly 25–40 words total where possible).🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@wceu-2026/slides/slide-17-issue-template-system.md` at line 45, Replace the hyphenated number range in the slide guidance string "Keep on-slide text short (roughly 25-40 words total where possible)." with an en dash so it reads "Keep on-slide text short (roughly 25–40 words total where possible)."; locate and update that exact phrase in slide-17-issue-template-system.md (the line containing the "roughly 25-40" range) to use the en dash character (U+2013).
github-actions
Bot
added
type:feature
🔍 Reviewer Summary for PR #751CI Status: ❌ Recommendations
|
There was a problem hiding this comment.
Pull request overview
Adds a WCEU 2026 talk “asset pack” under wceu-2026/ (talk outline, slide-per-file content, evidence mapping, and mini-site starter copy), plus a few minor documentation/run-log formatting tweaks elsewhere.
Changes:
- Adds/updates the WCEU 2026 mini-site plan and page-copy starter content.
- Reworks the 25-minute talk outline and slide content into a slide-per-file structure with evidence anchors and a slide-to-source mapping.
- Trims/simplifies NotebookLM ingestion/prompt docs and applies small markdown formatting clean-ups in project logs/metadata.
Reviewed changes
Copilot reviewed 32 out of 33 changed files in this pull request and generated 43 comments.
Show a summary per file
| File | Description |
|---|---|
| wceu-2026/website/page-copy-starter.md | Adds starter copy blocks for mini-site pages (home/problem/control plane/pivot/outcomes). |
| wceu-2026/website/mini-site-plan.md | Adds proposed IA, principles, and required assets for the mini-site. |
| wceu-2026/wceu-talk-june-2026.md | Minor markdown formatting normalisation (spacing/list style adjustments). |
| wceu-2026/talk-outline-25min.md | Replaces long-form outline with a tighter 20-slide order + timing and slide links. |
| wceu-2026/slides/slide-20-ecosystem-and-acknowledgements.md | Adds structured slide brief, evidence anchors, and speaker notes. |
| wceu-2026/slides/slide-19-ai-governance-model.md | Adds structured slide brief, evidence anchors, and speaker notes. |
| wceu-2026/slides/slide-18-pr-template-system.md | Adds structured slide brief, evidence anchors, and speaker notes. |
| wceu-2026/slides/slide-17-issue-template-system.md | Adds structured slide brief, evidence anchors, and speaker notes. |
| wceu-2026/slides/slide-16-workflow-layer.md | Adds structured slide brief, evidence anchors, and speaker notes. |
| wceu-2026/slides/slide-15-hook-layer.md | Adds structured slide brief, evidence anchors, and speaker notes. |
| wceu-2026/slides/slide-14-skill-layer.md | Adds structured slide brief, evidence anchors, and speaker notes. |
| wceu-2026/slides/slide-13-agent-layer.md | Adds structured slide brief, evidence anchors, and speaker notes. |
| wceu-2026/slides/slide-12-adoption-playbook.md | Adds structured slide brief, evidence anchors, and speaker notes. |
| wceu-2026/slides/slide-11-lessons-and-anti-patterns.md | Adds structured slide brief, evidence anchors, and speaker notes. |
| wceu-2026/slides/slide-10-metrics-and-governance-outcomes.md | Adds structured slide brief, evidence anchors, and speaker notes. |
| wceu-2026/slides/slide-09-quality-and-release-gates.md | Adds structured slide brief, evidence anchors, and speaker notes. |
| wceu-2026/slides/slide-08-multi-platform-parity.md | Adds structured slide brief, evidence anchors, and speaker notes. |
| wceu-2026/slides/slide-07-plugin-pack-architecture.md | Adds structured slide brief, evidence anchors, and speaker notes. |
| wceu-2026/slides/slide-06-why-we-pivoted.md | Adds structured slide brief, evidence anchors, and speaker notes. |
| wceu-2026/slides/slide-05-canonical-governance-assets.md | Adds structured slide brief, evidence anchors, and speaker notes. |
| wceu-2026/slides/slide-04-control-plane-architecture.md | Adds structured slide brief, evidence anchors, and speaker notes. |
| wceu-2026/slides/slide-03-inheritance-boundaries.md | Adds structured slide brief, evidence anchors, and speaker notes. |
| wceu-2026/slides/slide-02-why-github-control-plane.md | Adds structured slide brief, evidence anchors, and speaker notes. |
| wceu-2026/slides/slide-01-hook-and-stakes.md | Adds structured slide brief, evidence anchors, and speaker notes. |
| wceu-2026/references/slide-to-source-mapping.md | Adds a deck-order → repo-evidence mapping table. |
| wceu-2026/references/repo-source-index.md | Adds a curated index of repo-only sources to back talk claims. |
| wceu-2026/README.md | Replaces long, phase-heavy README with a shorter asset-pack index and current direction. |
| wceu-2026/notebooklm/source-ingestion-checklist.md | Simplifies ingestion rules and provides an allowlist of internal sources. |
| wceu-2026/notebooklm/deep-research-prompt.md | Replaces long, URL-heavy prompt with a repo-only evidence-constrained prompt. |
| .github/projects/completed/issue-670-readme-refresh/README.md | Tweaks list formatting (but introduces an extra YAML-like block in the body). |
| .github/projects/active/refactor-migrate-prompts/RUN_LOG.md | Adds blank lines to improve markdown readability between entries. |
| .github/projects/active/opsx-proposals-audit-2026-06-01.md | Adds spacing between sections for readability. |
| .github/metrics/meta.json | Fixes formatting/indentation at EOF. |
| related_issues: | ||
| - "#668" | ||
| - "#669" | ||
| - "#667" | ||
|
|
||
| - "#668" | ||
| - "#669" | ||
| - "#667" | ||
|
|
||
| --- |
| --- | ||
| file_type: "documentation" | ||
| title: "WCEU 2026 Presentation Materials" | ||
| description: "Complete Phase 1, 2, and 3 materials for WCEU 2026 talk: 'One .github repo to rule them all'" | ||
| version: "v1.0.0" | ||
| created_date: "2026-05-28" | ||
| last_updated: '2026-06-01' | ||
| maintainer: "LightSpeed Team" | ||
| tags: ["wceu-2026", "presentation", "documentation"] | ||
| title: "WCEU 2026 Talk Asset Pack" | ||
| description: "Working assets for the WordCamp Europe 2026 talk on evolving lightspeedwp/.github into an installable AI-ops and governance plugin platform." | ||
| last_updated: "2026-05-28" | ||
| owners: ["Ash Shaw"] |
| --- | ||
| title: "Talk Outline (25 Minutes)" | ||
| description: "Speaker outline for WCEU 2026: from central .github governance repo to installable AI-ops plugin packs." | ||
| created_date: "2026-05-28" | ||
| file_type: documentation | ||
| last_updated: "2026-05-29" | ||
| last_updated: "2026-05-28" | ||
| owners: ["Ash Shaw"] |
| --- | ||
| title: "Mini Website Plan" | ||
| description: "Information architecture and content requirements for a mini website explaining the WCEU 2026 talk." | ||
| created_date: "2026-05-28" | ||
| file_type: documentation | ||
| last_updated: "2026-05-28" | ||
| owners: ["Ash Shaw"] |
| --- | ||
| title: "Page Copy Starter" | ||
| description: "Draft copy scaffolding for mini website pages based on the talk narrative." | ||
| created_date: "2026-05-28" | ||
| file_type: documentation | ||
| last_updated: "2026-05-28" | ||
| owners: ["Ash Shaw"] |
| - `.github/labels.yml` | ||
| - `.github/labeler.yml` | ||
| - `.github/issue-types.yml` | ||
| - `docs/AUTOMATION_GOVERNANCE.md` |
| - `.github/workflows/linting.yml` | ||
| - `.github/workflows/release.yml` | ||
| - `.github/workflows/reviewer.yml` | ||
| - `docs/WORKFLOWS.md` |
| | 5 | [slide-05-canonical-governance-assets.md](../slides/slide-05-canonical-governance-assets.md) | Canonical governance assets | `.github/labels.yml`, `docs/LABEL_STRATEGY.md`, `instructions/coding-standards.instructions.md` | | ||
| | 6 | [slide-17-issue-template-system.md](../slides/slide-17-issue-template-system.md) | Issue templates | `.github/ISSUE_TEMPLATE/config.yml`, `.github/ISSUE_TEMPLATE/README.md`, `.github/ISSUE_TEMPLATE/23-ai-ops.md` | | ||
| | 7 | [slide-18-pr-template-system.md](../slides/slide-18-pr-template-system.md) | PR templates | `.github/PULL_REQUEST_TEMPLATE/README.md`, `.github/PULL_REQUEST_TEMPLATE/pr_feature.md`, `.github/PULL_REQUEST_TEMPLATE/pr_release.md` | | ||
| | 8 | [slide-16-workflow-layer.md](../slides/slide-16-workflow-layer.md) | Workflow layer | `.github/workflows/labeling.yml`, `.github/workflows/release.yml`, `docs/WORKFLOWS.md` | |
| - `docs/RELEASE_PROCESS.md` | ||
| - `docs/TESTING.md` | ||
| - `docs/METRICS.md` | ||
| - `docs/WORKFLOWS.md` |
| - `.github/issue-types.yml` | ||
| - `docs/AUTOMATION_GOVERNANCE.md` | ||
| - `docs/RELEASE_PROCESS.md` | ||
| - `docs/WORKFLOWS.md` |
github-actions
Bot
added
area:ci
ashleyshaw
removed
meta:needs-changelog
github-actions
Bot
added
type:chore
Summary\nAdds WCEU 2026 talk assets, including slide source files, talk outline, source mapping, and website starter content under wceu-2026/.\n\n## Scope\n- New talk outline and supporting references\n- 20 slide markdown files\n- Website mini-plan and starter copy\n\n## Validation\n- Content-only additions\n- No production code paths modified\n\n## Merge notes\n- Target branch: develop\n- Low risk: additive documentation/content files only