chore: update openspec artefacts

Signed-off-by: Jérôme Benoit <jerome.benoit@piment-noir.org>

diff --git a/.opencode/command/openspec-proposal.md b/.opencode/command/openspec-proposal.md
index 096770ee9055e81ded82e69638aa8f80dbd89990..9282a4fd20e5d606471f2e27c9aef5d5ba7425ae 100644 (file)
--- a/.opencode/command/openspec-proposal.md
+++ b/.opencode/command/openspec-proposal.md
@@ -16,6 +16,7 @@ $ARGUMENTS
 - Keep changes tightly scoped to the requested outcome.
 - Refer to `openspec/AGENTS.md` (located inside the `openspec/` directory—run `ls openspec` or `openspec update` if you don't see it) if you need additional OpenSpec conventions or clarifications.
 - Identify any vague or ambiguous details and ask the necessary follow-up questions before editing files.
+- Do not write any code during the proposal stage. Only create design documents (proposal.md, tasks.md, design.md, and spec deltas). Implementation happens in the apply stage after approval.
 
 **Steps**