Skip to content

test(fixtures): add execution recovery contract pack v1 - #97

Open
mohamedwael201193 wants to merge 1 commit into
KeeperHub:mainfrom
mohamedwael201193:feat/execution-recovery-contract-pack-v1
Open

test(fixtures): add execution recovery contract pack v1#97
mohamedwael201193 wants to merge 1 commit into
KeeperHub:mainfrom
mohamedwael201193:feat/execution-recovery-contract-pack-v1

Conversation

@mohamedwael201193

Copy link
Copy Markdown

Summary

Test plan

  • Port/load fixtures under testdata/execution_recovery_v1/ in Go tests
  • Assert decision table in docs/execution-recovery-v1/contract.md
  • Confirm fixture IDs are synthetic / DEMO FIXTURE labeled

Refs: #53

Adds golden status envelopes and recovery rules for KeeperHub#53.
Does not implement --require-verified (see KeeperHub#95).
suisuss added a commit that referenced this pull request Aug 11, 2026
…98)

* docs: KEEP-1132 add contribution guide and require an accepted issue

This repo had no CONTRIBUTING.md. Adds one covering the real build
(make build/test/lint, the sync-version step, `go generate ./docs/` which
CI fails on drift) and ISSUES.md as the contribution policy.

Anything that changes command behaviour needs an issue marked `accepted`
before the pull request, referenced in the PR title after the
conventional-commit type (`feat: #97 description`). The type prefix still
drives release-please.

Issue forms and pr-issue-link.yml match the keeperhub setup, retargeted to
main since this repo has no staging branch.

Needs before this is useful: the `accepted`, `needs-triage` and
`no-issue-required` labels.

* docs: KEEP-1132 require reason, scope and plan on every issue

Mirrors the keeperhub change. Issue forms restructured around three
required parts: reason (command, output, expectation and its source, what
it costs), scope (commands affected, siblings checked, one problem), and
plan (the filer's proposal, which triage may replace in a comment before
accepting).

Adds `confirmed` so reproducing an issue is separable from deciding to
fix it.

* docs: KEEP-1132 never bounce an issue for its format

Mirrors the keeperhub change: nothing applies retroactively, a filer is
never asked to restate what they already said, and compound issues are
split by us with the reporter credited on each part.
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.

1 participant