From 1aa98a805183f05f33a20d3be7c6d572ec98e091 Mon Sep 17 00:00:00 2001 From: Harald Hoyer Date: Thu, 7 May 2026 05:45:35 +0200 Subject: [PATCH] fix(opencode): require real shell timestamp in workflow summary MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit A workflow run wrote the timestamp as `2026-05-06T???:???:?? (session date)` because the agent had no time-of-day source and inserted a placeholder. Phase 9 now mandates capturing the timestamp from the shell at write time via `date -Iseconds` and forbids placeholders — omit the field rather than fabricate one. --- config/opencode/commands/workflow.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/config/opencode/commands/workflow.md b/config/opencode/commands/workflow.md index 2402427..f1b21ae 100644 --- a/config/opencode/commands/workflow.md +++ b/config/opencode/commands/workflow.md @@ -323,7 +323,7 @@ The workflow is forge-agnostic. It commits locally and stops. **Do not push, and ### Local Summary - Write `.opencode/workflow-summary.md` in the worktree with: - - Run timestamp + - **Run timestamp** — capture it from the shell at write time: `date -Iseconds` (e.g. `2026-05-07T11:24:13+02:00`). **Do not** use a placeholder like `???:???:??` or "session date" — if you cannot get a real timestamp, omit the field entirely rather than fabricating one. - Issue reference and title - Branch name and final commit SHA(s) - Summary of implementation