feat(workflows): add frontmatter-aligner gh-aw workflow

[Copilot]

Summary

Adds .github/workflows/frontmatter-aligner.md — a scheduled GitHub agentic workflow that keeps the ado-aw front matter schema aligned with gh-aw by automatically detecting gaps and filing a concrete Rust change proposal as a GitHub issue.

Every 6 hours the agent:

1. Fetches gh-aw's canonical front matter reference from https://raw.githubusercontent.com/github/gh-aw/main/.github/aw/syntax.md
2. Reads the ado-aw schema from src/compile/types.rs (FrontMatter struct and supporting types)
3. Compares the two schemas field-by-field, classifying each gh-aw field as present, partial, or missing in ado-aw
4. Drafts exact Rust snippets — the precise src/compile/types.rs field additions and docs/front-matter.md documentation entries needed to close each gap
5. Validates the proposal with cargo check (without committing any code)
6. Files an issue containing the ready-to-apply proposal, or exits silently if schemas are already aligned or a frontmatter-alignment-labelled issue is already open

Configuration

Field	Value
Schedule	every 6 hours → cron: "48 */6 * * *"
Rust runtime	actions-rust-lang/setup-rust-toolchain@v1 (stable)
Network	defaults + rust ecosystem (for cargo)
Safe output	create-issue (max 1, label: frontmatter-alignment)
Duplicate guard	skip-if-match: "is:issue is:open label:frontmatter-alignment"

Security review

This compilation introduces the following new action:

• github/gh-aw-actions/setup@v0.68.1 — the standard gh-aw framework setup action used by every workflow in this repository. Safe to add.

No new secrets beyond those already used by existing workflows in this repo.

Test plan

Compiled with gh aw compile frontmatter-aligner — 0 errors, 0 warnings. Lock file verified to contain the correct cron expression, Rust runtime setup step, create_issue safe-output handler with frontmatter-alignment label, and skip-if-match pre-activation check.

[jamesadevine]

@copilot instead of PRs let's make an issue. The agent here should make a concrete proposal in the issue it files b

[Copilot]

@copilot instead of PRs let's make an issue. The agent here should make a concrete proposal in the issue it files b

Done in a9e67e1. The workflow now uses create-issue instead of create-pull-request. The agent drafts the proposed Rust code snippets (exact struct field additions for src/compile/types.rs + doc entries for docs/front-matter.md), runs cargo check to validate they compile, then files everything as a concrete, ready-to-apply proposal in the issue body. A skip-if-match guard prevents duplicate issues when one with the frontmatter-alignment label is already open.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• https://api.github.com/repos/github/gh-aw-actions/git/ref/tags/v0.68.1
  • Triggering command: /usr/bin/gh gh api /repos/github/gh-aw-actions/git/ref/tags/v0.68.1 --jq .object.sha (http block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)