java-refactor-engram-contractlisted

# Java Refactor Engram Contract ## Activation Contract Use this skill for `java-refactor-anchor-first` and its workflow-private subagents when they exchange phase evidence through Engram. Do not use it for generic Java refactoring advice, testing technique selection, or non-Engram workflows. ## Hard Rules - The skill owns transport rules; agents own phase behavior. - Require `project` and `run_id` before any Engram access; do not infer them from cwd or session. - All workflow topics must match `java-refactor-anchor-first/{run_id}/...`, unless an exact caller allowlist explicitly overrides defaults. - Read Engram artifacts with `mem_search(query: topic_key, project: project, scope: "project")` followed by `mem_get_observation(id)`; search previews are never source material. - Write generated evidence with `mem_save`, exact `topic_key`, `scope: project`, `capture_prompt: false`, and `**What**/**Why**/**Where**/**Learned**` content. - Use topic-key upserts for evolving topics (`state`, `coverage`, `mutation`, `review-strategy`, `evidence-report`); use distinct topic keys for per-slice artifacts (`tcr-slice-{n}`). - Merge evolving `state`; never overwrite it with a partial snapshot. - Subagents do not talk to each other directly; the primary passes topic keys, not expanded artifacts. - Keep Engram artifacts compact. Do not save raw source, full tests, build files, coverage/mutation reports, logs, diffs, or broad file excerpts. ## Decision Gates | Condition | Action | |---|