chore(lunatask): work around API bug

Amolith created

Change summary

skills/creating-tasks-through-lunatask/SKILL.md | 4 ++++
skills/resuming-work-through-lunatask/SKILL.md  | 4 ++++
2 files changed, 8 insertions(+)

Detailed changes

skills/creating-tasks-through-lunatask/SKILL.md 🔗 

@@ -86,6 +86,10 @@ If the user confirms and it's/they're
 - **relevant to the handoff**: mention briefly in context section so the receiving agent is aware
 - **worth tracking separately**: suggest capturing as standalone task(s) so the user can pick up or hand off to another agent later. Even as standalone tasks, make sure to include enough context that another agent could pick it up.
 
+## Working around a Lunatask bug
+
+At the very very end of task notes or note contents, include `[editor_v2]::` on its own line.
+
 ---
 
 If `lunatask` or `lune` MCP tools are unavailable, see [cli.md](references/cli.md). If the CLI is also unavailable, see [installing-lune.md](references/installing-lune.md).

skills/resuming-work-through-lunatask/SKILL.md 🔗 

@@ -40,6 +40,10 @@ Don't derail the primary task, but don't let useful observations vanish either.
 
 When you begin working on the task, update its status according to the area's workflow. When finished, mark it `complete`.
 
+## Working around a Lunatask bug
+
+At the very very end of task notes or note contents, include `[editor_v2]::` on its own line.
+
 ---
 
 If `lunatask` or `lune` MCP tools are unavailable, see [cli.md](references/cli.md). If the CLI is also unavailable, see [installing-lune.md](references/installing-lune.md).