easy-coding-harness 1.1.0-beta.1 → 1.1.0-beta.3

package/templates/runtime/memory/SHORT_MEMORY_TEMPLATE.md

@@ -11,14 +11,12 @@ domain:
 tags:
   - "{keyword}"
 related_files:
-  - "{key file or module}"
-commit: none
-verification: passed | partial | not_run
+  - "{entrypoint or file useful for applying this knowledge}"
 memory_value: business | technical | both | none
 target_long: BUSINESS | TECHNICAL | BOTH | NONE
 ---
 
-# Short Memory Template
+# {Reusable knowledge topic}
 
 > This template defines the format for files under `.easy-coding/memory/short/`.
 > File naming convention: `{memory_id}_{YYYYMMDD}_{smart_name}.md`
@@ -26,57 +24,32 @@ target_long: BUSINESS | TECHNICAL | BOTH | NONE
 > both the filename prefix and this frontmatter `id`. The UUIDv7 id is safe for concurrent agents.
 > Keep `smart_name` as the readable summary suffix.
 > `source_task` must exactly match the current workflow task id from `task.json`.
-> Short memories are immutable after creation — they serve as a sliding window of recent
-> details and a buffer for long-term distillation candidates.
-> When short memories reach the threshold (default 10), the newest 5 are kept as recent
+> Short memories are immutable and directly useful for later development before distillation.
+> When short memories exceed the threshold (default 10), the newest 5 are kept as recent
 > context; older entries are distillation candidates for long-term memory.
 > Sorting: by frontmatter `date` ascending, then by frontmatter `id`, then by filename. Legacy
 > `SM-YYYYMMDD-NNN` ids sort before UUIDv7 ids on the same date for upgrade compatibility.
 
-## Task Summary
+## Knowledge Summary
 
-- Goal: {the actual problem solved}
-- Scope: {modules, pages, interfaces, or files involved}
-- Result: {completed / partially completed / not completed, with reasons}
-- Key Constraints: {encoding, compatibility, interface, spec, or user-specified constraints; "none" if none}
-- Workflow Mode: {frozen mode and why it was selected or escalated}
+{When this knowledge is useful and the main conclusion a future developer should find.}
 
-## Execution Evidence
+## Reusable Knowledge
 
-| Type | Content |
-|---|---|
-| Key Files | {file or module list; "none" if none} |
-| Verification Commands | {test / build / lint commands and results; explain if not run} |
-| Manual Acceptance | {key behaviors checked; "none" if none} |
-| Commit Info | {commit hash; "none" if not committed} |
+{Write only confirmed facts with future reuse value. Use natural paragraphs or bullets; omit
+inapplicable categories rather than filling a checklist. Useful material includes business rules,
+design reasons, change entrypoints, compatibility boundaries, and failure causes with their fixes.
+Add applicable conditions, necessary reasons and exact symbols where they guide the next change.
+Do not promote a task-specific restriction into a permanent project rule.}
 
-## Business Memory Candidates
+## Sources
 
-> Only record business facts with future reuse value. Write "none" if none.
+- {Relevant dev-spec section, implementation result or Review finding; reference instead of copying.}
+- {Related memory or existing knowledge topic, only when useful.}
 
-- Concepts / Field Semantics: {concepts, fields, enums, state meanings}
-- Workflows / State Transitions: {chain steps, pre/post conditions, exception branches}
-- Business Rules / Compatibility: {admission criteria, decision basis, grayscale or legacy reasons}
-- Upstream/Downstream Contracts: {producers, consumers, interface or message fields}
-- Business Troubleshooting: {common misdiagnosis, priority check paths}
-
-## Technical Memory Candidates
-
-> Only record engineering facts with future reuse value. Write "none" if none.
-
-- Architecture / Interface Decisions: {module boundaries, dependency direction, interface contracts}
-- Engineering Rules / Workflows: {coding, commit, release, installation, directory boundaries}
-- Implementation Patterns / Reusable Approaches: {recommended approaches, fallback strategies, compatibility patterns}
-- Pitfalls / Fix Strategies: {root cause, fix approach, verification method}
-- Verification Experience: {test commands, environment constraints, acceptance paths}
-
-## Non-Distillation Content
-
-> Content that should NOT enter long-term memory, with reasons — prevents accidental absorption of noise.
-
-- {routine file lists / temp logs / one-time data / non-reusable implementation details; "none" if none}
-
-## Related Memories
-
-- Predecessor: {related short memory id, long-term topic, or "none"}
-- Successor: {follow-up task; "none" if none}
+> Authoring guidance, not memory content: remove these instructions and unused placeholders.
+> If nothing new is reusable, set `memory_value: none` and `target_long: NONE`, give a brief reason
+> in Knowledge Summary and retain Sources; omit Reusable Knowledge rather than inventing lessons.
+> Leave task status, approvals, fingerprints, test statistics and temporary logs in task records.
+> Keep a verification command only when it teaches a reusable method or environment requirement.
+> Do not include an acceptance report or a list of excluded noise.

package/templates/shared-hooks/easy_coding_inputs.py

@@ -40,6 +40,24 @@ def memo(key, compute):
     return cache[key]
 
 
+def invalidate_memo(key):
+    cache = _operation.get()
+    if cache is not None:
+        cache.pop(key, None)
+
+
+def cached_memo(key):
+    cache = _operation.get()
+    return cache.get(key) if cache is not None else None
+
+
+def command_identity(command):
+    # Shell 展开和重定向受引号影响；只归一化普通 argv 命令，避免错误复用。
+    if re.search(r"[\$`\\\n;|&<>*?\[\]{}~#]", command):
+        return command
+    return tuple(shlex.split(command))
+
+
 def digest(value):
     return hashlib.sha256(json.dumps(value, sort_keys=True, ensure_ascii=False,
                                      separators=(",", ":")).encode()).hexdigest()