justinmclean opened a new pull request, #468:
URL: https://github.com/apache/airflow-steward/pull/468
## Summary
Reconcile the plan with what has actually shipped and trim it to the
work that's still open.
- "Already in place": Pairing and Mentoring now list both shipped skills
each; contributor (nomination/activity-sweep/committer-onboarding) and
drafting (issue-fix-workflow/audit-finding-fix) skills recorded as
landed; spec-validator and agent-isolation Python packaging noted;
eval coverage marked complete (37 suites incl. the full setup family).
- Remove the "In-flight work" section: it tracked local branches and
unmerged PRs that no one else can see, so it was noise in a shared plan.
- Reprioritise the remaining work items down to the two still open
(prompt-injection defence hardening, license-header enforcement) and
drop the items that are now done.
- Add a next-pass note that adapters.md still needs a full read.
-
## Type of change
<!-- Tick all that apply. -->
- [ ] Skill change (`.claude/skills/<name>/`) — eval fixtures updated below
- [ ] Tool / bridge contract (`tools/<system>/*.md`)
- [ ] Python package (`tools/*/` with `pyproject.toml`)
- [ ] Groovy reference impl
- [ ] Cross-cutting (RFC, AGENTS.md, sandbox, privacy-LLM)
- [ ] Documentation (`docs/`, `README.md`, `CONTRIBUTING.md`)
- [ ] Project template (`projects/_template/`)
- [ ] CI / dev loop (`prek`, workflows, validators)
- [X] Other: update plan
## Test plan
- [X] `prek run --all-files` passes
- [ ] For Python packages touched: `uv run pytest` / `ruff check` / `mypy`
passes
- [ ] For Groovy bridges touched: command-line invocation tested end-to-end
- [ ] For skill changes: eval suite passes for the affected skill
(`PYTHONPATH=tools/skill-evals/src python3 -m skill_evals.runner
tools/skill-evals/evals/<skill>/`)
- [ ] For skill *behaviour* changes: a new or updated eval fixture is
included in this PR
(a regression test for the bug fixed / the behaviour added — see
CONTRIBUTING.md)
- [ ] Other:
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
