oh-my-customcode 0.88.0 → 0.88.1

package/dist/cli/index.js

@@ -2334,7 +2334,7 @@ var init_package = __esm(() => {
     workspaces: [
       "packages/*"
     ],
-    version: "0.88.0",
+    version: "0.88.1",
     description: "Batteries-included agent harness for Claude Code",
     type: "module",
     bin: {

package/dist/index.js

@@ -2007,7 +2007,7 @@ var package_default = {
   workspaces: [
     "packages/*"
   ],
-  version: "0.88.0",
+  version: "0.88.1",
   description: "Batteries-included agent harness for Claude Code",
   type: "module",
   bin: {

package/package.json

@@ -3,7 +3,7 @@
   "workspaces": [
     "packages/*"
   ],
-  "version": "0.88.0",
+  "version": "0.88.1",
   "description": "Batteries-included agent harness for Claude Code",
   "type": "module",
   "bin": {

package/templates/.claude/rules/MUST-completion-verification.md

@@ -10,7 +10,7 @@ Before declaring any task `[Done]`, verify completion against task-type-specific
 
 | Task Type | REQUIRED Verification Before [Done] |
 |-----------|-------------------------------------|
-| Release | All issues closed, version bumped, PR merged, GitHub Release created |
+| Release | All issues closed, version bumped, PR merged, GitHub Release created; **External automation verified**: `.github/workflows/` listed AND `gh run list --limit 10` checked for auto-publish workflows |
 | Implementation | Code compiles/passes lint, tests pass (if exist), no TODO markers left |
 | Documentation | Links valid, counts accurate, cross-references updated |
 | Git Operations | Operation succeeded (check exit code), working tree clean |
@@ -28,6 +28,19 @@ Before [Done]: (1) Verify ACTUAL outcome not just attempt — "ran command" ≠
 4. Would I bet $100 this is truly complete? YES: Declare [Done] / NO: Identify uncertain and verify
 -->
 
+## Subagent Self-Report Verification
+
+Subagents often report failures as "pre-existing", "baseline", or "unchanged". These claims MUST be verified against the base branch before acceptance.
+
+| Subagent Claim | Required Verification |
+|----------------|----------------------|
+| "X test already failing on base" | `git stash && git checkout {base} && run test X && compare` |
+| "This warning is pre-existing" | `git log -S "warning-text" {base}` or run on clean checkout |
+| "File was unchanged" | `git diff {base}..HEAD -- {file}` |
+| "Dependency issue not from this PR" | `git show {base}:package.json` compare |
+
+Never accept "pre-existing" without direct base-branch evidence. A false "pre-existing" claim can mask a regression introduced by the current change.
+
 ## Common False Completion Patterns
 
 | Pattern | Reality | Fix |
@@ -37,6 +50,8 @@ Before [Done]: (1) Verify ACTUAL outcome not just attempt — "ran command" ≠
 | "PR created" | CI not checked | Wait for CI, verify green |
 | "Issue closed" | Related issues not updated | Check parent epic, cross-refs |
 | "Tests pass" | Only ran subset | Run full test suite |
+| "Waiting for manual publish" | External CI/CD auto-publishes on merge | Check `.github/workflows/` BEFORE assuming manual step |
+| "Subagent said pre-existing" | Claim not verified against base branch | Run test on base branch, compare directly |
 
 ## Completion Contract Format
 
@@ -58,6 +73,24 @@ Then at completion:
 └── ✓ Criterion N: {evidence}
 ```
 
+## Autonomous Mode Entry Checklist
+
+When entering autonomous mode (user grants extended execution without per-step confirmation), perform this inventory BEFORE first action:
+
+1. **Workflow inventory**: `ls .github/workflows/` — identify auto-publish, auto-tag, release, docs-sync, CI workflows
+2. **Recent runs**: `gh run list --limit 10` — check success/failure patterns of automated workflows
+3. **External publish targets**: Check if npm/PyPI/Docker Hub/GitHub Releases are auto-triggered on merge
+4. **Manual intervention points**: Identify which steps require human approval vs. fully automated
+5. **Cross-reference with task**: Which workflows will the planned work trigger?
+
+Record findings in session context. Failure to inventory automation is a R020 violation (unknown external state = unverifiable completion).
+
+### Cross-reference
+
+Related memory records:
+- `feedback_github_workflows_inventory.md` — original incident (v0.87.2~v0.88.0 session)
+- `feedback_subagent_pre_existing_claims.md` — subagent false-positive pattern
+
 ## Integration
 
 | Rule | Interaction |

package/templates/.claude/rules/MUST-intent-transparency.md

@@ -37,6 +37,34 @@ Display reasoning when routing to agents. Users must always know which agent was
 
 Users can specify agent directly with `@{agent-name} {command}`. Override bypasses detection.
 
+## User Directive Persistence
+
+When a user explicitly names a tool, skill, or workflow (e.g., "use /pipeline auto-dev", "always run tests with bun test"), this preference persists for the entire session — including after autonomous mode transitions.
+
+### Persistence Triggers
+
+| User Statement Pattern | Persistence Scope |
+|------------------------|-------------------|
+| "use X for development" | Entire session |
+| "always / every time" | Entire session |
+| "from now on" | Entire session + memory save candidate |
+| "for this task" | Current task only |
+| Named slash command | Subsequent similar invocations |
+
+### Cycle Start Self-Check
+
+At the start of every work cycle (issue, task, release, or autonomous sub-loop):
+1. Review recent user messages in the conversation
+2. Identify any named tool/skill/workflow directives
+3. Apply those directives unless explicitly rescinded
+4. If unsure whether a directive applies, default to the stated preference
+
+**Anti-pattern**: Treating autonomous mode as a clean slate that discards earlier user preferences. Autonomous mode means "continue without per-step confirmation" — NOT "reset user directives".
+
+### Cross-reference
+
+- Related memory: session v0.87.2~v0.88.0 (issue #869) — `/pipeline auto-dev` preference was lost after autonomous mode transition
+
 ## Agent Triggers
 
 Defined in `.claude/skills/intent-detection/patterns/agent-triggers.yaml`. Each agent has keywords, file patterns, actions, and base confidence.

package/templates/.claude/rules/SHOULD-memory-integration.md

@@ -277,6 +277,30 @@ User Model data feeds into intent-detection (R015) and routing skill confidence
 
 -->
 
+## Mid-Session Immediate Save
+
+Save memory IMMEDIATELY upon surprising discovery — do not defer to session end.
+
+| Trigger | Action | Rationale |
+|---------|--------|-----------|
+| Repeated pattern observed (2nd time) | Save `feedback_*.md` now | Pattern will recur within session |
+| Unexpected tool behavior / workaround | Save `feedback_*.md` now | Session state defense |
+| Subagent false-positive detected | Save `feedback_*.md` now | Prevent repeat in same session |
+| User correction / feedback | Save `feedback_*.md` now | Honor correction immediately |
+
+### Why Immediate?
+
+Session-end saves lose context: by the time the session ends, multiple discoveries have compounded and nuance is lost. Immediate saves preserve the exact trigger context that makes the memory actionable.
+
+**Anti-pattern**: "I'll batch all learnings at session end" — by then you'll have forgotten WHY each one mattered, and further violations may have occurred using the un-saved pattern.
+
+### Cross-reference
+
+Related records from session v0.87.2~v0.88.0 (issue #869):
+- `feedback_subagent_pre_existing_claims.md`
+- `feedback_github_workflows_inventory.md`
+- `feedback_bun_mock_module.md`
+
 ## Session-End Auto-Save
 
 ### Trigger

package/templates/manifest.json

@@ -1,5 +1,5 @@
 {
-  "version": "0.88.0",
+  "version": "0.88.1",
   "lastUpdated": "2026-04-14T00:00:00.000Z",
   "components": [
     {