insta 0.0.26 → 0.0.27

package/README.md

@@ -79,8 +79,8 @@ plane's address, not the CLI's loopback address.
 ### Services are branch-scoped
 
 A project holds services (`postgres`, `storage`, `compute`) and each branch owns its own
-set. `insta branch create feature-x` forks the parent's services: a Neon branch per
-Postgres, a copy-on-write bucket per storage, a clone of every compute service. From there
+set. `insta branch create feature-x` forks the parent's services: a copy-on-write database
+branch per Postgres, a copy-on-write bucket per storage, a clone of every compute service. From there
 the two branches diverge independently. A project is capped at 10 branches.
 
 ### Credentials come from the secret seam, not a file you maintain
@@ -207,8 +207,9 @@ build never reaches a production installer.
 The `insta` skill and its task guides live in
 [InsForge/insta-skills](https://github.com/InsForge/insta-skills). `insta setup agent`
 installs it user-globally for every coding agent on the machine. `insta project create` and
-`insta project link` additionally install the stack skills (Neon Postgres, Tigris, Better
-Auth) into the project, along with the `insta observe` credential-audit hook.
+`insta project link` additionally install the stack skills (Tigris, Better Auth) into the
+project, along with the `insta observe` credential-audit hook. Postgres needs no stack
+skill — it's plain Postgres, reached directly via `DATABASE_URL`.
 
 ## Contributing
 

package/dist/commands/setup.js

@@ -3,7 +3,7 @@
 // every agent the skills tool knows: the skill is pure product knowledge with brand-gated
 // triggers — no project state in it (the project binding is carried by ./.insta/project.json
 // at command time), so one machine-level copy is strictly better than per-project copies.
-// Stack skills (neon/tigris/better-auth) intentionally stay per-project: their presence in a
+// Stack skills (tigris/better-auth) intentionally stay per-project: their presence in a
 // project doubles as its stack manifest — that install happens on `project create|link`.
 import { spawn } from 'node:child_process';
 import os from 'node:os';

package/dist/ensure-skills.js

@@ -1,6 +1,7 @@
 // Install the related agent skills into a linked project so the developer's coding agent has
-// context for what InstaCloud provisions — the `insta` CLI itself plus the three services you build
-// directly against (Neon Postgres, Tigris storage, Better Auth). Runs `npx skills add`
+// context for what InstaCloud provisions — the `insta` CLI itself plus the services you build
+// directly against (Tigris storage, Better Auth). Postgres gets no vendor skill: instadb is
+// plain Postgres, and agents talk to it directly via DATABASE_URL. Runs `npx skills add`
 // (vercel-labs/skills) fully non-interactively. Best-effort: a failure (offline, npx missing, a
 // repo moved) prints a manual fallback and never blocks or fails the host command — same contract
 // as the observe-hook install.
@@ -13,8 +14,8 @@ import { DEFAULT_ENV, ENVS } from './env.js';
 // Codex → .agents/skills/ (.github/skills/ is the third well-known dir). These are regenerable
 // agent context, not the developer's source — keep them out of git.
 const SKILL_DIRS = ['.claude/skills/', '.agents/skills/', '.github/skills/'];
-// `skills` prints a full-screen ASCII banner at the top of every `add`, so our 4 invocations
-// would stack 4 banners. It skips the banner when it detects an agent driving it rather than a
+// `skills` prints a full-screen ASCII banner at the top of every `add`, so our 3 invocations
+// would stack 3 banners. It skips the banner when it detects an agent driving it rather than a
 // human — AI_AGENT is its first-checked signal (any non-empty value ⇒ agent mode). Setting it is
 // honest here (this IS programmatic, not an interactive prompt) and, because we already pin the
 // agents/skills/-y, has no effect on the install beyond quieting the banner. Preserve a caller's
@@ -32,10 +33,9 @@ const defaultRunner = (cmd, args, inherit = false) => new Promise((resolve) => {
 const AGENT_FLAGS = ['-a', 'claude-code', '-a', 'codex', '-y', '--copy'];
 // `instaSpec` is the insta skill source for the resolved environment (`owner/repo[@ref]`), so a
 // project created against staging gets the staging skill text. The third-party stack skills are
-// environment-independent — they document Neon/Tigris/Better Auth, not our control plane.
+// environment-independent — they document Tigris/Better Auth, not our control plane.
 const skillTargets = (instaSpec) => [
     { label: 'insta', args: ['skills', 'add', instaSpec, '-s', 'insta', ...AGENT_FLAGS] },
-    { label: 'neon-postgres', args: ['skills', 'add', 'neondatabase/agent-skills', '-s', 'neon-postgres', ...AGENT_FLAGS] },
     { label: 'tigris', args: ['skills', 'add', 'tigrisdata/skills',
             '-s', 'tigris-object-operations', '-s', 'file-storage', '-s', 'tigris-sdk-guide',
             '-s', 'tigris-security-access-control', '-s', 'tigris-image-optimization',
@@ -63,7 +63,7 @@ export async function installSkills(deps) {
             targets = skillTargets(skills);
         }
         catch { /* keep production defaults */ }
-        print('  installing related agent skills (insta, neon-postgres, tigris, better-auth) …');
+        print('  installing related agent skills (insta, tigris, better-auth) …');
         for (const s of targets) {
             // Don't stream: the `skills` tool's clack UI (clone spinner, banners) is noise. Run it
             // silent (stdio 'ignore') and let the per-skill ✓/failed line below be the clean output —

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "insta",
-  "version": "0.0.26",
+  "version": "0.0.27",
   "type": "module",
   "description": "InstaCloud CLI — a thin client of the platform control-plane API.",
   "keywords": [