docs(lunatask): clarify status values and workflow

Amolith created 

- Fix 'complete' → 'completed' (correct status value)
- Document status progression: later → in-progress → completed

Assisted-by: Claude Opus 4.5 via Crush

Change summary

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

Detailed changes

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

@@ -31,13 +31,13 @@ Titles must be clear:
 
 Examples:
 
-- `Accept 'complete' as status alias in lune`
+- `Accept 'completed' as status alias in lune`
 - `Implement ACP event sink in Crush`
 - `Investigate why lune habit track silently fails`
 
 ### Status
 
-New tasks usually get status `later`.
+New tasks usually get status `later`. When beginning work on a task, update to `in-progress`, then completed when done (or use `done` shortcut).
 
 ### Note structure

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

@@ -38,7 +38,9 @@ Don't derail the primary task, but don't let useful observations vanish either.
 
 ## Workflow
 
-When you begin working on the task, update its status according to the area's workflow. When finished, mark it `complete`.
+When you begin working on the task, update its status according to the area's workflow. When finished, mark it `completed`.
+
+New tasks usually get status `later`, then `in-progress`, then lastly `completed`. Different workflows might have other stages, but those are core.
 
 ## Working around a Lunatask bug