From a293f5c228526e2d4a33ea46b5560e40eff27438 Mon Sep 17 00:00:00 2001 From: Lee Overy Date: Sun, 26 Jul 2026 17:04:14 +0100 Subject: [PATCH] fix(discussion-entry): the handoff reports the source it actually had MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit One arm serves both `fresh` and `topic-provided` and hardcoded `Source: fresh`, so a discussion arriving with a topic already chosen — from the map, or a continue menu — told the processing skill it was a direct entry. Found by a prose-test walker, which recorded it as a DEVIATION on a case that otherwise passed: a marker is a finding in its own right. Scope checked before changing anything: the sibling entry skills carry a `Source:` line only in single-source arms, where the fixed wording is accurate. This was the one multi-source arm stating a constant. Impact is narrower than it first looks — nothing in workflow-discussion-process reads `Source:`, so this is context handed downstream being wrong rather than a branch being taken wrongly. Worth correcting; not worth overstating. Co-Authored-By: Claude Opus 5 --- skills/workflow-discussion-entry/references/invoke-skill.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/skills/workflow-discussion-entry/references/invoke-skill.md b/skills/workflow-discussion-entry/references/invoke-skill.md index 827e348e5..cdb0f31b4 100644 --- a/skills/workflow-discussion-entry/references/invoke-skill.md +++ b/skills/workflow-discussion-entry/references/invoke-skill.md @@ -72,7 +72,7 @@ Invoke the **workflow-discussion-process** skill (Skill tool) with the next fenc ``` Discussion session for: {topic} Work unit: {work_unit} -Source: fresh +Source: {source} Output: {output_path} Description: