easy-coding-harness 0.4.0 → 0.5.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "easy-coding-harness",
-  "version": "0.4.0",
+  "version": "0.5.0",
   "description": "CLI scaffold for installing Easy Coding harness files into agent-native directories.",
   "repository": {
     "type": "git",

package/templates/common/skills/ec-git/SKILL.md

@@ -37,7 +37,12 @@ with `.easy-coding/sessions/` always excluded. The CLI already added it to `.git
    `repo_paths`), the commit/push covers every involved repo. Read `repo_paths` from the
    current task state to locate each checkout, check changes, and commit/push them as one
    coherent change set — do not leave a sub-repo behind.
-4. **No false success.** Never claim a commit or push succeeded without reading the command
+4. **Supermodule two-step commits.** If the current repo has `.gitmodules`, or the current
+   task touches a git submodule path, treat each submodule as an independent git boundary:
+   commit and push child repos first, then commit and push the parent gitlink update. If a
+   child repo is on a detached HEAD, stop and ask the user to choose or create a branch before
+   committing there.
+5. **No false success.** Never claim a commit or push succeeded without reading the command
    output. A failed push reported as success is a serious error.
 
 ## Boundaries
@@ -45,3 +50,6 @@ with `.easy-coding/sessions/` always excluded. The CLI already added it to `.git
 - Do not touch session files, task status fields, or run stage transitions — git only.
 - Do not commit `.easy-coding/sessions/`.
 - Do not commit `spec/dev/` unless the user explicitly asks.
+- In a supermodule task launched from the parent root, parent `.easy-coding/` belongs to the
+  parent git. Child `.easy-coding/memory/` changes created by memory archive belong to the
+  owning child git and must be committed before the parent gitlink update.

package/templates/common/skills/ec-memory/SKILL.md

@@ -45,6 +45,23 @@ conversation. Refer to SHORT_MEMORY_TEMPLATE.md for the complete section format.
 
 If the task was cross-repo, record the repo names involved and the collaboration reason.
 
+## Supermodule memory routing
+
+If the current project config contains `supermodule.role: super-parent`, archive memory by
+ownership:
+
+- Cross-repo business context, parent orchestration decisions, and multi-repo contracts stay
+  in the parent `.easy-coding/memory`.
+- Technical memory that belongs to one child repo must be written to that child's
+  `.easy-coding/memory`, not only to the parent. Use changed file paths and module ownership
+  to decide the child.
+- Only write child memory files during this routing. Do not edit child task, session, state,
+  or dev-spec files from the parent workflow.
+- If a touched child repo has no initialized `.easy-coding/memory` directory, keep the memory
+  in the parent and mark it as "original child: <path>; child not initialized".
+- When child memory is written, the later git flow must commit and push the child repo before
+  the parent gitlink update.
+
 **Immutability:** Short memories are write-once. Never edit an existing short memory file —
 create a new one instead. Short memories serve as both a recent-detail sliding window and a
 distillation buffer for long-term memory.

package/templates/main-constraint/AGENTS.md.tpl

@@ -62,6 +62,7 @@ First run `ec-init`; daily work goes through `ec-workflow`.
   creates the project-init task — agent skills perform all project analysis.
 - Cross-repo references in git-tracked task artifacts use repo NAMES, never local paths.
   Cache local paths only through the state script so they land on the current task.
+{{supermodule_boundary}}
 
 <!-- ═══ end easy-coding-harness generated ═══ -->
 

package/templates/main-constraint/CLAUDE.md.tpl

@@ -60,6 +60,7 @@ First run `/ec-init`; daily work goes through `/ec-workflow`.
   creates the project-init task — agent skills perform all project analysis.
 - Cross-repo references in git-tracked task artifacts use repo NAMES, never local paths.
   Cache local paths only through the state script so they land on the current task.
+{{supermodule_boundary}}
 
 <!-- ═══ end easy-coding-harness generated ═══ -->