The GitHub Actions job "link-check" on airflow-steward.git/main has failed. Run started by GitHub user potiuk (triggered by potiuk).
Head commit for run: 72e55c2e5018f079b56d65e54841a76589e87d67 / André Ahlert <[email protected]> feat: surface MISSION mode taxonomy in code, skills, and adopter-facing docs (#61) * docs(modes): add docs/modes.md mapping MISSION taxonomy to current skills MISSION.md frames the framework around Mode A/B/C/D, but the taxonomy is not surfaced anywhere in the code or adopter docs. Add a maintainer- facing reference that maps each mode to the skills currently shipping, with honest status per mode (stable / experimental / proposed / off): - Mode A (triage) — 10 skills across pr-management and security - Mode B (mentoring) — proposed, no skill yet - Mode C (agent-authored fixes with human review) — partial, security-only - Mode D (narrowly-scoped fix-and-merge) — off per MISSION sequencing Also documents skills that sit outside the mode taxonomy (the setup family is framework infrastructure) and the mode lifecycle states (proposed → experimental → stable → graduated-to-D-eligible) so adopters and reviewers can map MISSION's commitments to verifiable repo state. Generated-by: Claude Code (Opus 4.7) * feat(skills): add `mode` field to SKILL.md frontmatter Tag every skill that fits the MISSION mode taxonomy (see docs/modes.md) with a `mode:` frontmatter field — Mode A for triage skills, Mode C for agent-authored fix skills. Setup-family skills are infrastructure and intentionally omit the field. Extends `skill-validator` to recognise `mode` as an optional frontmatter key and validate the value against `{A, B, C}`. Mode D is excluded because MISSION holds it off; a `mode: D` value would be a sequencing violation rather than a typo. * docs(readme,asf): surface MISSION mode taxonomy README skill-families table gains a `Modes` column linking each family to docs/modes.md (security: A+C, pr-management: A, setup: infra). Updates the .asf.yaml github.description from "security vulnerabilities" to the broader "agent-assisted maintainership" framing the MISSION proposes — security is one mode of one family, not the project's identity. * docs(mission): cross-link MISSION § Technical scope to docs/modes.md The MISSION proposal lists the four modes but did not point at the honest snapshot of which modes are actually shipping. Add a one-line forward reference to docs/modes.md inside § Technical scope so a reader can move from "what we promise" to "what currently exists" without leaving the document. * docs(modes): align Mode C at-a-glance status with the legend The "Modes at a glance" row for Mode C used `partial (security-only)`, which is not a value defined in the Status legend. The detailed Mode C section already states the one shipping skill (security-issue-fix) is stable while the generic Mode C is proposed; mirror that wording in the at-a-glance row so the doc uses only legend-defined terms. Report URL: https://github.com/apache/airflow-steward/actions/runs/25425302543 With regards, GitHub Actions via GitBox --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
