feinai 0.5.6 → 0.5.7

package/README.md

@@ -165,7 +165,7 @@ tasks   — atomic work units with blocked_by, quality_gates, worktree
 events  — append-only audit log: {parent_process}:{pid}:{user}
 ```
 
-Every mutation is logged. Every agent is identified. Override identity with `$FEINA_USER`.
+Every mutation is logged. Every agent is identified. Override identity with `$FEINAI_USER`.
 
 ---
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "feinai",
-  "version": "0.5.6",
+  "version": "0.5.7",
   "description": "Task & spec manager for AI agents — parallel worktrees, live dashboard, SDD skills",
   "type": "module",
   "bin": {

package/skills/feinai-sdd/SKILL.md

@@ -3,7 +3,7 @@ name: feinai-sdd
 description: Use when working in spec-driven development (SDD) workflows that involve brainstorming, writing-plans, or subagent-driven-development AND the project has a `.tasca/tasca.db` file. Replaces creating markdown files in `docs/superpowers/specs/` and `docs/superpowers/plans/` with atomic `feinai` CLI calls, keeping state queryable, race-free, and audit-logged. Also use when the user asks to create a spec, add a task, claim work, or mark progress, in a project that uses tasca.
 ---
 
-# Tasca SDD integration
+# feinai SDD integration
 
 `feinai` is a CLI + local SQLite database for managing specs, plans, and tasks in
 SDD workflows. When a project has `.tasca/tasca.db`, you should write to that
@@ -20,7 +20,7 @@ just change *where the artifacts get stored*.
 Invoke when **all** of the following are true:
 
 1. The project has a `.tasca/tasca.db` file (walk up the directory tree from
-   the current working directory; tasca uses the same discovery pattern as git).
+   the current working directory; feinai uses the same discovery pattern as git).
    Check with: `feinai status` (exit code 0 = tasca is set up).
 2. You are about to:
    - Write a spec via the `brainstorming` skill, OR
@@ -41,7 +41,7 @@ Before any spec / plan / task write, run:
 feinai status 2>/dev/null
 ```
 
-- Exit code 0: tasca is active in this project → use this skill.
+- Exit code 0: feinai is active in this project → use this skill.
 - Exit code 2: `No .tasca/tasca.db found` → fall back to vanilla superpowers
   (or ask the user `feinai init` if it seems intended).
 - Command not found: feinai is not installed or not on PATH. Tell the user:
@@ -96,7 +96,7 @@ FEINAI_EOF
 
 ### What replaces what
 
-| Superpowers step | tasca equivalent |
+| Superpowers step | feinai equivalent |
 |---|---|
 | `Write(docs/superpowers/specs/YYYY-MM-DD-X-design.md, ...)` | `feinai spec add SPEC-NNN "title" --stdin <<<` content |
 | Spec self-review (re-read the markdown) | `feinai spec content SPEC-NNN` (returns the markdown) |
@@ -169,7 +169,7 @@ single response, the full payload: `description` (workplan), `quality_gates`,
 `packages`, `blocked_by`. **The subagent never has to read the plan markdown.**
 
 This is the single biggest token saving and the strongest correctness
-guarantee from using tasca: each subagent's context contains exactly the task
+guarantee from using feinai: each subagent's context contains exactly the task
 it's executing, nothing else.
 
 ---
@@ -248,7 +248,7 @@ human-readable rationale; the tasks are the executable state.
 
 ### ❌ Don't create `docs/superpowers/specs/*.md` files
 
-If tasca is active, those files become a source of drift. The spec lives in
+If feinai is active, those files become a source of drift. The spec lives in
 the database. If you need to publish the spec elsewhere (PR description, wiki,
 etc.), export it on demand: `feinai spec content SPEC-X > /tmp/spec.md`.
 
@@ -262,9 +262,9 @@ subagents that both `show` then act will collide. Always `feinai take`.
 The CLI handles concurrency, audit logging, and validation. Direct SQL
 mutations bypass the events table and leave the audit log incomplete.
 
-### ✅ Do set `FEINA_USER` for explicit subagent identity
+### ✅ Do set `FEINAI_USER` for explicit subagent identity
 
-When dispatching a subagent, pass `FEINA_USER=subagent-N` in its environment
+When dispatching a subagent, pass `FEINAI_USER=subagent-N` in its environment
 so the audit log distinguishes which subagent did what. Otherwise the actor
 field will read `bun:<pid>:<user>` for everyone.
 
@@ -294,8 +294,8 @@ field will read `bun:<pid>:<user>` for everyone.
 
 This skill is **additive**. The superpowers skills (`brainstorming`,
 `writing-plans`, `subagent-driven-development`, etc.) still run; they still
-own the process. tasca only changes the storage of the artifacts they produce.
+own the process. feinai only changes the storage of the artifacts they produce.
 
-If you start brainstorming and discover the project has no tasca DB, fall back
+If you start brainstorming and discover the project has no feinai DB, fall back
 to the normal superpowers behavior (markdown files). Do not silently switch
 storage strategy mid-project.

package/src/cli.ts

@@ -48,7 +48,7 @@ import {
   type OutputFormat,
 } from "./format";
 
-const VERSION = "0.5.6";
+const VERSION = "0.5.7";
 
 interface ParsedArgs {
   positional: string[];
@@ -126,7 +126,7 @@ function detectFormat(args: ParsedArgs): OutputFormat {
  * Build a stable identifier for whoever is invoking feina.
  *
  * Priority:
- *   1. $FEINA_USER env var (explicit override — used by agents to identify themselves)
+ *   1. $FEINAI_USER env var (explicit override — used by agents to identify themselves)
  *   2. parent process name (on Linux via /proc/$PPID/comm) → "{parent_name}:{ppid}:{user}"
  *   3. fallback: "{user}@{hostname}"
  *
@@ -134,7 +134,7 @@ function detectFormat(args: ParsedArgs): OutputFormat {
  * from "bash:9999:m" in the events audit log without manual configuration.
  */
 function getCurrentUser(): string {
-  const override = process.env.FEINA_USER;
+  const override = process.env.FEINAI_USER;
   if (override) return override;
 
   const username = process.env.USER ?? userInfo().username ?? "unknown";
@@ -259,7 +259,7 @@ GLOBAL FLAGS:
   --version                         Show version
 
 ENV:
-  FEINA_USER                        Override owner/actor identity used in audit log
+  FEINAI_USER                        Override owner/actor identity used in audit log
 
 \x1b[34m\x1b[1m── Agent Integration ──────────────────────────────────────────────\x1b[0m
   \x1b[36mTeach your AI agents to use \x1b[1mfeina\x1b[0m\x1b[36m as their single source of truth for\x1b[0m