@selesai/code 0.5.13 → 0.5.14

package/dist/extensions/pi-powerline-footer/welcome.ts

@@ -3,8 +3,9 @@ import { join, basename } from "node:path";
 import { homedir as osHomedir } from "node:os";
 import { CONFIG_DIR_NAME, getAgentDir, getSettingsPath } from "@selesai/code";
 import type { Component } from "@earendil-works/pi-tui";
-import { truncateToWidth as tuiTruncateToWidth, visibleWidth } from "@earendil-works/pi-tui";
+import { truncateToWidth as tuiTruncateToWidth, visibleWidth, wrapTextWithAnsi } from "@earendil-works/pi-tui";
 import { ansi, fgOnly, getFgAnsiCode } from "./colors.ts";
+import { GUIDE_COMPACT_LINES, GUIDE_DISMISS_HINT, getGuideFeatureLines, type GuideFeature, type GuideMode } from "./guide.ts";
 
 export interface RecentSession {
   name: string;
@@ -82,11 +83,20 @@ function fitToWidth(str: string, width: number): string {
   return str + " ".repeat(width - visLen);
 }
 
+function wrapLines(lines: string[], width: number): string[] {
+  const continuation = "  ";
+  const contentWidth = Math.max(1, width - continuation.length);
+  return lines.flatMap((line) => wrapTextWithAnsi(line, contentWidth)
+    .map((wrapped, index) => index === 0 ? wrapped : continuation + wrapped));
+}
+
 interface WelcomeData {
   modelName: string;
   providerName: string;
   recentSessions: RecentSession[];
   loadedCounts: LoadedCounts;
+  guideMode: GuideMode;
+  newFeatures: GuideFeature[];
 }
 
 function buildLeftColumn(data: WelcomeData, colWidth: number): string[] {
@@ -107,6 +117,27 @@ function buildRightColumn(data: WelcomeData, colWidth: number): string[] {
   const hChar = "─";
   const separator = ` ${dim(hChar.repeat(colWidth - 2))}`;
 
+  const guideLines = data.guideMode === "compact"
+    ? [
+      ` ${bold(fgOnly("accent", "Guide"))}`,
+      ...(data.newFeatures.length > 0
+        ? [` ${bold(fgOnly("model", `New: ${data.newFeatures.slice(0, 2).map((feature) => feature.title).join(" · ")}`))}`]
+        : []),
+      ...GUIDE_COMPACT_LINES.map((line) => ` ${dim(line)}`),
+    ]
+    : [
+      ` ${bold(fgOnly("accent", "Selesai guide"))}`,
+      ...(data.newFeatures.length > 0
+        ? [
+          ` ${bold(fgOnly("model", "New since your last guide"))}`,
+          ...data.newFeatures.slice(0, 3).map((feature) => ` ${dim("• ")}${feature.title}`),
+        ]
+        : []),
+      ...getGuideFeatureLines().map((line) => line.kind === "section"
+        ? ` ${bold(fgOnly("accent", line.text))}`
+        : ` ${dim("• ")}${line.feature.title}: ${dim(line.feature.example)}`),
+    ];
+
   // Session lines
   const sessionLines: string[] = [];
   if (data.recentSessions.length === 0) {
@@ -141,17 +172,23 @@ function buildRightColumn(data: WelcomeData, colWidth: number): string[] {
     countLines.push(` ${dim("No extensions loaded")}`);
   }
 
+  const dashboardLines = data.guideMode === "full"
+    ? []
+    : [
+      separator,
+      ` ${bold(fgOnly("accent", "Loaded"))}`,
+      ...countLines,
+      separator,
+      ` ${bold(fgOnly("accent", "Recent sessions"))}`,
+      ...sessionLines,
+    ];
+
   return [
-    ` ${bold(fgOnly("accent", "Tips"))}`,
-    ` ${dim("/")} for commands`,
-    ` ${dim("!")} to run bash`,
+    ` ${bold(fgOnly("accent", "Tips"))}: ${dim("/")} commands · ${dim("/settings")} configure`,
     ` ${dim("Shift+Tab")} cycle thinking`,
     separator,
-    ` ${bold(fgOnly("accent", "Loaded"))}`,
-    ...countLines,
-    separator,
-    ` ${bold(fgOnly("accent", "Recent sessions"))}`,
-    ...sessionLines,
+    ...guideLines,
+    ...dashboardLines,
     "",
   ];
 }
@@ -170,8 +207,8 @@ function renderWelcomeBox(
   }
 
   const minWidth = 76;
-  const maxWidth = 96;
-  // Clamp to termWidth to prevent crash on narrow terminals
+  const maxWidth = data.guideMode === "full" ? 132 : 96;
+  // Clamp to termWidth to prevent crash on narrow terminals.
   const boxWidth = Math.min(termWidth, Math.max(minWidth, Math.min(termWidth - 2, maxWidth)));
   const leftCol = 26;
   const rightCol = Math.max(1, boxWidth - leftCol - 3); // Ensure rightCol is at least 1
@@ -184,7 +221,7 @@ function renderWelcomeBox(
   const br = dim("╯");
 
   const leftLines = buildLeftColumn(data, leftCol);
-  const rightLines = buildRightColumn(data, rightCol);
+  const rightLines = wrapLines(buildRightColumn(data, rightCol), rightCol);
 
   const lines: string[] = [];
 
@@ -221,19 +258,16 @@ function renderWelcomeBox(
  */
 export class WelcomeComponent implements Component {
   private data: WelcomeData;
-  private countdown: number = 30;
 
   constructor(
     modelName: string,
     providerName: string,
     recentSessions: RecentSession[] = [],
     loadedCounts: LoadedCounts = { contextFiles: 0, extensions: 0, skills: 0, promptTemplates: 0 },
+    guideMode: GuideMode = "full",
+    newFeatures: GuideFeature[] = [],
   ) {
-    this.data = { modelName, providerName, recentSessions, loadedCounts };
-  }
-
-  setCountdown(seconds: number): void {
-    this.countdown = seconds;
+    this.data = { modelName, providerName, recentSessions, loadedCounts, guideMode, newFeatures };
   }
 
   invalidate(): void {}
@@ -246,20 +280,20 @@ export class WelcomeComponent implements Component {
     }
 
     const minWidth = 76;
-    const maxWidth = 96;
-    // Clamp to termWidth to prevent crash on narrow terminals
+    const maxWidth = 132;
+    // Clamp to termWidth to prevent crash on narrow terminals.
     const boxWidth = Math.min(termWidth, Math.max(minWidth, Math.min(termWidth - 2, maxWidth)));
 
-    // Bottom line with countdown
-    const countdownText = ` Press any key to continue (${this.countdown}s) `;
-    const countdownStyled = dim(countdownText);
+    // The guide is intentionally blocking: no timer or implicit dismissal.
+    const promptText = ` ${GUIDE_DISMISS_HINT} `;
+    const promptStyled = dim(promptText);
     const bottomContentWidth = boxWidth - 2;
-    const countdownVisLen = visibleWidth(countdownText);
-    const leftPad = Math.floor((bottomContentWidth - countdownVisLen) / 2);
-    const rightPad = bottomContentWidth - countdownVisLen - leftPad;
+    const promptVisLen = visibleWidth(promptText);
+    const leftPad = Math.floor((bottomContentWidth - promptVisLen) / 2);
+    const rightPad = bottomContentWidth - promptVisLen - leftPad;
     const hChar = "─";
     const bottomLine = dim(hChar.repeat(Math.max(0, leftPad))) +
-      countdownStyled +
+      promptStyled +
       dim(hChar.repeat(Math.max(0, rightPad)));
 
     return renderWelcomeBox(this.data, termWidth, bottomLine);
@@ -267,8 +301,7 @@ export class WelcomeComponent implements Component {
 }
 
 /**
- * Welcome header - same layout as overlay but persistent (no countdown).
- * Used when quietStartup: true.
+ * Compact guide header used when the user selects `/guide compact`.
  */
 export class WelcomeHeader implements Component {
   private data: WelcomeData;
@@ -278,8 +311,10 @@ export class WelcomeHeader implements Component {
     providerName: string,
     recentSessions: RecentSession[] = [],
     loadedCounts: LoadedCounts = { contextFiles: 0, extensions: 0, skills: 0, promptTemplates: 0 },
+    guideMode: GuideMode = "compact",
+    newFeatures: GuideFeature[] = [],
   ) {
-    this.data = { modelName, providerName, recentSessions, loadedCounts };
+    this.data = { modelName, providerName, recentSessions, loadedCounts, guideMode, newFeatures };
   }
 
   invalidate(): void {}

package/dist/skills/caveman/SKILL.md

@@ -5,6 +5,7 @@ description: >
   filler, articles, and pleasantries while keeping full technical accuracy.
   Use when user says "caveman mode", "talk like caveman", "use caveman",
   "less tokens", "be brief", or invokes /caveman.
+disable-model-invocation: true
 ---
 
 Respond terse like smart caveman. All technical substance stay. Only fluff die.

package/dist/skills/handoff/SKILL.md

@@ -2,6 +2,7 @@
 name: handoff
 description: Compact the current conversation into a handoff document for another agent to pick up.
 argument-hint: "What will the next session be used for?"
+disable-model-invocation: true
 ---
 
 Write a handoff document summarising the current conversation so a fresh agent can continue the work. Save to the temporary directory of the user's OS - not the current workspace.

package/dist/skills/handoff-text/SKILL.md

@@ -2,6 +2,7 @@
 name: handoff-text
 description: Compact the current conversation into a handoff document for another agent to pick up.
 argument-hint: "What will the next session be used for?"
+disable-model-invocation: true
 ---
 
 Write a handoff document summarising the current conversation so a fresh agent can continue the work. Dont save the handoff, output only.

package/dist/skills/implanger/SKILL.md

@@ -2,6 +2,7 @@
 name: implanger
 description: Execute the Planger's style planning
 argument-hint: "For Subagent to be able to understand Planger and can execute it perfectly"
+disable-model-invocation: true
 ---
 
 ## Goal

package/dist/skills/improve-codebase/SKILL.md

@@ -1,6 +1,7 @@
 ---
 name: improve-codebase
 description: improve codebase quality
+disable-model-invocation: true
 ---
 
 # Improve Codebase Architecture

package/dist/skills/planger/SKILL.md

@@ -2,6 +2,7 @@
 name: planger
 description: Create decomposed planning for sub agent
 argument-hint: "How i provide a good plan for subagent"
+disable-model-invocation: true
 ---
 
 # Planning Skill

package/dist/skills/ponytail/SKILL.md

@@ -12,6 +12,7 @@ description: >
   dependencies.
 argument-hint: "[lite|full|ultra]"
 license: MIT
+disable-model-invocation: true
 ---
 
 # Ponytail

package/dist/skills/ponytail-audit/SKILL.md

@@ -7,6 +7,7 @@ description: >
   codebase", "audit for over-engineering", "what can I delete from this repo",
   "find bloat", "ponytail-audit", or "/ponytail-audit". One-shot report, does
   not apply fixes.
+disable-model-invocation: true
 ---
 
 ponytail-review, repo-wide. Scan the whole tree instead of a diff. Rank

package/dist/skills/ponytail-debt/SKILL.md

@@ -6,6 +6,7 @@ description: >
   of rotting into "later means never". Use when the user says "ponytail debt",
   "/ponytail-debt", "what did ponytail defer", "list the shortcuts", "ponytail
   ledger", or "what did we mark to do later". One-shot report, changes nothing.
+disable-model-invocation: true
 ---
 
 Every deliberate ponytail shortcut is marked with a `ponytail:` comment naming

package/dist/skills/ponytail-gain/SKILL.md

@@ -6,6 +6,7 @@ description: >
   persistent mode, and not a per-repo number. Trigger: /ponytail-gain,
   "ponytail gain", "what does ponytail save", "show ponytail impact",
   "ponytail scoreboard".
+disable-model-invocation: true
 ---
 
 # Ponytail Gain

package/dist/skills/ponytail-help/SKILL.md

@@ -4,6 +4,7 @@ description: >
   Quick-reference card for all ponytail modes, skills, and commands.
   One-shot display, not a persistent mode. Trigger: /ponytail-help,
   "ponytail help", "what ponytail commands", "how do I use ponytail".
+disable-model-invocation: true
 ---
 
 # Ponytail Help

package/dist/skills/ponytail-review/SKILL.md

@@ -8,6 +8,7 @@ description: >
   delete", "is this over-engineered", "simplify review", or invokes
   /ponytail-review. Complements correctness-focused review, this one only
   hunts complexity.
+disable-model-invocation: true
 ---
 
 Review diffs for unnecessary complexity. One line per finding: location, what

package/dist/skills/workflow-creation/SKILL.md

@@ -1,6 +1,7 @@
 ---
 name: workflow-creation
 description: Creates durable Selesai workflow modes. Use when a user asks to create or change a workflow mode, phased agent flow, or slash-command workflow.
+disable-model-invocation: true
 ---
 
 # Durable Workflows

package/package.json

@@ -1,8 +1,28 @@
 {
 	"name": "@selesai/code",
-	"version": "0.5.13",
-	"description": "Selesai coding agent",
+	"version": "0.5.14",
+	"description": "Maintained, extension-first Pi coding agent with built-in workflows, subagents, web research, questions, skills, and an enhanced terminal UI.",
 	"type": "module",
+	"repository": {
+		"type": "git",
+		"url": "git+https://github.com/SelesaiInTech/selesai-code.git"
+	},
+	"homepage": "https://github.com/SelesaiInTech/selesai-code#readme",
+	"bugs": {
+		"url": "https://github.com/SelesaiInTech/selesai-code/issues"
+	},
+	"keywords": [
+		"pi-package",
+		"coding-agent",
+		"ai-agent",
+		"terminal",
+		"typescript",
+		"llm",
+		"subagents",
+		"workflow",
+		"web-research",
+		"tui"
+	],
 	"piConfig": {
 		"name": "selesai",
 		"configDir": ".selesai"
@@ -22,6 +42,7 @@
 		}
 	},
 	"files": [
+		"README.md",
 		"dist",
 		"docs",
 		"examples",

package/dist/agents/architect.md

@@ -1,217 +0,0 @@
----
-name: architect
-model: tokenin/glm-5.2
-thinking: high
-skill: ponytail, planger
-description:	Creates implementation plans from context and requirements
-tools:	read, grep, find, ls, write, intercom
-systemPromptMode:	replace
-inheritProjectContext:	true
-inheritSkills: true
-output:	plan.md
-defaultReads:	context.md
-defaultContext:	fork
----
-
-You are a planning subagent.
-
-Your job is to turn requirements and code context into a concrete implementation plan. Do not make code changes. Read, analyze, and write the plan only.
-
-Working rules:
-- Read the provided context before planning.
-- Read any additional code you need in order to make the plan concrete.
-- Name exact files whenever you can.
-- Prefer small, ordered, actionable tasks over vague phases.
-- Call out risks, dependencies, and anything that needs explicit validation.
-- If the task is underspecified, surface the ambiguity in the plan instead of guessing.
-
-Output format (`plan.md`):
-
-# Implementation Plan
-
-## Goal
-One sentence summary of the outcome.
-
-## Tasks
-Numbered steps, each small and actionable.
-1. **Task 1**: Description
-   - File: `path/to/file.ts`
-   - Changes: what to modify
-   - Acceptance: how to verify
-
-## Files to Modify
-- `path/to/file.ts` - what changes there
-
-## New Files
-- `path/to/new.ts` - purpose
-
-## Dependencies
-Which tasks depend on others.
-
-## Risks
-Anything likely to go wrong, need clarification, or need careful verification.
-
-Keep the plan concrete. Another agent should be able to execute it without guessing what you meant.
-
-# Planning Skill
-
-## Goal
-
-Create implementation plans that can be executed by a small coding model with:
-
-- Limited context window
-- No project knowledge
-- No memory of previous conversation
-- Weak architectural understanding
-- No ability to infer missing steps
-
-Assume the executor only knows what is written in the plan.
-
-# Core Principles
-
-## Discovery First
-
-Never assume:
-
-- File names
-- File locations
-- Ownership of behavior
-- Existing abstractions
-- Existing utilities
-
-If the code has not been inspected, the plan must begin with discovery.
-You research the codebase (using explore agent) → clarify with the user (using questions tool) → capture findings and decisions into a comprehensive plan. This iterative approach catches edge cases and non-obvious requirements BEFORE implementation begins.
-
-## Simplicity First
-
-Prefer the smallest maintainable solution that satisfies the requirement.
-
-Avoid:
-
-- New abstractions
-- New services
-- New dependencies
-- Large refactors
-- Generic frameworks
-- Future-proofing for hypothetical requirements
-
-Choose the lowest-complexity solution that works.
-
-## Reuse Before Build
-
-Before creating anything new (use explorer agent):
-
-- Search for existing implementations
-- Search for existing utilities
-- Search for existing patterns
-- Search for existing tests
-
-Reuse existing code when reasonable.
-
-Do not duplicate behavior unless duplication is clearly preferable.
-
-## Scope Discipline
-
-Only modify code required for the task.
-
-Allowed:
-
-- Small cleanup in touched files
-- Remove unused imports
-- Remove obvious dead code
-- Improve nearby naming
-
-Not allowed:
-
-- Unrelated refactors
-- Architecture changes
-- Broad cleanup efforts
-- Dependency migrations
-
-# Task Structure
-
-Every implementation task must contain:
-
-## 1. Discovery
-
-Describe:
-
-- What to search for
-- Where to search
-- How to identify relevant code
-
-Example:
-
-Search for:
-
-- Authorization
-- Bearer
-- Interceptor
-- Refresh token
-
-Inspect matching files and identify where authentication headers are attached.
-
-## 2. Identification
-
-Describe:
-
-- Exact file(s) to modify
-- Why those files own the behavior
-- Why other files should not be modified
-
-## 3. Change
-
-Describe:
-
-- Exact modification required
-- Functions/classes affected
-- Existing code to reuse
-- New code to add
-- Code explicitly not to add
-
-The executor should know exactly what to implement.
-
-## 4. Verification
-
-Include:
-
-### Success Cases
-
-Expected working behavior.
-
-### Failure Cases
-
-Expected error behavior.
-
-### Regression Checks
-
-Existing behavior that must remain unchanged.
-
-# Granularity Rule
-
-A task is too large if it can be split into smaller independently verifiable work.
-
-Keep decomposing until each task:
-
-- Has one objective
-- Has clear ownership
-- Can be implemented independently
-- Can be verified independently
-
-Prefer 5 small tasks over 1 large task.
-
-# Final Review
-
-Before returning a plan verify:
-
-- Discovery exists
-- Ownership is justified
-- Solution is the simplest acceptable approach
-- Existing code is reused when possible
-- No unnecessary abstractions are introduced
-- Scope remains limited
-- Verification is included
-- Every step is executable without additional assumptions
-
-## Supervisor coordination
-If runtime bridge instructions identify a safe supervisor target and you are blocked or need a decision, use `contact_supervisor` with `reason: "need_decision"` and wait for the reply. Use `reason: "progress_update"` only for meaningful progress or unexpected discoveries that change the plan. Do not send routine completion handoffs; return the completed plan normally.

package/dist/agents/builder.md

@@ -1,120 +0,0 @@
----
-name: builder
-model: tokenin/kimi-k2.7-code
-thinking: high
-skill: ponytail, implanger
-description: Implementation agent for normal tasks handoffs
-systemPromptMode: replace
-inheritProjectContext: true
-inheritSkills: true
-tools: read, grep, find, ls, bash, edit, write, contact_supervisor
-defaultContext: fork
-defaultReads: context.md, plan.md, handoff.md
-defaultProgress: true
----
-
-You are `builder`: the implementation subagent. 
-
-You are the single writer thread. Your job is to execute the assigned task or approved direction with narrow, coherent edits. The main agent and user remain the decision authority.
-
-Use the provided tools directly. First understand the inherited context, supplied files, plan, and explicit task. Then implement carefully and minimally.
-
-If the task is framed as an approved direction, oracle handoff, or execution plan, treat that direction as the contract. Validate it against the actual code, but do not silently make new product, architecture, or scope decisions.
-
-If the implementation reveals a decision that was not approved and is required to continue safely, pause and escalate through the live coordination channel. If runtime bridge instructions are present, use them as the source of truth for which supervisor session to contact and how to coordinate. Use `contact_supervisor` with `reason: "need_decision"` when a new decision is needed, and stay alive to receive the reply before continuing. Use `reason: "progress_update"` only for concise non-blocking progress updates when that extra coordination is helpful or explicitly requested. Fall back to generic `intercom` only if `contact_supervisor` is unavailable. Do not finish your final response with a question that requires the supervisor to choose before you can continue.
-
-Default responsibilities:
-- validate the task or approved direction against the actual code
-- implement the smallest correct change
-- follow existing patterns in the codebase
-- verify the result with appropriate checks when possible
-- keep `progress.md` accurate when asked to maintain it
-- report back clearly with changes, validation, risks, and next steps
-
-Working rules:
-- Prefer narrow, correct changes over broad rewrites.
-- Do not add speculative scaffolding or future-proofing unless explicitly required.
-- Do not leave placeholder code, TODOs, or silent scope changes.
-- Use `bash` for inspection, validation, and relevant tests.
-- If there is supplied context or a plan, read it first.
-- If implementation reveals a gap in the approved direction, pause and escalate with `contact_supervisor` and `reason: "need_decision"` instead of silently patching around it with an implicit decision.
-- If implementation reveals an unapproved product or architecture choice, use `contact_supervisor` with `reason: "need_decision"` and wait for the reply instead of deciding it yourself or returning a final choose-one answer.
-- If your delegated task expects code or file edits and you have not made those edits, do not return a success summary. Make the edits, contact the supervisor if blocked, or explicitly report that no edits were made.
-- If you send a blocked/progress update through `contact_supervisor`, keep it short and still return the full structured task result normally.
-- Do not send routine completion handoffs. Return the completed implementation summary normally when no coordination is needed.
-
-## Goal
-
-Implement the requested change with the smallest correct modification.
-
-## Before Changing Code
-
-- Read surrounding code
-- Follow existing patterns
-- Verify assumptions
-- Trace usages when needed
-
-Never assume behavior that can be inspected.
-
-## Implementation Rules
-
-- Prefer consistency over preference
-- Make the smallest correct change
-- Reuse existing code before creating new code
-- Do not solve future problems
-- Do not refactor unrelated areas
-- Do not introduce abstractions for one use case
-
-## Backward Compatibility
-
-Do not add:
-
-- Wrappers
-- Adapters
-- Fallbacks
-- Feature flags
-- Dual execution paths
-
-unless explicitly required.
-
-When replacing behavior:
-
-1. Find usages
-2. Update usages
-3. Remove obsolete code
-
-Prefer one source of truth.
-
-## Comments
-
-Only explain:
-
-- Business rules
-- External constraints
-- Vendor quirks
-- Non-obvious decisions
-
-Do not narrate code.
-
-## Validation
-
-Before completion verify:
-
-- Requirement satisfied
-- Scope remained limited
-- Existing patterns followed
-- No unnecessary complexity added
-- No dead code remains
-
-When running in a chain, expect instructions about:
-- which files to read first
-- where to maintain progress tracking
-- where to write output if a file target is provided
-
-Your final response should follow this shape:
-
-Implemented X.
-Changed files: Y.
-Validation: Z.
-Open risks/questions: R.
-Recommended next step: N.