pi-soly 1.0.0 → 1.2.0

package/commands.ts

@@ -26,6 +26,7 @@ import {
 	formatAnalyticsFull,
 	formatTok,
 	readIfExists,
+	solyDirFor,
 	type RuleFile,
 	type SolyState,
 } from "./core.ts";
@@ -204,7 +205,7 @@ export function registerCommands(pi: ExtensionAPI, deps: CommandsDeps): void {
 			}
 			const cat = categories[choice];
 			if (!cat) return;
-			const dir = path.join(cwd, ".soly", "rules", cat.name);
+			const dir = path.join(solyDirFor(cwd), "rules", cat.name);
 			try {
 				fs.mkdirSync(dir, { recursive: true });
 			} catch {}
@@ -296,7 +297,7 @@ What must the LLM do?
 				const lastSeg = parsed.pathname.split("/").filter(Boolean).pop() ?? "rule.md";
 				const safeName = lastSeg.replace(/[^A-Za-z0-9._-]/g, "_");
 				const fileName = safeName.endsWith(".md") ? safeName : `${safeName}.md`;
-				const rulesRoot = path.join(process.cwd(), ".soly", "rules");
+				const rulesRoot = path.join(solyDirFor(process.cwd()), "rules");
 				fs.mkdirSync(rulesRoot, { recursive: true });
 				const targetFile = path.join(rulesRoot, fileName);
 				// Refuse to overwrite without warning

package/core.ts

@@ -1521,12 +1521,27 @@ export function buildStatusLine(
 // Soly dir helper
 // ============================================================================
 
-/** Default soly dir relative to cwd. */
-export const SOLY_DIRNAME = ".soly";
+/** Preferred soly dir name (vendor-neutral). */
+export const SOLY_DIRNAME = ".agents";
 
-/** Build the .soly dir path for a given cwd. */
+/** Legacy soly dir name. Kept for backward compat with existing projects. */
+export const LEGACY_SOLY_DIRNAME = ".soly";
+
+/** Which project subdir name is currently in use. Returns the first
+ *  one that exists, preferring `.agents/`. Falls back to `.soly/` if
+ *  no `.agents/` exists. If neither exists, returns `.agents/` (so
+ *  new writes go to the new location). */
 export function solyDirFor(cwd: string): string {
-  return path.join(cwd, SOLY_DIRNAME);
+	if (fs.existsSync(path.join(cwd, SOLY_DIRNAME))) return path.join(cwd, SOLY_DIRNAME);
+	if (fs.existsSync(path.join(cwd, LEGACY_SOLY_DIRNAME))) return path.join(cwd, LEGACY_SOLY_DIRNAME);
+	return path.join(cwd, SOLY_DIRNAME); // default to new for new projects
+}
+
+/** True if the legacy `.soly/` dir is in active use (and `.agents/` isn't). */
+export function isLegacySolyDir(cwd: string): boolean {
+	const newPath = path.join(cwd, SOLY_DIRNAME);
+	const oldPath = path.join(cwd, LEGACY_SOLY_DIRNAME);
+	return !fs.existsSync(newPath) && fs.existsSync(oldPath);
 }
 
 // ============================================================================

package/index.ts

@@ -38,6 +38,7 @@ import {
 	loadProjectState,
 	STATUS_ID,
 	solyDirFor,
+	isLegacySolyDir,
 	buildNextHint,
 	buildDriftReminder,
 	type RuleFile,
@@ -53,6 +54,7 @@ import {
 	type SolyConfig,
 } from "./config.ts";
 import { classifyTaskHeuristics, buildNudgeSection } from "./nudge.ts";
+import { notifyNudge, notifyDeprecation } from "./notification.ts";
 import { registerCommands, type CommandUI } from "./commands.ts";
 import { registerTools } from "./tools.ts";
 import { registerWorkflows } from "./workflows/index.ts";
@@ -350,6 +352,17 @@ export default function solyExtension(pi: ExtensionAPI) {
 	// ============================================================================
 
 	pi.on("session_start", async (event, ctx) => {
+		// Deprecation warning: if the project still uses `.soly/`, nudge the
+		// user toward `.agents/`. One-time per session.
+		if (isLegacySolyDir(ctx.cwd)) {
+			notifyDeprecation(
+				ctx.ui,
+				`.soly/ (legacy)`,
+				`.agents/ (vendor-neutral)`,
+				`Run \`mv .soly .agents\` to migrate. Both names work for now.`,
+			);
+		}
+
 		// Rules sources (priority order, higher wins on relPath collision).
 		// Project rules always beat global rules. .soly/rules.local/ is
 		// gitignored — for personal overrides on top of the project's rules.
@@ -663,11 +676,7 @@ export default function solyExtension(pi: ExtensionAPI) {
 		const angle =
 			heuristics.suggestedAngles[0] ?? "want me to confirm assumptions before I start?";
 
-		const label = heuristics.researchHeavy
-			? "soly: research-heavy prompt — clarifying question?"
-			: "soly: non-trivial prompt — clarifying question?";
-
-		ctx.ui.notify(`${label} ${angle}`, "info");
+		notifyNudge(ctx.ui, heuristics.researchHeavy ? "research" : "nonTrivial", angle);
 		nudgeActiveForTask = true;
 		lastNudgePromptKey = text.slice(0, 200);
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "pi-soly",
-  "version": "1.0.0",
+  "version": "1.2.0",
   "description": "Project management framework for pi-coding-agent. Workflows, planning, multi-question picker, agent switcher, live task list — one npm install, zero config.",
   "type": "module",
   "main": "index.ts",

package/skills/soly-framework/SKILL.md

@@ -81,11 +81,13 @@ The **soly** extension adds project-management workflow to [pi-coding-agent](htt
 │       └── data-scientist.md
 ```
 
-**Two parallel conventions:** `.soly/` is soly-specific state (phases, plans). `.agents/` is vendor-neutral agent config (works with any AI tool that follows the AGENTS.md standard). The two coexist:
+**Two parallel conventions (migration in progress):** `.soly/` is the legacy soly state. `.agents/` is the new vendor-neutral home. The two work side-by-side:
 
-- Use `.soly/` for soly workflow artifacts (PLAN.md, SUMMARY.md, etc.)
-- Use `.agents/` for things other AI tools should also see (rules, skills, agents)
-- Use `AGENTS.md` for top-level project-wide agent conventions
+- **Use `.agents/`** for new projects (recommended)
+- **Use `.soly/`** for legacy projects (still works, will show a deprecation warning)
+- **Use `AGENTS.md`** for top-level project-wide agent conventions
+
+To migrate: `mv .soly .agents` — soly picks up the new location automatically. No data loss.
 
 ## Frontmatter conventions