ponder

Apply plan - Target sync, symlink preservation, and backup lifecycle in EveryInc/compound-engineering-plugin

compound-engineering-plugin · lens architecture · 3 open findings at severity must or above · generated 2026-10-28T15:12:49.179Z

Work top to bottom. Ponder does not edit source - this plan is the handoff.

1. Codex target writer & symlink/manifest cleanup (src/targets/codex.ts) module.targets.codex

src/targets/codex.ts

• f-0001 · must · score 1 · effort s - Codex prompt writer bypasses symlink and ownership checks, clobbering user symlinks and deleting them on cleanup In src/targets/codex.ts:57-61, prompts are written directly via writeText(targetPath, content) (fs.writeFile) without checking if targetPath is a user symlink or unmanaged file, and are unconditionally recorded in writeInstallManifest (codex.ts:177). By contrast, skills and agents call cleanupCurrentManagedSkillDir and cleanupCurrentManagedAgentFile (codex.ts:364-403) to preserve user symlinks and unmanaged files. In addition, cleanupRemovedPrompts (codex.ts:326-338) omits if (await isPreservedSymlink(entryPath)) continue. Evidence: src/targets/codex.ts:57-61, src/targets/codex.ts:177, src/targets/codex.ts:326-338, src/targets/codex.ts:364-403 Do: In src/targets/codex.ts:57-61, check await cleanupCurrentManagedPromptFile(targetPath, prompt.name, ownedPrompts, backupDir) before writeText, only include written prompt names in writeInstallManifest (line 177), and add if (await isPreservedSymlink(entryPath)) continue to cleanupRemovedPrompts (line 331).

2. Pi target writer, extension bundler & legacy artifact cleanup (src/targets/pi.ts) module.targets.pi

src/targets/pi.ts

• f-0002 · must · score 1 · effort s - Pi prompt and extension writers clobber user symlinks and cleanupKnownLegacyPiArtifacts ignores prompt ownership In src/targets/pi.ts:95-99 and 150-154, both prompts and extensions call writeText directly without checking for preserved symlinks or unmanaged files, while cleanupRemovedPrompts (pi.ts:407-419) and cleanupRemovedExtensions (pi.ts:421-433) omit isPreservedSymlink checks. Furthermore, cleanupKnownLegacyPiArtifacts (pi.ts:532-535) and cleanupPi (src/commands/cleanup.ts:411-413) move legacy prompts without checking ownedPrompts (unlike codex.ts:428-430). Evidence: src/targets/pi.ts:95-99, src/targets/pi.ts:150-154, src/targets/pi.ts:407-433, src/targets/pi.ts:532-535, src/commands/cleanup.ts:411-413 Do: Apply managed-file ownership and symlink checks before writing Pi prompts/extensions, add isPreservedSymlink guards to cleanupRemovedPrompts/cleanupRemovedExtensions, and check ownedPrompts in cleanupKnownLegacyPiArtifacts and cleanupPi.

3. OpenCode config & command writer (src/targets/opencode.ts) module.targets.opencode

src/targets/opencode.ts

• f-0003 · must · score 2 · effort xs - Idempotent OpenCode installs accumulate unbounded .bak. files inside .opencode/commands/ and opencode.json In src/targets/opencode.ts:123 and 169-174, writeOpenCode calls backupFile(paths.configPath) and backupFile(commandPath) unconditionally before writing without comparing incoming content against existing file content on disk (unlike src/targets/codex.ts:218-227). Every idempotent install or sync creates a new .md.bak. inside the live .opencode/commands/ directory. Evidence: `src/targets/opencode.ts:123`, `src/targets/opencode.ts:169-174`, `src/targets/codex.ts:218-227` Do: In src/targets/opencode.ts:123 and 169-174, read existingContent via fs.readFile(path, "utf8").catch(() => null) and skip backupFile + writeText when existingContent === content (mirroring src/targets/codex.ts:218-227).

Shape of the work

3 modules · 3 findings · effort 1×xs, 2×s

---

Generated by Ponder - AI that knows when to speak, and when to shut up.

This site is open source. Improve this page.