@loneexile/omp-superpowers 7.0.1-omp.3 → 7.0.1-omp.4

package/.pi/extensions/superpowers.ts

@@ -1,4 +1,4 @@
-import { existsSync, readFileSync, readdirSync } from "node:fs";
+import { readFileSync } from "node:fs";
 import { dirname, resolve } from "node:path";
 import { fileURLToPath } from "node:url";
 import type { ExtensionAPI } from "@earendil-works/pi-coding-agent";
@@ -10,15 +10,8 @@ const extensionDir = dirname(fileURLToPath(import.meta.url));
 const packageRoot = resolve(extensionDir, "../..");
 const skillsDir = resolve(packageRoot, "skills");
 const bootstrapSkillPath = resolve(skillsDir, "using-superpowers", "SKILL.md");
-const SKILL_URL = /skill:\/\/([a-z0-9][a-z0-9-]*)/g;
-// An SDD workspace directory, as sdd-workspace prints it or as part of a path
-// into it; the ledger is its progress.md. Dot-names (`.gitignore`) and the old
-// flat `.superpowers/sdd/progress.md`, which SDD's own text mentions, are not plans.
-const SDD_WORKSPACE = /[^\s"'`()<>[\]\\]*\.superpowers\/sdd\/[A-Za-z0-9_-]+(?![\w.-])/g;
-const MAX_SKILLS_NAMED = 4;
 
 let cachedBootstrap: string | null | undefined;
-let cachedSkillNames: Set<string> | undefined;
 
 export default function superpowersPiExtension(pi: ExtensionAPI) {
 	let injectBootstrap = true;
@@ -35,13 +28,6 @@ export default function superpowersPiExtension(pi: ExtensionAPI) {
 		injectBootstrap = true;
 	});
 
-	// The compaction summary does not carry skill text. Name the superpowers
-	// skills read before it and the plan's ledger, so the agent reads them again.
-	pi.on("session.compacting", async (event) => {
-		const context = compactionContext(event?.messages ?? []);
-		return context.length > 0 ? { context } : undefined;
-	});
-
 	pi.on("session_switch", async () => {
 		injectBootstrap = true;
 	});
@@ -59,17 +45,9 @@ export default function superpowersPiExtension(pi: ExtensionAPI) {
 		const bootstrap = getBootstrapContent();
 		if (!bootstrap) return;
 
-		const content: Array<{ type: "text"; text: string }> = [{ type: "text", text: bootstrap }];
-		// After a compaction, name the superpowers skills and ledger used before it.
-		// Read from the session branch, so it holds whatever the compaction method
-		// and also after a restart or `omp -c`.
-		if (event.messages.some((message) => field(message, "role") === "compactionSummary")) {
-			const note = compactionContext(messagesBeforeLatestCompaction(ctx));
-			if (note.length > 0) content.push({ type: "text", text: note.join("\n") });
-		}
 		const bootstrapMessage = {
 			role: "user" as const,
-			content,
+			content: [{ type: "text" as const, text: bootstrap }],
 			timestamp: Date.now(),
 		};
 
@@ -133,96 +111,6 @@ From omp 18.4.12 every subagent is told to leave builds, tests and smoke runs to
 If your tools include \`vibe_spawn\` but not \`task\`, omp's vibe mode is on and you are its director: you have none of the \`task\`, \`bash\`, \`edit\` or \`write\` tools named above. Read the "Vibe mode" section of \`skill://using-superpowers/references/pi-tools.md\` before acting on them.`;
 }
 
-// Reads one property of an unknown value; undefined unless it is an object holding it.
-function field(value: unknown, key: string): unknown {
-	return value !== null && typeof value === "object" && key in value ? Reflect.get(value, key) : undefined;
-}
-
-function messagesBeforeLatestCompaction(ctx: unknown): unknown[] {
-	const sessionManager = field(ctx, "sessionManager");
-	const getBranch = field(sessionManager, "getBranch");
-	if (typeof getBranch !== "function") return [];
-	let entries: unknown;
-	try {
-		entries = getBranch.call(sessionManager);
-	} catch {
-		return [];
-	}
-	if (!Array.isArray(entries)) return [];
-	let end = -1;
-	entries.forEach((entry, index) => {
-		if (field(entry, "type") === "compaction") end = index;
-	});
-	return entries
-		.slice(0, Math.max(end, 0))
-		.filter((entry) => field(entry, "type") === "message")
-		.map((entry) => field(entry, "message"));
-}
-
-function compactionContext(messages: unknown[]): string[] {
-	const ours = superpowersSkillNames();
-	const skills: string[] = [];
-	let ledger: string | undefined;
-
-	for (const message of messages) {
-		for (const part of contentParts(message)) {
-			if (part.type === "toolCall") {
-				const args = JSON.stringify(part.arguments ?? {});
-				for (const match of args.matchAll(SKILL_URL)) {
-					const name = match[1];
-					if (!ours.has(name)) continue;
-					const seen = skills.indexOf(name);
-					if (seen !== -1) skills.splice(seen, 1);
-					skills.push(name);
-				}
-				ledger = lastLedgerPath(args) ?? ledger;
-			} else if (part.type === "text" && typeof part.text === "string") {
-				ledger = lastLedgerPath(part.text) ?? ledger;
-			}
-		}
-	}
-
-	if (skills.length === 0) return [];
-	const named = skills.slice(-MAX_SKILLS_NAMED).map((name) => `skill://${name}`).join(", ");
-	const lines = [
-		`Superpowers skills in use before this compaction (most recent last): ${named}. This summary does not carry their text: before your next step, read again the ones you are still following.`,
-	];
-	if (ledger) {
-		lines.push(`Superpowers ledger: ${ledger}. Read it before you continue; it records what is done and what is next.`);
-	}
-	return lines;
-}
-
-function superpowersSkillNames(): Set<string> {
-	if (cachedSkillNames) return cachedSkillNames;
-	try {
-		cachedSkillNames = new Set(
-			readdirSync(skillsDir, { withFileTypes: true })
-				.filter((entry) => entry.isDirectory() && existsSync(resolve(skillsDir, entry.name, "SKILL.md")))
-				.map((entry) => entry.name),
-		);
-	} catch {
-		cachedSkillNames = new Set();
-	}
-	// The bootstrap re-injects using-superpowers after every compaction already.
-	cachedSkillNames.delete("using-superpowers");
-	return cachedSkillNames;
-}
-
-function contentParts(message: unknown): Array<{ type?: unknown; text?: unknown; arguments?: unknown }> {
-	const content = field(message, "content");
-	if (typeof content === "string") return [{ type: "text", text: content }];
-	if (!Array.isArray(content)) return [];
-	return content
-		.filter((part) => part !== null && typeof part === "object")
-		.map((part) => ({ type: field(part, "type"), text: field(part, "text"), arguments: field(part, "arguments") }));
-}
-
-function lastLedgerPath(text: string): string | undefined {
-	const matches = text.match(SDD_WORKSPACE);
-	return matches ? `${matches[matches.length - 1]}/progress.md` : undefined;
-}
-
 function messageContainsBootstrap(message: unknown): boolean {
 	const content = (message as { content?: unknown }).content;
 	if (typeof content === "string") return content.includes(BOOTSTRAP_MARKER);

package/CHANGELOG.md

@@ -6,6 +6,12 @@ A version is `<upstream version>-omp.<n>`: the upstream release this fork is syn
 
 ## [Unreleased]
 
+## [7.0.1-omp.4] - 2026-10-24
+
+### Removed
+
+- **The post-compaction note from 7.0.1-omp.3.** After a compaction, the bootstrap no longer names the superpowers skills read before it and the SDD ledger, and `session.compacting` no longer hands those lines to the summarizer; the extension is back to 7.0.1-omp.2's. The note never changed behavior in testing on omp 18.12.6, with memory and the advisor off. With and without it, a brainstorm-then-build run compacted mid-conversation re-read the brainstorming skill in 5 of 5 runs. A six-task subagent-driven-development run compacted after its first wave re-read the SDD skill and the ledger before its next dispatch, redid no finished task and finished the plan in 2 of 2 runs, both with the usual summary and with a summary told to leave out skills, plans and ledgers plus a 1,000-token kept window. The note's only visible effect was an extra read of every skill it listed: both of those last runs also re-read `using-git-worktrees`. It has little to add on omp: each compaction method tried kept the list of files the session wrote, which in an SDD run includes the ledger under `.superpowers/sdd/`. With a plain-text summary that named the skill nowhere, the model still named the SDD skill and the ledger path from memory, without tools.
+
 ## [7.0.1-omp.3] - 2026-10-24
 
 ### Added
@@ -143,7 +149,8 @@ First release, synced to upstream [v6.4.2](https://github.com/obra/superpowers/b
 - The fork's rewritten subagent-driven-development text invokes its helper scripts through `bash` as well, so a package extractor that drops exec bits cannot break them.
 - `sdd-final-reviewer` carries upstream's new review rules from `code-reviewer.md`, the template it replaces in SDD's final review: the spec is a vision document (behavior it is silent on is graded by what a reasonable person expects), and a "Declined to judge" section that the controller rules on and ledgers like a plan conflict.
 
-[Unreleased]: https://github.com/LoneExile/omp-superpowers/compare/v7.0.1-omp.3...HEAD
+[Unreleased]: https://github.com/LoneExile/omp-superpowers/compare/v7.0.1-omp.4...HEAD
+[7.0.1-omp.4]: https://github.com/LoneExile/omp-superpowers/releases/tag/v7.0.1-omp.4
 [7.0.1-omp.3]: https://github.com/LoneExile/omp-superpowers/releases/tag/v7.0.1-omp.3
 [7.0.1-omp.2]: https://github.com/LoneExile/omp-superpowers/releases/tag/v7.0.1-omp.2
 [7.0.1-omp.1]: https://github.com/LoneExile/omp-superpowers/releases/tag/v7.0.1-omp.1

package/README.md

@@ -221,7 +221,7 @@ In short: the omp extension and `pi-tools.md` describe omp's real tools; five `s
 <details>
 <summary><b>File by file</b></summary>
 
-- `.pi/extensions/superpowers.ts` — the injected mapping names `task`, `todo`, the `sdd-*` roster, and the no-`model:`-field rule; it also re-arms on `session_switch`, skips subagent sessions, and ignores an `agent_end` that will auto-continue; it tells a dispatching session to name the checks each subagent must run, since omp 18.4.12 tells subagents to leave builds, tests and smoke runs to the main agent unless their assignment explicitly instructs them; its last paragraph points a vibe-mode director (tools include `vibe_spawn` but not `task`) at the *Vibe mode* section of `pi-tools.md`; after a compaction, the re-injected bootstrap also names the superpowers skills read before it and the last SDD ledger path, read from the session branch so it holds for any compaction method and after `omp -c`, and `session.compacting` hands the same lines to the summarizer
+- `.pi/extensions/superpowers.ts` — the injected mapping names `task`, `todo`, the `sdd-*` roster, and the no-`model:`-field rule; it also re-arms on `session_switch`, skips subagent sessions, and ignores an `agent_end` that will auto-continue; it tells a dispatching session to name the checks each subagent must run, since omp 18.4.12 tells subagents to leave builds, tests and smoke runs to the main agent unless their assignment explicitly instructs them; its last paragraph points a vibe-mode director (tools include `vibe_spawn` but not `task`) at the *Vibe mode* section of `pi-tools.md`
 - `.omp-plugin/plugin.json` — new. Marks the repo root as an omp-native plugin so a marketplace or `--plugin-dir` install keeps each agent's `model:` line
 - `skills/using-superpowers/references/pi-tools.md` — same, as the reference doc; it also gains a *Checks* subsection (the 18.4.12 subagent hand-off rule, and why every dispatch names its checks) and a *Vibe mode* section: what a director keeps and lacks, how skill actions map onto `vibe_*` and workers, and the worktree and request-budget limits
 - `skills/brainstorming/` — a defined small-change path: after the in-chat approval the session builds it itself on a branch: the full suite before changing anything, test first, the covering tests and the suite again, then one commit of only its own files and hunks, with no design document, plan or subagents (a new behavior such as a `--quiet` flag can be small; security, auth, concurrency, money, migrations, changes one revert cannot undo, new config files or stored formats, changes to existing behavior, new interfaces other code builds on and new dependencies never are, and none of them takes the quick-task route however complete the request); a request is a quick task only if doing it leaves no choice the person would see (a format, a default, wording, bad input) for the agent to make; each question asks one thing, with any reason before it; a playback rides along with the next question instead of waiting for its own answer; for software, the plan is written right after the builder check so the design and the plan get one approval. Of upstream v7.0.1's retune it keeps reading the project first, the new first message and the sharper questions; the approaches ride with the last playback chunk, whose one question is the pick, instead of going out in a message of their own; upstream's short design doc and plan for every small change are not taken

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@loneexile/omp-superpowers",
-  "version": "7.0.1-omp.3",
+  "version": "7.0.1-omp.4",
   "description": "obra/superpowers adapted for Oh My Pi (omp): a truthful task/todo tool mapping and five subagent-driven-development agents, each with its own model, thinking level, and tools.",
   "type": "module",
   "keywords": [