@phi-code-admin/phi-code 0.80.0 → 0.81.0

package/CHANGELOG.md

@@ -1,5 +1,21 @@
 # Changelog
 
+## [0.81.0] - 2026-06-14
+
+Marathon increment 4 (prompt-only, low risk).
+
+### Changed
+
+- **Memory discipline.** The per-turn reminder now tells the model to (1) save only
+  non-obvious, cross-session facts (not what git already records) and (2)
+  verify-before-trust: a recalled note describes a PAST state, so confirm it against
+  the live code before acting, and the current observation wins on conflict.
+- **REVIEW final sweep.** On large diffs, the reviewer re-reads the diff once more
+  as if fresh and adds only genuinely new bugs (no padding).
+- **Run Recipe.** EXPLORE records a `## Run Recipe` (build/run command, port, ready
+  signal) in the brief; TEST uses it to actually run the code and to tell a real
+  failure (FAIL) from a stale launch recipe (BLOCKED).
+
 ## [0.80.0] - 2026-06-14
 
 Marathon increment 3: context protection, productivity commands, and the

package/extensions/phi/memory.ts

@@ -665,9 +665,15 @@ REMINDER (project rule, applies every turn):
    project context, prior decisions, and saved learnings are accessible
    ONLY via this tool.
 2. AFTER completing significant work, call \`memory_write\` to save what
-   you did and learned.
-
-These two tool calls are not optional. Skipping them violates project rules.
+   you did and learned. Save only NON-OBVIOUS, cross-session facts and user
+   preferences; do NOT save what the repo or git history already records.
+3. Saved notes describe a PAST state. Before you act on a recalled fact,
+   verify it against the CURRENT code (read/grep that the path or symbol still
+   exists). If it conflicts, the live observation wins. Do not delete a stale
+   note; note the divergence.
+
+The memory_search and memory_write calls are not optional. Skipping them
+violates project rules.
 </system-reminder>
 
 `;

package/extensions/phi/orchestrator.ts

@@ -414,6 +414,7 @@ export default function orchestratorExtension(pi: ExtensionAPI) {
    - Requirements: specific features needed
    - Tech decisions: frameworks, patterns to use
    - Constraints: what to NOT break
+   - Run Recipe: from package.json scripts / Makefile / Dockerfile / README, a \`## Run Recipe\` with the build command, run command, port/URL, and ready signal (the TEST phase uses this to actually run the code)
 5. **MANDATORY:** Write your findings to \`.phi/plans/explore-${ts}.md\` using the \`write\` tool. This file is READ by Phase 2 PLAN — if you skip it, the plan agent has no context. Do NOT skip this step.
 
 **LAST ACTION (MANDATORY):** Call \`memory_write\` to save your exploration findings for downstream agents.
@@ -580,6 +581,8 @@ $ <command actually executed>
 - Error: ... -> Fix: ...
 \`\`\`
 
+**Launch:** if the brief contains a "## Run Recipe" (build command, run command, port/URL, ready signal), use it. Distinguish a real failure (FAIL) from a stale launch recipe (BLOCKED) and report the recipe that actually works.
+
 **Verdict rules:** PASS only if you OBSERVED every feature working at runtime. When in doubt, FAIL. No partial pass (3/4 working = FAIL). Use BLOCKED only when you could not run anything (broken launch recipe, missing env, provider down) and say what is needed.
 
 **CRITICAL RULES:**
@@ -640,6 +643,8 @@ After testing, use \`memory_write\` to save test results, bugs found, and lesson
 - path/file.ts:123 - <what must change and why>
 \`\`\`
 
+**Final sweep (large diffs only):** before writing the verdict, re-read the diff once more as if you had never seen it; add ONLY bugs not already in your list. If there are none, do not pad.
+
 **Verdict rules:** VERDICT: FAIL if there is ANY CONFIRMED correctness/security finding (it goes under BLOCKING). VERDICT: PASS only if BLOCKING is empty. Do NOT pad: if the code is clean, return PASS with no findings.
 
 After your review, use \`memory_write\` ONCE to save:

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@phi-code-admin/phi-code",
-	"version": "0.80.0",
+	"version": "0.81.0",
 	"description": "Coding agent CLI with persistent memory, sub-agents, intelligent routing, and orchestration",
 	"type": "module",
 	"piConfig": {