From 6a402bf556664157f3ed106a73f18f3f4dafc711 Mon Sep 17 00:00:00 2001 From: claude Date: Sat, 5 Sep 2026 21:51:43 +0400 Subject: [PATCH] docs: add action-resolution boundary slice report --- docs/reports/2026-09-05-action-resolution-boundary.md | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/docs/reports/2026-09-05-action-resolution-boundary.md b/docs/reports/2026-09-05-action-resolution-boundary.md index 1dd12d2..8ed1beb 100644 --- a/docs/reports/2026-09-05-action-resolution-boundary.md +++ b/docs/reports/2026-09-05-action-resolution-boundary.md @@ -124,6 +124,12 @@ No ambiguity uncovered. The boundary is clean: The eval harness `Reach()` now uses the same `ResolveActionCandidate` function, eliminating the previous duplication. -## 11. Commit hash +## 11. Commit hashes -Pending. +Three commits, split to stay under the 300-line pre-commit cap: + +``` +f6d7b05 mavend: add action-resolution regression tests +025f81e mavend: wire resolveAction into actionAct +064747f router: add ActionCandidate type and ResolveActionCandidate +```