Maintainer actions after v1.5.0: fixture run, next skills release decisions, GHE pilot package #71

Maintainer actions left open after the v1.5.0 release (2026-09-05). Each item is blocked on a human step; the preparation is done and linked.

Run the full fixture review (#17)

• Open a Claude Code session in ~/tmp/pkgreviewtest (a private throwaway, remote openwashdata/pkgreviewtest, commit bc6d62e) and type /review-package; follow the refreshed procedure in the Run the fixture review: acceptance gate for PR #14 #17 comment of 2026-09-05
• Score the run against fixtures/SCORECARD.md (17 defects by area, no unmapped finding, no guardrail violation) and record the result on Run the fixture review: acceptance gate for PR #14 #17
• Afterwards: gh repo delete openwashdata/pkgreviewtest --yes and remove ~/tmp/pkgreviewtest

Decide the next skills release

• Design: an unattended review mode that stops only where the standard requires a human #69, unattended review mode: choose A, B, or C (recommendation posted: B first, A after one clean B run)
• Explore: align /create-release with posit-dev/skills release practice, and evaluate a release-post skill #55, release practice: choose which of the remaining items to take (recommendation posted: the add-doi-style preflight, use_dev_version() after the dev sync, a NEWS bullet per review PR; defer the rest)
• Record the decisions at the top of each issue; both ship together as one skills release

Name the Global Health Engineering pilot package (#50)

• Name the GHE data package for the first review under the global-health-engineering profile; the pilot verifies the Zenodo community slug and the funding sidebar text (Phase 0: capture Global-Health-Engineering conventions for the first non-openwashdata org profile #48 decisions 5 and 7)

Later, not blocked on you

• Decision: scope of pkgreview-check.R once washr ships check_publication_readiness() (washr #82) #66: swap the frozen check-script sections for washr::check_publication_readiness() when check_publication_readiness(): workflow status gates (port fairenough's validate_* design) washr#82 ships (item list posted there)

v1.6.0 (workflow release, PR opened 2026-09-06)

• Merge the v1.6.0 PR once the gate, washr-drift, and lint jobs are green, then run bash scripts/release.sh 1.6.0 from main (done 2026-09-06: PR Release v1.6.0: CI gate, release tail, plugin manifests, org YAML, review-upgrade #81 merged at a11cf53, tag v1.6.0, GitHub release created, dev synced, skills copy installed)
• Merge PR Fix the main-branch tag check after a release merge #82 (CI-only fix: the main-branch tag check raced the tag push after the v1.6.0 release and left main red; no version bump; merged 2026-09-06 at 38bb9a4)
• Add the permission allowlist to .claude/settings.json (JSON on Release tail: one script or tag action, plus a permission allowlist for its commands #73); a session cannot write permission rules
• Try the plugin install on this machine after removing the copies in ~/.claude/skills/ (claude plugin marketplace add openwashdata/pkgreview, claude plugin install pkgreview@pkgreview); report on Distribute the skills as a Claude Code plugin instead of copying skills/ by hand #75 whether ${CLAUDE_SKILL_DIR} resolves the shared references and the skills invoke
• Automate the interactive fixture gate or retire it; scripted throwaway setup #80 task 3 at the next release: keep or retire the interactive gate text (claude plugin eval is early access on this account; findings on Automate the interactive fixture gate or retire it; scripted throwaway setup #80)