Skip to content

refactor(harness): unify request consequence recording - #77

Merged
MMinasyan merged 1 commit into
mainfrom
refactor/hook-recording
Oct 30, 2026
Merged

MMinasyan merged 1 commit into
mainfrom
refactor/hook-recording

Conversation

@MMinasyan

Copy link
Copy Markdown
Owner

Changes

  • Use one accepted request-consequence recorder for pure and effectful hooks, preserving validation, effect timing, adopted consequences and identity order.
  • Correct the message-name documentation: absent or empty names are unnamed; null and non-string names are rejected.

Tests

  • Existing request/argument-hook provenance, evidence ordering, empty tool selection and empty message-name checks passed.
  • Full Go suite, Wails build, formatting and diff checks passed.

@MMinasyan
MMinasyan merged commit eab8407 into main Oct 30, 2026
2 checks passed
@MMinasyan
MMinasyan deleted the refactor/hook-recording branch October 30, 2026 03:48
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