Skip to content

fix: add acceptance verifier registry - #14

Closed
matthias-scale wants to merge 2 commits into
fork/pr-basefrom
fix/acceptance-verifier-registry
Closed

fix: add acceptance verifier registry#14
matthias-scale wants to merge 2 commits into
fork/pr-basefrom
fix/acceptance-verifier-registry

Conversation

@matthias-scale

Copy link
Copy Markdown
Owner

Summary

Bootstrap the base-owned strict acceptance-verifier allowlist required before Protected admission can verify PR #13. The canonical schema permits only verifier IDs and exact trusted CI check names; it intentionally does not carry PR-authored commands or acceptance clauses.

herdr-check-ubuntu resolves to the existing GitHub Actions check (ubuntu-latest) job. That job runs just ci, covering Herdr Rust tests, integration assets, and repository maintenance tests. A subsequent typed contract can independently bind AC1 through AC12—including the session-scoped final-paragraph title behavior in AC12—to this base-owned verifier and receive one exact-head evidence record per clause.

Validation

  • python3 -m unittest scripts.test_acceptance_verifier_registry (red before registry, green after)
  • Canonical issue-acceptance-criteria.py loader accepts the committed registry by full SHA
  • Pinned just check-parallel (all lanes passed)

No live Herdr, preview, or PR #13 content was modified.

@matthias-scale

Copy link
Copy Markdown
Owner Author

Closing as superseded. The keyboard fix this PR describes is already on fork/pr-basesrc/pane.rs sends \x1b[>5u\x1b[>4;2m… and src/main.rs uses ime_compatible_keyboard_enhancement_flags() — so none of @fabiorizzomatos's work is lost here.

The branch's remaining QA files are older than current base; checking them out would delete 159 lines of since-evolved script. The one piece that was still undelivered, the acceptance verifier registry, is revived against current base in #51.

Branch is left intact.

matthias-scale added a commit that referenced this pull request Aug 11, 2026
Names `check (ubuntu-latest)` as herdr's trusted acceptance verifier so /amerge can bind a Deep+ ci_surface to a real check instead of guessing from the rollup. The test pins the registry contents and asserts the three ci.yml facts it depends on, so a workflow rename breaks the test rather than silently voiding the mapping.

Revives the only undelivered content of #14; that branch's keyboard fix is already on fork/pr-base and its other QA files are older than base.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants