Preserve Build Evidence from Hermes Agent Kanban Scratch Workspaces
Treat a Kanban scratch workspace as temporary. Declare the build report as a task attachment before completion or review. A reviewer then has a durable artifact even after the worker finishes and the dispatcher cleans up scratch storage.
- Scratch build
- Declare artifact
- Durable attachment
Choose where work should live
The Hermes Kanban documentation describes scratch, an existing absolute directory, and Git worktree modes. Choose scratch for generated evidence that can be declared explicitly. Choose a worktree when a reviewer needs the full source diff and working tree. A Git worktree separates checkouts, while OS permissions still determine filesystem access.
Use a configured development worker and a test board. In the task description instruct the worker to create a .NET console fixture, build it, and write a text report to its workspace. A safe repro is to create the fixture with dotnet new console -f net10.0, then capture dotnet build --nologo > build-report.txt 2>&1 and record the command's exit code separately. A redirected command can create a file even when the build fails. Spot-check the result before declaring success.
Declare exactly what the reviewer needs
Have the worker call the documented kanban_request_review or kanban_complete operation with an artifacts entry for the real report path. Inspect the tool schema exposed in the installed version for the entry shape. Use a small allowlisted file. Avoid attaching the full workspace, especially hidden files and provider configuration.
Open the task from a second reviewer session and confirm the attachment can be read. If there are secrets or absolute paths in a build log, generate a sanitized summary and attach that instead. Verify the sanitized attachment is readable and contains the command, revision, exit code and a concise error excerpt where relevant.
Verify the failure cases
In the test board, deliberately declare a missing report path and check whether the task remains in flight, as current docs describe. Correct the path and complete again. Then compare the durable attachment timestamp and checksum to the worker's reported result. If the task claims success but no report is visible, check if completion used an explicit artifact declaration in the right board.
Can I just leave a note with a scratch path? Prefer a declared attachment. A path into a deleted workspace cannot serve as durable evidence.
Is the attachment a backup? Retain important release evidence in the project's authorized artifact store with its own retention and access controls.
References
Official Hermes Agent documentation · ASP.NET PB on MCP tools and resources
Comments
Post a Comment