Submit OpenSSF Best Practices badge applications

[hyperpolymath]

Manual browser task — submit multiple repos for OpenSSF Best Practices badges. Requires passing Scorecard checks, security policy, branch protection.

[hyperpolymath]

Tracked in roadmap as an explicit outstanding operational task:\n- stateful-artefacts/ROADMAP.md (commit 071baa6) now includes issue-linked OpenSSF badge submission backlog.\n\nLeaving open since this is still a manual browser flow after Scorecard/security-policy/branch-protection checks are green.

[hyperpolymath]

Triage ping (2026-05-30) — no activity since 2026-04-07.

This is a manual browser task that needs Scorecard checks, security policy + branch protection per repo. Given the recent estate Scorecard wrapper sweep (standards#282 / #303) is still in flight, the pre-conditions are moving.

Two paths:

• Wait for the Scorecard wrapper sweep + post-#282 audit to settle, then submit in one batch.
• Pick a small starter set (≤5 mature repos) to submit now and dogfood the process.

Suggest labelling manual-task + blocked and parking until the sweep settles, unless you want to start the dogfood pass.

[hyperpolymath]

cicd triage 2026-05-30 — OpenSSF Best Practices readiness check

The badge-application step is a manual browser task (https://www.bestpractices.dev/ submission); cannot be automated by me. Current readiness for the reposystem repo specifically:

Criterion	State
SECURITY.md	✅ present
.github/workflows/scorecard.yml	✅ present, wrapper-shape correct (has job-level {security-events,id-token}: write)
.github/workflows/scorecard-enforcer.yml	✅ present
README.adoc references	⚠️ no current OpenSSF badge reference
main branch protection	✅ enabled (required_reviews = 0)
Scorecard run status	⚠️ recent runs are startup_failure despite correct wrapper shape — needs separate investigation; estate-wide pattern from #303 / #282

Next step (owner action)

• Submit at https://www.bestpractices.dev/projects/new for each top-level repo deemed ready.
• The standards-cohort approach: gh search repos --owner hyperpolymath --json name | jq '.[].name' → filter to ones with the 4 criteria above → batch-apply in browser.

Leaving open as the badge submission itself isn't a code task. The recent estate-wide scorecard wrapper sweep (memory: session_2026_05_30_estate_ci_fanout_coordinator + #282/#303) is the prereq — once that converges, the badge-ready cohort is larger.