Use fixed .tmp suffix for writeSettings temp file

The mutex already serializes all writes, so the PID-based temp name
is unnecessary. A fixed suffix matches writeStore and avoids orphaned
temp files after a crash (a restarted process picks a new PID).

Co-Authored-By: Paperclip <noreply@paperclip.ing>

.agents/skills/company-creator/SKILL.md

@@ -154,14 +154,6 @@ Each AGENTS.md body should include not just what the agent does, but how they fi
 
 This turns a collection of agents into an organization that actually works together. Without workflow context, agents operate in isolation — they do their job but don't know what happens before or after them.
 
-Add a concise execution contract to every generated working agent:
-
-- Start actionable work in the same heartbeat and do not stop at a plan unless planning was requested.
-- Leave durable progress in comments, documents, or work products with the next action.
-- Use child issues for long or parallel delegated work instead of polling agents, sessions, or processes.
-- Mark blocked work with the unblock owner and action.
-- Respect budget, pause/cancel, approval gates, and company boundaries.
-
 ### Step 5: Confirm Output Location
 
 Ask the user where to write the package. Common options:

.agents/skills/company-creator/references/example-company.md

@@ -105,13 +105,6 @@ Your responsibilities:
 - Implement features and fix bugs
 - Write tests and documentation
 - Participate in code reviews
-
-Execution contract:
-
-- Start actionable implementation work in the same heartbeat; do not stop at a plan unless planning was requested.
-- Leave durable progress with a clear next action.
-- Use child issues for long or parallel delegated work instead of polling agents, sessions, or processes.
-- Mark blocked work with the unblock owner and action.
 ```
 
 ## teams/engineering/TEAM.md

.agents/skills/create-agent-adapter/SKILL.md

@@ -548,7 +548,7 @@ Import from `@paperclipai/adapter-utils/server-utils`:
 ### Prompt Templates
 - Support `promptTemplate` for every run
 - Use `renderTemplate()` with the standard variable set
-- Default prompt should use `DEFAULT_PAPERCLIP_AGENT_PROMPT_TEMPLATE` from `@paperclipai/adapter-utils/server-utils` so local adapters share Paperclip's execution contract: act in the same heartbeat, avoid planning-only exits unless requested, leave durable progress and a next action, use child issues instead of polling, mark blockers with owner/action, and respect governance boundaries.
+- Default prompt: `"You are agent {{agent.id}} ({{agent.name}}). Continue your Paperclip work."`
 
 ### Error Handling
 - Differentiate timeout vs process error vs parse failure

.agents/skills/deal-with-security-advisory/SKILL.md

@@ -1,230 +0,0 @@
----
-name: deal-with-security-advisory
-description: >
-  Handle a GitHub Security Advisory response for Paperclip, including
-  confidential fix development in a temporary private fork, human coordination
-  on advisory-thread comments, CVE request, synchronized advisory publication,
-  and immediate security release steps.
----
-
-# Security Vulnerability Response Instructions
-
-## ⚠️ CRITICAL: This is a security vulnerability. Everything about this process is confidential until the advisory is published. Do not mention the vulnerability details in any public commit message, PR title, branch name, or comment. Do not push anything to a public branch. Do not discuss specifics in any public channel. Assume anything on the public repo is visible to attackers who will exploit the window between disclosure and user upgrades.
-
-***
-
-## Context
-
-A security vulnerability has been reported via GitHub Security Advisory:
-
-* **Advisory:** {{ghsaId}} (e.g. GHSA-x8hx-rhr2-9rf7)
-* **Reporter:** {{reporterHandle}}
-* **Severity:** {{severity}}
-* **Notes:** {{notes}}
-
-***
-
-## Step 0: Fetch the Advisory Details
-
-Pull the full advisory so you understand the vulnerability before doing anything else:
-
-```
-gh api repos/paperclipai/paperclip/security-advisories/{{ghsaId}}
-
-```
-
-Read the `description`, `severity`, `cvss`, and `vulnerabilities` fields. Understand the attack vector before writing code.
-
-## Step 1: Acknowledge the Report
-
-⚠️ **This step requires a human.** The advisory thread does not have a comment API. Ask the human operator to post a comment on the private advisory thread acknowledging the report. Provide them this template:
-
-> Thanks for the report, @{{reporterHandle}}. We've confirmed the issue and are working on a fix. We're targeting a patch release within {{timeframe}}. We'll keep you updated here.
-
-Give your human this template, but still continue
-
-Below we use `gh` tools - you do have access and credentials outside of your sandbox, so use them.
-
-## Step 2: Create the Temporary Private Fork
-
-This is where all fix development happens. Never push to the public repo.
-
-```
-gh api --method POST \
-  repos/paperclipai/paperclip/security-advisories/{{ghsaId}}/forks
-
-```
-
-This returns a repository object for the private fork. Save the `full_name` and `clone_url`.
-
-Clone it and set up your workspace:
-
-```
-# Clone the private fork somewhere outside ~/paperclip
-git clone <clone_url_from_response> ~/security-patch-{{ghsaId}}
-cd ~/security-patch-{{ghsaId}}
-git checkout -b security-fix
-
-```
-
-**Do not edit `~/paperclip`** — the dev server is running off the `~/paperclip` master branch and we don't want to touch it. All work happens in the private fork clone.
-
-**TIPS:**
-
-* Do not commit `pnpm-lock.yaml` — the repo has actions to manage this
-* Do not use descriptive branch names that leak the vulnerability (e.g., no `fix-dns-rebinding-rce`). Use something generic like `security-fix`
-* All work stays in the private fork until publication
-* CI/GitHub Actions will NOT run on the temporary private fork — this is a GitHub limitation by design. You must run tests locally
-
-## Step 3: Develop and Validate the Fix
-
-Write the patch. Same content standards as any PR:
-
-* It must functionally work — **run tests locally** since CI won't run on the private fork
-* Consider the whole codebase, not just the narrow vulnerability path. A patch that fixes one vector but opens another is worse than no patch
-* Ensure backwards compatibility for the database, or be explicit about what breaks
-* Make sure any UI components still look correct if the fix touches them
-* The fix should be minimal and focused — don't bundle unrelated changes into a security patch. Reviewers (and the reporter) should be able to read the diff and understand exactly what changed and why
-
-**Specific to security fixes:**
-
-* Verify the fix actually closes the attack vector described in the advisory. Reproduce the vulnerability first (using the reporter's description), then confirm the patch prevents it
-* Consider adjacent attack vectors — if DNS rebinding is the issue, are there other endpoints or modes with the same class of problem?
-* Do not introduce new dependencies unless absolutely necessary — new deps in a security patch raise eyebrows
-
-Push your fix to the private fork:
-
-```
-git add -A
-git commit -m "Fix security vulnerability"
-git push origin security-fix
-
-```
-
-## Step 4: Coordinate with the Reporter
-
-⚠️ **This step requires a human.** Ask the human operator to post on the advisory thread letting the reporter know the fix is ready and giving them a chance to review. Provide them this template:
-
-> @{{reporterHandle}} — fix is ready in the private fork if you'd like to review before we publish. Planning to release within {{timeframe}}.
-
-Proceed
-
-## Step 5: Request a CVE
-
-This makes vulnerability scanners (npm audit, Snyk, Dependabot) warn users to upgrade. Without it, nobody gets automated notification.
-
-```
-gh api --method POST \
-  repos/paperclipai/paperclip/security-advisories/{{ghsaId}}/cve
-
-```
-
-GitHub is a CVE Numbering Authority and will assign one automatically. The CVE may take a few hours to propagate after the advisory is published.
-
-## Step 6: Publish Everything Simultaneously
-
-This all happens at once — do not stagger these steps. The goal is **zero window** between the vulnerability becoming public knowledge and the fix being available.
-
-### 6a. Verify reporter credit before publishing
-
-```
-gh api repos/paperclipai/paperclip/security-advisories/{{ghsaId}} --jq '.credits'
-
-```
-
-If the reporter is not credited, add them:
-
-```
-gh api --method PATCH \
-  repos/paperclipai/paperclip/security-advisories/{{ghsaId}} \
-  --input - << 'EOF'
-{
-  "credits": [
-    {
-      "login": "{{reporterHandle}}",
-      "type": "reporter"
-    }
-  ]
-}
-EOF
-
-```
-
-### 6b. Update the advisory with the patched version and publish
-
-```
-gh api --method PATCH \
-  repos/paperclipai/paperclip/security-advisories/{{ghsaId}} \
-  --input - << 'EOF'
-{
-  "state": "published",
-  "vulnerabilities": [
-    {
-      "package": {
-        "ecosystem": "npm",
-        "name": "paperclip"
-      },
-      "vulnerable_version_range": "< {{patchedVersion}}",
-      "patched_versions": "{{patchedVersion}}"
-    }
-  ]
-}
-EOF
-
-```
-
-Publishing the advisory simultaneously:
-
-* Makes the GHSA public
-* Merges the temporary private fork into your repo
-* Triggers the CVE assignment (if requested in step 5)
-
-### 6c. Cut a release immediately after merge
-
-```
-cd ~/paperclip
-git pull origin master
-
-gh release create v{{patchedVersion}} \
-  --repo paperclipai/paperclip \
-  --title "v{{patchedVersion}} — Security Release" \
-  --notes "## Security Release
-
-This release fixes a critical security vulnerability.
-
-### What was fixed
-{{briefDescription}} (e.g., Remote code execution via DNS rebinding in \`local_trusted\` mode)
-
-### Advisory
-https://github.com/paperclipai/paperclip/security/advisories/{{ghsaId}}
-
-### Credit
-Thanks to @{{reporterHandle}} for responsibly disclosing this vulnerability.
-
-### Action required
-All users running versions prior to {{patchedVersion}} should upgrade immediately."
-
-```
-
-## Step 7: Post-Publication Verification
-
-```
-# Verify the advisory is published and CVE is assigned
-gh api repos/paperclipai/paperclip/security-advisories/{{ghsaId}} \
-  --jq '{state: .state, cve_id: .cve_id, published_at: .published_at}'
-
-# Verify the release exists
-gh release view v{{patchedVersion}} --repo paperclipai/paperclip
-
-```
-
-If the CVE hasn't been assigned yet, that's normal — it can take a few hours.
-
-⚠️ **Human step:** Ask the human operator to post a final comment on the advisory thread confirming publication and thanking the reporter.
-
-Tell the human operator what you did by posting a comment to this task, including:
-
-* The published advisory URL: `https://github.com/paperclipai/paperclip/security/advisories/{{ghsaId}}`
-* The release URL
-* Whether the CVE has been assigned yet
-* All URLs to any pull requests or branches

.agents/skills/release-changelog-discord-message/SKILL.md

@@ -1,406 +0,0 @@
----
-name: release-changelog-discord-message
-description: >
-  Write the Discord release announcement for a stable Paperclip release. Companion
-  to `release-changelog` — that skill produces the file at `releases/vYYYY.MDD.P.md`;
-  this one turns that file into a single copy-pasteable Discord post in dotta's
-  voice and attaches it as the `discord_announcement` document on the release
-  issue.
----
-
-# Release Discord Announcement Skill
-
-Write the Discord release announcement for the **stable** Paperclip release.
-
-This is the companion to `.agents/skills/release-changelog/SKILL.md`. That skill
-generates the file at `releases/vYYYY.MDD.P.md`. This skill turns that file into
-a single copy-pasteable Discord block, in dotta's voice, and posts it as the
-`discord_announcement` document on the release issue.
-
-## What dotta said
-
-> This is for discord — try to follow my format. If I have a section where I
-> think about the future, pull from recent issues we're working on etc.
-
-The Discord announcement is **not** the changelog. The changelog is exhaustive;
-the announcement is opinionated, in-voice, and built around the same handful of
-shipped highlights plus a real "what's next" + "what's on my mind" pulled from
-current Paperclip work — not invented.
-
-## When to use
-
-- After `release-changelog` has produced `releases/vYYYY.MDD.P.md` on the
-  release worktree/PR.
-- When the release issue (the one assigned by the release routine) asks for a
-  Discord announcement, or has a `discord_announcement` document that needs to
-  be refreshed for a new date/version.
-- Never run this in isolation. The version, date, contributor list, and
-  highlight set MUST match the matching changelog file — if the changelog has
-  been updated, refresh this too.
-
-## Output
-
-A single fenced markdown code block, ready to paste into Discord. Attached as
-issue document key `discord_announcement` on the release issue, and pasted
-verbatim into a comment on that issue so the human can copy it out.
-
-```bash
-PUT /api/issues/{releaseIssueId}/documents/discord_announcement
-{
-  "title": "Discord announcement",
-  "format": "markdown",
-  "body": "<the announcement>",
-  "baseRevisionId": "<latest if updating>"
-}
-```
-
-If the document already exists, fetch it first and pass the current
-`baseRevisionId`. Never overwrite silently — if the version has changed since
-the document was last written, mention what changed in the issue comment.
-
-## Format (follow this template)
-
-Use Discord emoji shortcodes (`:paperclip:`, `:lock:`, `:brain:` …) — NOT the
-Unicode emoji. Discord renders the shortcodes; the changelog file uses prose.
-
-```
-:paperclip: :paperclip: :paperclip: CLIPPERS!!! v{VERSION} IS OUT :paperclip: :paperclip: :paperclip:
-
-OFFICIAL TWITTER: https://x.com/papercliping - follow it, report any others
-
-## Highlights
-
-:emoji: **Feature Name** - one-sentence description in dotta's voice.
-:emoji: **Feature Name** - …
-:emoji: **Feature Name** - …
-
-... and a long tail of {flavor of the rest}. Read the [full release notes](<github link>).
-
-## WHATS NEXT (:motorway:  Roadmap)
-
-* **Theme A** - one-line forward-looking blurb
-* **Theme B** - …
-* **Theme C** - …
-
-## What's on my mind
-
-* **Topic** - what's bugging dotta / what's queued / open questions
-* **Topic** - …
-
-## PRESS                              (optional — only if there is real press)
-
-* **Outlet / Person** - what happened ([link](<x.com link>))
-
-## WHAT I NEED FROM YOU               (optional — only if there's a real ask)
-
-FOLLOW THE TWITTER: https://x.com/papercliping - that's the only official one
-TELL ME if you're using Paperclip in your business - I want to meet you
-
-## Community
-
-Thank you to everyone who contributed to this release!
-
-```
-@username1, @username2, @username3
-```
-
-## In Summary
-
-PAPERCLIP IS THE AI ORCHESTRATOR FOR HUMANS TO ACCOMPLISH 100x MORE WORK
-
-Every single person will be managing a team of a dozen, or a hundred, or a
-thousand agents and Paperclip will be the default tool to manage it all.
-
-ITS TIME TO CLIP :paperclip: :paperclip: :paperclip:
-
-FULL RELEASE NOTES
-
-https://github.com/paperclipai/paperclip/blob/master/releases/v{VERSION}.md
-
-||@everyone||
-```
-
-Notes on the template:
-
-- The opening and closing `:paperclip: :paperclip: :paperclip:` bookends are
-  part of the brand — keep them.
-- Sections may be UPPERCASE or Title Case — dotta has used both. Pick a style
-  and stay consistent within a single post.
-- Use `||@everyone||` (Discord spoiler-wrapped) at the very end so it pings
-  exactly once when the spoiler is removed by the poster.
-
-## Language tips
-
-These are extracted from how dotta has written the last several announcements.
-Mimic this register; do not invent a "professional" tone.
-
-- **First person, conversational.** "I want to meet companies using Paperclip",
-  "what's on my mind", "if that's you let me know". Not "Paperclip is excited
-  to announce".
-- **ALL CAPS for excitement and asks**, especially in the opener, the section
-  headers, the "WHAT I NEED FROM YOU" section, and the closing tagline. Do not
-  ALL-CAPS feature descriptions.
-- **One emoji shortcode per highlight bullet**, picked to evoke the feature
-  (`:lock:` for secrets, `:brain:` for planning, `:mag:` for search,
-  `:cloud:` for cloud / sandbox, `:jigsaw:` for plugins, `:rewind:` for
-  history/restore, `:thread:` for threads, etc.).
-- **Highlight bullets are one sentence**, opinionated, told from the user's
-  perspective — "the cloud-secrets prereq is real now", not "added support
-  for…".
-- **Tail line after highlights** wraps the rest in a single sentence and links
-  to the full release notes ("… and a long tail of {flavor}. Read the [full
-  release notes](url).").
-- **"WHATS NEXT" is forward-looking themes**, not a literal sprint list. 3–5
-  bullets is the right size. Pull these from active goals, in-flight projects,
-  and recent issues the team is working on — do not invent themes.
-- **"What's on my mind"** is dotta's personal/strategic thinking — docs gaps,
-  philosophical positioning ("we're the human control plane for ai labor"),
-  invitations ("if you've ever wanted to write about how you use Paperclip,
-  hit me up"). Pull real tensions from recent issues/comments; do not invent.
-- **Press section** is optional. Only include it if there is real press in the
-  release window (a tweet, a podcast, a talk, a star milestone). No press →
-  drop the section entirely.
-- **"WHAT I NEED FROM YOU"** is optional. Use it for a single concrete ask
-  (follow the twitter, intros, beta sign-ups). No real ask → drop it.
-- **Community** is the same contributors list that's in the changelog file,
-  fenced in a triple-backtick block, comma-separated `@username, @username`.
-  Exclude bots and Paperclip founders, same rules as the changelog skill.
-- **The "In Summary" mission line** evolves slowly. Use the most recent
-  variant unless dotta tells you otherwise. Recent variants:
-  - "PAPERCLIP IS THE AI ORCHESTRATOR FOR HUMANS TO ACCOMPLISH 100x MORE WORK"
-  - "PAPERCLIP WILL BE THE DEFAULT AGENT-MANAGEMENT TOOL FOR EVERY COMPANY"
-  - "Paperclip will be _the_ control plane for AI agents in **every** company."
-- **Closing tagline** is always `ITS TIME TO CLIP :paperclip: :paperclip:
-  :paperclip:`. Keep it.
-
-## Workflow
-
-1. Read the matching `releases/vYYYY.MDD.P.md` produced by `release-changelog`.
-   Use the version and contributor list from that file — never re-derive them.
-2. Read the **release issue thread** (the one assigned to you that ran the
-   release routine) — comments + linked issues + recent issues in the company
-   are the source for `WHATS NEXT` and `What's on my mind`. Pull real themes,
-   not invented ones.
-3. Re-read the three verbatim examples below — they're the canonical voice.
-4. Draft the announcement using the template above.
-5. PUT it as the `discord_announcement` document on the release issue (see
-   "Output" above). If updating, send the latest `baseRevisionId`.
-6. Post a comment on the release issue that includes the announcement inside a
-   single fenced markdown code block, so dotta can copy-paste it into Discord
-   without opening the document.
-
-Do not publish to Discord. This skill only prepares the artifact.
-
-## Verbatim previous examples
-
-Three previous Discord announcements from dotta, included **verbatim** as the
-ground-truth examples for voice, structure, and emoji usage. When in doubt,
-match these.
-
-### Example 1 — v2026.403.0
-
-```
-CLIPPERS! v2026.403.0 has dropped!! :paperclip: :paperclip: :paperclip:
-
-## Highlights
-
-:inbox_tray:  **Inbox overhaul** - there is a new "mine" tab that has mail-client like keyboard shortcuts. It's my new default view for managing work
-:thumbsup:  **Feedback and evals** - you can now vote :thumbsup: / :thumbsdown: on your agent's responses. If you choose to share your traces with me, I'll use it to make Paperclip better. In either case you can export locally for your own org's learning
-:page_with_curl:  **Document revisions** - you can now restore old versions of your documents
-:ping_pong:  **Telemetry** - this version has anonymized telemetry that helps me better understand the basic uses of Paperclip (adapters and so on) - if you hate that, just it disable with `DO_NOT_TRACK=1` or `PAPERCLIP_TELEMETRY_DISABLED=1` environment variables
-:construction_worker: **Execution Workspaces (experimental)** - Paperclip is not a "code review" tool, but I have been finding worktrees are important for certain projects. Enable it in experimental settings
-:loop:  **Routine variables** - sometimes you need to customize a routine and the new variables feature makes that easy
-
-PLUS **tons** of improvements aound adapters, bugfixes, qol
-
-## COMMUNITY
-
-HUGE THANKS to the contributors with commits in this release:
-
-```
-@aronprins, @bittoby, @edimuj, @HenkDz, @kevmok, @mvanhorn, @radiusred, @remdev, @statxc, @vanductai
-```
-
-## WHATS NEXT (ROADMAP)
-
-* **Multi-human users** -- you've been asking for it, we have a draft and will have this shortly
-* **Sandbox execution** - the other half of cloud deployment: run your agents in a sandbox across any provider
-
-PLUS: just dealing with the excellent PRs we have sitting in our inbox.
-
-**What's also on my mind (coming soonish)**
-
-* MAXIMIZER MODE - for when you've got a dream and tokens to burn
-* Artifacts, work products, and deployments
-* CEO Chat
-* Stronger agent defaults
-
-## PRESS
-
-I've been doing my part to spread the word about Paperclip
-
-* We talked to the incredible [Andrew Warner of Mixergy Fame](https://x.com/dotta/status/2039087507514507407)
-* We gave a tutorial with the [inimitable Greg Isenberg](https://x.com/dotta/status/2037279902445994345)
-* We met with the [Seed Club guys](https://x.com/dotta/status/2039020365926576377)
-* We crossed [40k stars (46k now!)](https://x.com/dotta/status/2038638188227387613)
-* ... and a couple others that will be released in a few days
-
-## SUCCESS STORIES
-
-* [Nevo made $76k in march](https://x.com/dotta/status/2039406772859920758) after using Paperclip to automate his marketing
-* [Lewis Jackson](https://x.com/WhatSayLew/status/2039810227394978158) said 34 agents were already operating his trading firm through Paperclip and called it his "holy s***" AI moment.
-* [Neal Kotak](https://x.com/nkotak1/status/2039582439459209638) said Paperclip already runs most of Roominary for him and praised how strong the product is.
-* [Sam Woods](https://x.com/samwoods/status/2039039305960587755) said he knows several people who moved from OpenClaw to Paperclip, often with Hermes in the stack, and that they love it.
-* [Josh Galt](https://x.com/JoshGalt/status/2039386307219095557) called Paperclip the coolest agent tooling he has used and said it is finally something that just works.
-
-## IN SUMMARY
-
-I know there are still some rough edges, but
-
-Paperclip will be *the* control plane for AI agents in **every** company.
-
-and I think we're moving at a pretty good clip :paperclip: :paperclip: :paperclip:
-
-FULL RELEASE NOTES HERE
-
-https://github.com/paperclipai/paperclip/releases/tag/v2026.403.0
-
-||@everyone||
-```
-
-### Example 2 — v2026.416.0
-
-```
-:paperclip: :paperclip: :paperclip: CLIPPERS!!! v2026.416.0 IS OUT :paperclip: :paperclip: :paperclip:
-
-## Highlights
-
-This release has *tons* of quality of life improvements around speed, performance, and workflow. You should notice that comment threads feel faster and your agents stay on task longer
-
-:thread: Issue chat threads now are a conversation more than comments
-:police_officer: Execution policies like **Reviewer** and **Approver** are now first-class in the harness (e.g. enforce that QA *must* review a task)
-:no_smoking: Blocker dependencies - first-class "wake on blocker resolved" which means now you can have "task graphs" that depend on one another and it's enforced by Paperclip
-:woman_feeding_baby: Parent-child tasks - better support for sub-tasks all around, which makes it much easier to organize your work
-
-And then a million fixes around ux, details, keyboard shortcuts, bug fixes, security fixes, etc. Really you should read the [full release notes here](https://github.com/paperclipai/paperclip/releases/tag/v2026.416.0)
-
-## COMMUNITY
-
-INCREDIBLE INCREDIBLE WORK BY folks with commits and reports in this release:
-
-```
-@AllenHyang, @antonio-mello-ai, @aronprins, @chrisschwer, @cleanunicorn, @DanielSousa, @davison, @ergonaworks, @HearthCore, @HenkDz, @KhairulA, @kimnamu, @Lempkey, @marysomething99-prog, @mvanhorn, @officialasishkumar, @plind-dm, @shoaib050326, @sparkeros, @wbelt, @offset, @sagilayani, @mattdonnelly10, @peaktwilight, @YuvalElbar6
-```
-
-## WHATS NEXT (:motorway:  Roadmap)
-
-* **Multi-human users** - in the last stages of testing, Paperclip is better with teams
-* **Memory Infrastructure** - your agents will remember everything about yoru business
-* **Sandbox execution** - run your agents anywhere
-
-## What's on my mind
-
-* I want to meet with companies who are using Paperclip in their business - if that's you let me know
-* We need more Paperclip tutorials, defaults, and education - thanks to @aronprins for his work in this area already!
-* We still need to get better at reviewing your PRs and we're improving our process every day
-* "Zero-human company" language has to go - we're the human control plane for ai labor
-* We're adding better support for *knowledge (wikis & files)*, *artifacts*, and *work product* in Paperclip soon.
-
-## PRESS
-
-* **AI Engineer Europe Tutorial** - I gave a tutorial for AIE. If someone is looking for a basics ABC of Paperclip [you can send them this](https://x.com/dotta/status/2044575580264316931)
-* **AI Club Chicago** - JB gave a talk on Paperclip [at AI Tinkerers in Chicago](https://x.com/developwithJB/status/2044281068778316268) !
-
-## IN SUMMARY
-
-PAPERCLIP WILL BE THE DEFAULT AGENT-MANAGEMENT TOOL FOR EVERY COMPANY
-
-If there's anything I can do to help you and your company use Paperclip, hit me up. Until then, enjoy the new release
-
-ITS TIME TO CLIP :paperclip: :paperclip: :paperclip:
-
-FULL RELEASE NOTES
-
-https://github.com/paperclipai/paperclip/releases/tag/v2026.416.0
-
-||@everyone||
-```
-
-### Example 3 — v2026.427.0
-
-```
-:paperclip: :paperclip: :paperclip: CLIPPERS!!! v2026.427.0 IS OUT :paperclip: :paperclip: :paperclip:
-
-THIS IS THE OFFICIAL TWITTER FOLLOW IT: https://x.com/papercliping
-
-## Highlights
-
-:man_feeding_baby: **MULTI USER** - you can now invite multiple users to your instance
-:factory_worker:  **HARDER WORKING** - robosut liveness continuations and lifecycle recovery means your instance tries harder before involving you
-:white_check_mark:  **SUBISSUE CHECKLISTS** - subissues have better ordering which allows for long-run planning
-:thread: **Rich Thread UX** - now your agents can ask you questions, ask for approvals, suggest tasks and you can approve or refine them right in your task threads
-:cloud:  **BETA: Sandbox Providers** - Cloud sandboxing is in beta - the API ships in this release and we'll be adding more providers
-... and *tons* of other improvements and bugfixes.
-
-## Community
-
-Thank you to everyone who contributed to this release!
-
-```
-@akhater, @aronprins, @GodsBoy, @LeonSGP43, @neerazz, @NoronhaH, @rbarinov, @rvanduiven, @SgtPooki, @superbiche
-```
-
-## WHATS NEXT (:motorway:  Roadmap)
-
-* **Longer-range planning and execution** - Paperclip will support longer and longer tasks and work until it's done
-* **Secrets Service v2** - an important prereq for Paperclip cloud
-* **Artifacts, memory, and knowledge**
-* **Conference Room** aka CEO/Agent Chat
-
-## What's on my mind
-
-* **Documentation & Blog posts** - I've fallen behind on the docs but aron has done a good job here - we'll be setting up Clips to help maintain these
-* **Paperclip Cloud** - will be a critical unlock for us, but even the shared team story needs developed more - *where should the work be done* and *where are the outputs stored* and *how do we surface them to users*? Each of these questions are a core Paperclip service that needs developed
-* **Paperclip Bench** - In the vein of SWE-Bench I've started an internal benchmark for Paperclip - we have to be able to measure that our changes are improving the system and not regressing
-* **Paperclip Connections Store** - connecting to Github, Slack, Google Docs, and the hundreds of other services we use every day should be easy, secure, and configurable per agent and team
-
-## Press
-
-I met with the [Wisemen about Paperclip](https://x.com/dotta/status/2045146539534827998)
-
-## WHAT I NEED FROM YOU
-
-FOLLOW THIS TWITTER ACCOUNT: https://x.com/papercliping - that's the only official one, report any others
-
-## In Summary
-
-PAPERCLIP IS THE AI ORCHESTRATOR FOR HUMANS TO ACCOMPLISH 100x MORE WORK
-
-Every single person will be managing a team of a dozen, or a hundred, or a thousand agents and Paperclip will be the default tool to manage it all.
-
-ITS TIME TO CLIP :paperclip: :paperclip: :paperclip:
-
-FULL RELEASE NOTES
-
-https://github.com/paperclipai/paperclip/blob/master/releases/v2026.427.0.md
-
-||@everyone||
-```
-
-## Review checklist
-
-Before handing off:
-
-1. Version + date match the matching `releases/vYYYY.MDD.P.md` exactly.
-2. Contributor list matches the changelog (same exclusions: bots, founders).
-3. Highlights are a subset of the changelog Highlights — same shipped features,
-   not invented or pre-alpha work.
-4. `WHATS NEXT` and `What's on my mind` are pulled from real recent issues /
-   active goals — not invented themes.
-5. Section style (UPPERCASE vs Title Case) is internally consistent.
-6. Closing tagline is `ITS TIME TO CLIP :paperclip: :paperclip: :paperclip:`
-   and `||@everyone||` is the very last line.
-7. Document `discord_announcement` is updated on the release issue, and the
-   announcement is also posted in a comment inside a fenced code block.
-
-This skill never posts to Discord. It only prepares the announcement artifact.

.agents/skills/release-changelog/SKILL.md

@@ -177,12 +177,8 @@ real name or email). To find GitHub usernames:
 
 **Never expose contributor email addresses.** Use `@username` only.
 
-Exclude bot accounts (e.g. `lockfile-bot`, `dependabot`) from the list.
-Exclude Paperclip founders from the list (e.g. `cryppadotta`, `forgottendev`, `devinfoley`, `sockmonster`, `scotttong`)
-
-List contributors in alphabetical order by GitHub username (case-insensitive).
-
-If there are no contributors left after exclusions, then just skip this section and don't mention it.
+Exclude bot accounts (e.g. `lockfile-bot`, `dependabot`) from the list. List contributors
+in alphabetical order by GitHub username (case-insensitive).
 
 ## Step 6 — Review Before Release
 

.env.example

@@ -2,6 +2,3 @@ DATABASE_URL=postgres://paperclip:paperclip@localhost:5432/paperclip
 PORT=3100
 SERVE_UI=false
 BETTER_AUTH_SECRET=paperclip-dev-secret
-
-# Discord webhook for daily merge digest (scripts/discord-daily-digest.sh)
-# DISCORD_WEBHOOK_URL=https://discord.com/api/webhooks/...

.github/PULL_REQUEST_TEMPLATE.md

@@ -38,8 +38,6 @@
 
 -
 
-> For core feature work, check [`ROADMAP.md`](ROADMAP.md) first and discuss it in `#dev` before opening the PR. Feature PRs that overlap with planned core work may need to be redirected — check the roadmap first. See `CONTRIBUTING.md`.
-
 ## Model Used
 
 <!--
@@ -59,7 +57,6 @@
 
 - [ ] I have included a thinking path that traces from project context to this change
 - [ ] I have specified the model used (with version and capability details)
-- [ ] I have checked ROADMAP.md and confirmed this PR does not duplicate planned core work
 - [ ] I have run tests locally and they pass
 - [ ] I have added or updated tests where applicable
 - [ ] If this change affects the UI, I have included before/after screenshots

.github/workflows/build.yml

@@ -1,55 +1,53 @@
-name: Docker
+name: Build & Push
 
 on:
   push:
-    branches:
-      - "master"
-    tags:
-      - "v*"
+    branches: [master]
+  workflow_dispatch:
 
 permissions:
   contents: read
   packages: write
 
 jobs:
-  build-and-push:
-    runs-on: ubuntu-latest
-    timeout-minutes: 60
-    concurrency:
-      group: docker-${{ github.ref }}
-      cancel-in-progress: true
+  build:
+    runs-on: runners-farhoodliquor
+    timeout-minutes: 30
     steps:
       - name: Checkout
         uses: actions/checkout@v4
 
-      - name: Login to GitHub Container Registry
+      - name: Login to Docker Hub
         uses: docker/login-action@v3
         with:
-          registry: ghcr.io
-          username: ${{ github.repository_owner }}
-          password: ${{ secrets.GITHUB_TOKEN }}
+          username: ${{ secrets.DOCKERHUB_USERNAME }}
+          password: ${{ secrets.DOCKERHUB_TOKEN }}
 
       - name: Set up Docker Buildx
         uses: docker/setup-buildx-action@v3
 
+      - name: Login to GHCR
+        uses: docker/login-action@v3
+        with:
+          registry: ghcr.io
+          username: ${{ github.actor }}
+          password: ${{ secrets.GITHUB_TOKEN }}
+
       - name: Docker meta
         id: meta
         uses: docker/metadata-action@v5
         with:
-          images: ghcr.io/${{ github.repository }}
+          images: ghcr.io/farhoodliquor/paperclip
           tags: |
-            type=raw,value=latest,enable={{is_default_branch}}
+            type=raw,value=latest
+            type=sha,prefix=
             type=semver,pattern={{version}}
-            type=semver,pattern={{major}}.{{minor}}
-            type=sha
 
       - name: Build and push
         uses: docker/build-push-action@v6
         with:
           context: .
-          platforms: linux/amd64,linux/arm64
           push: true
-          cache-from: type=gha
-          cache-to: type=gha,mode=max
           tags: ${{ steps.meta.outputs.tags }}
           labels: ${{ steps.meta.outputs.labels }}
+          no-cache: true

.github/workflows/e2e.yml

@@ -29,11 +29,9 @@ jobs:
 
       - run: pnpm install --frozen-lockfile
       - run: pnpm build
-      - run: google-chrome --version
+      - run: npx playwright install --with-deps chromium
 
       - name: Run e2e tests
-        env:
-          PAPERCLIP_PLAYWRIGHT_CHANNEL: "chrome"
         run: pnpm run test:e2e
 
       - uses: actions/upload-artifact@v4

.github/workflows/pr.yml

@@ -23,9 +23,7 @@ jobs:
       - name: Block manual lockfile edits
         if: github.head_ref != 'chore/refresh-lockfile'
         run: |
-          # Diff the PR branch against its merge base so recent base-branch commits
-          # do not masquerade as changes made by the PR itself.
-          changed="$(git diff --name-only "${{ github.event.pull_request.base.sha }}...${{ github.event.pull_request.head.sha }}")"
+          changed="$(git diff --name-only "${{ github.event.pull_request.base.sha }}" "${{ github.event.pull_request.head.sha }}")"
           if printf '%s\n' "$changed" | grep -qx 'pnpm-lock.yaml'; then
             echo "Do not commit pnpm-lock.yaml in pull requests. CI owns lockfile updates."
             exit 1
@@ -43,119 +41,54 @@ jobs:
           node-version: 24
 
       - name: Validate Dockerfile deps stage
-        run: node ./scripts/check-docker-deps-stage.mjs
-
-      - name: Reject git push in adapter/runtime code
-        run: node ./scripts/check-no-git-push.mjs
-
-      - name: Test no-git-push check
-        run: node --test ./scripts/check-no-git-push.test.mjs
-
-      - name: Validate release package manifest
-        run: node ./scripts/release-package-map.mjs check
-
-      - name: Verify release package bootstrap for changed manifests
         run: |
-          mapfile -t changed_paths < <(git diff --name-only "${{ github.event.pull_request.base.sha }}...${{ github.event.pull_request.head.sha }}")
-          PAPERCLIP_RELEASE_BOOTSTRAP_BASE_SHA="${{ github.event.pull_request.base.sha }}" \
-            node ./scripts/check-release-package-bootstrap.mjs "${changed_paths[@]}"
+          missing=0
+
+          # Extract only the deps stage from the Dockerfile
+          deps_stage="$(awk '/^FROM .* AS deps$/{found=1; next} found && /^FROM /{exit} found{print}' Dockerfile)"
+
+          if [ -z "$deps_stage" ]; then
+            echo "::error::Could not extract deps stage from Dockerfile (expected 'FROM ... AS deps')"
+            exit 1
+          fi
+
+          # Derive workspace search roots from pnpm-workspace.yaml (exclude dev-only packages)
+          search_roots="$(grep '^ *- ' pnpm-workspace.yaml | sed 's/^ *- //' | sed 's/\*$//' | grep -v 'examples' | grep -v 'create-paperclip-plugin' | tr '\n' ' ')"
+
+          if [ -z "$search_roots" ]; then
+            echo "::error::Could not derive workspace roots from pnpm-workspace.yaml"
+            exit 1
+          fi
+
+          # Check all workspace package.json files are copied in the deps stage
+          for pkg in $(find $search_roots -maxdepth 2 -name package.json -not -path '*/examples/*' -not -path '*/create-paperclip-plugin/*' -not -path '*/node_modules/*' 2>/dev/null | sort -u); do
+            dir="$(dirname "$pkg")"
+            if ! echo "$deps_stage" | grep -q "^COPY ${dir}/package.json"; then
+              echo "::error::Dockerfile deps stage missing: COPY ${pkg} ${dir}/"
+              missing=1
+            fi
+          done
+
+          # Check patches directory is copied if it exists
+          if [ -d patches ] && ! echo "$deps_stage" | grep -q '^COPY patches/'; then
+            echo "::error::Dockerfile deps stage missing: COPY patches/ patches/"
+            missing=1
+          fi
+
+          if [ "$missing" -eq 1 ]; then
+            echo "Dockerfile deps stage is out of sync. Update it to include the missing files."
+            exit 1
+          fi
 
       - name: Validate dependency resolution when manifests change
         run: |
-          changed="$(git diff --name-only "${{ github.event.pull_request.base.sha }}...${{ github.event.pull_request.head.sha }}")"
+          changed="$(git diff --name-only "${{ github.event.pull_request.base.sha }}" "${{ github.event.pull_request.head.sha }}")"
           manifest_pattern='(^|/)package\.json$|^pnpm-workspace\.yaml$|^\.npmrc$|^pnpmfile\.(cjs|js|mjs)$'
           if printf '%s\n' "$changed" | grep -Eq "$manifest_pattern"; then
             pnpm install --lockfile-only --ignore-scripts --no-frozen-lockfile
           fi
 
-  typecheck_release_registry:
-    name: Typecheck + Release Registry
-    needs: [policy]
-    runs-on: ubuntu-latest
-    timeout-minutes: 20
-
-    steps:
-      - name: Checkout repository
-        uses: actions/checkout@v4
-
-      - name: Setup pnpm
-        uses: pnpm/action-setup@v4
-        with:
-          version: 9.15.4
-
-      - name: Setup Node.js
-        uses: actions/setup-node@v4
-        with:
-          node-version: 24
-          cache: pnpm
-
-      - name: Install dependencies
-        run: pnpm install --frozen-lockfile
-
-      - name: Typecheck workspaces whose build scripts skip TypeScript
-        run: pnpm run typecheck:build-gaps
-
-      - name: Verify release registry test coverage
-        run: pnpm run test:release-registry
-
-  general_tests:
-    name: General tests (${{ matrix.group_label }})
-    needs: [policy]
-    runs-on: ubuntu-latest
-    timeout-minutes: 20
-    strategy:
-      fail-fast: false
-      matrix:
-        include:
-          - group: general-server
-            group_label: server
-          - group: general-workspaces-a
-            group_label: workspaces-a
-          - group: general-workspaces-b
-            group_label: workspaces-b
-
-    steps:
-      - name: Checkout repository
-        uses: actions/checkout@v4
-
-      - name: Setup pnpm
-        uses: pnpm/action-setup@v4
-        with:
-          version: 9.15.4
-
-      - name: Setup Node.js
-        uses: actions/setup-node@v4
-        with:
-          node-version: 24
-          cache: pnpm
-
-      - name: Install dependencies
-        run: pnpm install --frozen-lockfile
-
-      - name: Run grouped general test suites
-        run: pnpm test:run:general -- --group '${{ matrix.group }}'
-
   verify:
-    # Preserve the legacy required-check name while the underlying work runs in parallel.
-    name: verify
-    if: ${{ always() }}
-    needs: [typecheck_release_registry, general_tests, build]
-    runs-on: ubuntu-latest
-    timeout-minutes: 5
-
-    steps:
-      - name: Fail if any split verify lane failed
-        env:
-          TYPECHECK_RELEASE_REGISTRY_RESULT: ${{ needs.typecheck_release_registry.result }}
-          GENERAL_TESTS_RESULT: ${{ needs.general_tests.result }}
-          BUILD_RESULT: ${{ needs.build.result }}
-        run: |
-          test "$TYPECHECK_RELEASE_REGISTRY_RESULT" = "success"
-          test "$GENERAL_TESTS_RESULT" = "success"
-          test "$BUILD_RESULT" = "success"
-
-  build:
-    name: Build
     needs: [policy]
     runs-on: ubuntu-latest
     timeout-minutes: 20
@@ -178,79 +111,16 @@ jobs:
       - name: Install dependencies
         run: pnpm install --frozen-lockfile
 
+      - name: Typecheck
+        run: pnpm -r typecheck
+
+      - name: Run tests
+        run: pnpm test:run
+
       - name: Build
         run: pnpm build
 
-  verify_serialized_server:
-    name: Verify serialized server suites (${{ matrix.shard_label }})
-    needs: [policy]
-    runs-on: ubuntu-latest
-    timeout-minutes: 20
-    strategy:
-      fail-fast: false
-      matrix:
-        include:
-          - shard_index: 0
-            shard_count: 4
-            shard_label: 1/4
-          - shard_index: 1
-            shard_count: 4
-            shard_label: 2/4
-          - shard_index: 2
-            shard_count: 4
-            shard_label: 3/4
-          - shard_index: 3
-            shard_count: 4
-            shard_label: 4/4
-
-    steps:
-      - name: Checkout repository
-        uses: actions/checkout@v4
-
-      - name: Setup pnpm
-        uses: pnpm/action-setup@v4
-        with:
-          version: 9.15.4
-
-      - name: Setup Node.js
-        uses: actions/setup-node@v4
-        with:
-          node-version: 24
-          cache: pnpm
-
-      - name: Install dependencies
-        run: pnpm install --frozen-lockfile
-
-      - name: Run serialized server test shard
-        run: pnpm test:run:serialized -- --shard-index ${{ matrix.shard_index }} --shard-count ${{ matrix.shard_count }}
-
-  canary_dry_run:
-    name: Canary Dry Run
-    needs: [policy]
-    runs-on: ubuntu-latest
-    timeout-minutes: 20
-
-    steps:
-      - name: Checkout repository
-        uses: actions/checkout@v4
-
-      - name: Setup pnpm
-        uses: pnpm/action-setup@v4
-        with:
-          version: 9.15.4
-
-      - name: Setup Node.js
-        uses: actions/setup-node@v4
-        with:
-          node-version: 24
-          cache: pnpm
-
-      - name: Install dependencies
-        run: pnpm install --frozen-lockfile
-
-      # `release.sh` always executes its Step 2/7 workspace build, even when
-      # `--skip-verify` bypasses the initial verification gate.
-      - name: Release canary dry run via release.sh internal build
+      - name: Release canary dry run
         run: |
           git checkout -B master HEAD
           git checkout -- pnpm-lock.yaml
@@ -279,11 +149,11 @@ jobs:
       - name: Install dependencies
         run: pnpm install --frozen-lockfile
 
-      - name: Verify runner Chrome
-        # GitHub's Ubuntu runner image already ships Google Chrome, so use that
-        # directly for the headless e2e lane instead of downloading Playwright
-        # browser bundles inside the 30 minute job budget.
-        run: google-chrome --version
+      - name: Build
+        run: pnpm build
+
+      - name: Install Playwright
+        run: npx playwright install --with-deps chromium
 
       - name: Generate Paperclip config
         run: |
@@ -303,7 +173,6 @@ jobs:
       - name: Run e2e tests
         env:
           PAPERCLIP_E2E_SKIP_LLM: "true"
-          PAPERCLIP_PLAYWRIGHT_CHANNEL: "chrome"
         run: pnpm run test:e2e
 
       - name: Upload Playwright report

.github/workflows/release-smoke.yml

@@ -58,10 +58,8 @@ jobs:
       - name: Install dependencies
         run: pnpm install --no-frozen-lockfile
 
-      - name: Verify runner Chrome
-        # Release smoke also runs headless on GitHub's Ubuntu image, so use the
-        # runner's preinstalled Chrome instead of a Playwright browser download.
-        run: google-chrome --version
+      - name: Install Playwright browser
+        run: npx playwright install --with-deps chromium
 
       - name: Launch Docker smoke harness
         run: |
@@ -91,7 +89,6 @@ jobs:
           PAPERCLIP_RELEASE_SMOKE_BASE_URL: ${{ env.SMOKE_BASE_URL }}
           PAPERCLIP_RELEASE_SMOKE_EMAIL: ${{ env.SMOKE_ADMIN_EMAIL }}
           PAPERCLIP_RELEASE_SMOKE_PASSWORD: ${{ env.SMOKE_ADMIN_PASSWORD }}
-          PAPERCLIP_PLAYWRIGHT_CHANNEL: "chrome"
         run: pnpm run test:release-smoke
 
       - name: Capture Docker logs

.github/workflows/release.yml

@@ -1,273 +0,0 @@
-name: Release
-
-on:
-  push:
-    branches:
-      - master
-  workflow_dispatch:
-    inputs:
-      source_ref:
-        description: Commit SHA, branch, or tag to publish as stable
-        required: true
-        type: string
-        default: master
-      stable_date:
-        description: Enter a UTC date in YYYY-MM-DD format, for example 2026-03-18. Do not enter a version string. The workflow will resolve that date to a stable version such as 2026.318.0, then 2026.318.1 for the next same-day stable.
-        required: false
-        type: string
-      dry_run:
-        description: Preview the stable release without publishing
-        required: true
-        type: boolean
-        default: false
-
-concurrency:
-  group: release-${{ github.event_name }}-${{ github.ref }}
-  cancel-in-progress: false
-
-jobs:
-  verify_canary:
-    if: github.event_name == 'push'
-    runs-on: ubuntu-latest
-    timeout-minutes: 30
-    permissions:
-      contents: read
-
-    steps:
-      - name: Checkout repository
-        uses: actions/checkout@v4
-        with:
-          fetch-depth: 0
-
-      - name: Setup pnpm
-        uses: pnpm/action-setup@v4
-        with:
-          version: 9.15.4
-
-      - name: Setup Node.js
-        uses: actions/setup-node@v4
-        with:
-          node-version: 24
-          cache: pnpm
-
-      - name: Validate release package manifest
-        run: node ./scripts/release-package-map.mjs check
-
-      - name: Install dependencies
-        run: pnpm install --no-frozen-lockfile
-
-      - name: Typecheck
-        run: pnpm -r typecheck
-
-      - name: Run tests
-        run: pnpm test:run
-
-      - name: Build
-        run: pnpm build
-
-  publish_canary:
-    if: github.event_name == 'push'
-    needs: verify_canary
-    runs-on: ubuntu-latest
-    timeout-minutes: 45
-    environment: npm-canary
-    permissions:
-      contents: write
-      id-token: write
-
-    steps:
-      - name: Checkout repository
-        uses: actions/checkout@v4
-        with:
-          fetch-depth: 0
-
-      - name: Setup pnpm
-        uses: pnpm/action-setup@v4
-        with:
-          version: 9.15.4
-
-      - name: Setup Node.js
-        uses: actions/setup-node@v4
-        with:
-          node-version: 24
-          cache: pnpm
-
-      - name: Validate release package manifest
-        run: node ./scripts/release-package-map.mjs check
-
-      - name: Install dependencies
-        run: pnpm install --no-frozen-lockfile
-
-      - name: Restore tracked install-time changes
-        run: git checkout -- pnpm-lock.yaml
-
-      - name: Configure git author
-        run: |
-          git config user.name "github-actions[bot]"
-          git config user.email "41898282+github-actions[bot]@users.noreply.github.com"
-
-      - name: Publish canary
-        env:
-          GITHUB_ACTIONS: "true"
-        run: ./scripts/release.sh canary --skip-verify
-
-      - name: Push canary tag
-        run: |
-          tag="$(git tag --points-at HEAD | grep '^canary/v' | head -1)"
-          if [ -z "$tag" ]; then
-            echo "Error: no canary tag points at HEAD after release." >&2
-            exit 1
-          fi
-          git push origin "refs/tags/${tag}"
-
-  verify_stable:
-    if: github.event_name == 'workflow_dispatch'
-    runs-on: ubuntu-latest
-    timeout-minutes: 30
-    permissions:
-      contents: read
-
-    steps:
-      - name: Checkout repository
-        uses: actions/checkout@v4
-        with:
-          fetch-depth: 0
-          ref: ${{ inputs.source_ref }}
-
-      - name: Setup pnpm
-        uses: pnpm/action-setup@v4
-        with:
-          version: 9.15.4
-
-      - name: Setup Node.js
-        uses: actions/setup-node@v4
-        with:
-          node-version: 24
-          cache: pnpm
-
-      - name: Validate release package manifest
-        run: node ./scripts/release-package-map.mjs check
-
-      - name: Install dependencies
-        run: pnpm install --no-frozen-lockfile
-
-      - name: Typecheck
-        run: pnpm -r typecheck
-
-      - name: Run tests
-        run: pnpm test:run
-
-      - name: Build
-        run: pnpm build
-
-  preview_stable:
-    if: github.event_name == 'workflow_dispatch' && inputs.dry_run
-    needs: verify_stable
-    runs-on: ubuntu-latest
-    timeout-minutes: 45
-    permissions:
-      contents: read
-
-    steps:
-      - name: Checkout repository
-        uses: actions/checkout@v4
-        with:
-          fetch-depth: 0
-          ref: ${{ inputs.source_ref }}
-
-      - name: Setup pnpm
-        uses: pnpm/action-setup@v4
-        with:
-          version: 9.15.4
-
-      - name: Setup Node.js
-        uses: actions/setup-node@v4
-        with:
-          node-version: 24
-          cache: pnpm
-
-      - name: Validate release package manifest
-        run: node ./scripts/release-package-map.mjs check
-
-      - name: Install dependencies
-        run: pnpm install --no-frozen-lockfile
-
-      - name: Dry-run stable release
-        env:
-          GITHUB_ACTIONS: "true"
-        run: |
-          args=(stable --skip-verify --dry-run)
-          if [ -n "${{ inputs.stable_date }}" ]; then
-            args+=(--date "${{ inputs.stable_date }}")
-          fi
-          ./scripts/release.sh "${args[@]}"
-
-  publish_stable:
-    if: github.event_name == 'workflow_dispatch' && !inputs.dry_run
-    needs: verify_stable
-    runs-on: ubuntu-latest
-    timeout-minutes: 45
-    environment: npm-stable
-    permissions:
-      contents: write
-      id-token: write
-
-    steps:
-      - name: Checkout repository
-        uses: actions/checkout@v4
-        with:
-          fetch-depth: 0
-          ref: ${{ inputs.source_ref }}
-
-      - name: Setup pnpm
-        uses: pnpm/action-setup@v4
-        with:
-          version: 9.15.4
-
-      - name: Setup Node.js
-        uses: actions/setup-node@v4
-        with:
-          node-version: 24
-          cache: pnpm
-
-      - name: Install dependencies
-        run: pnpm install --no-frozen-lockfile
-
-      - name: Restore tracked install-time changes
-        run: git checkout -- pnpm-lock.yaml
-
-      - name: Configure git author
-        run: |
-          git config user.name "github-actions[bot]"
-          git config user.email "41898282+github-actions[bot]@users.noreply.github.com"
-
-      - name: Publish stable
-        env:
-          GITHUB_ACTIONS: "true"
-        run: |
-          args=(stable --skip-verify)
-          if [ -n "${{ inputs.stable_date }}" ]; then
-            args+=(--date "${{ inputs.stable_date }}")
-          fi
-          ./scripts/release.sh "${args[@]}"
-
-      - name: Push stable tag
-        run: |
-          tag="$(git tag --points-at HEAD | grep '^v' | head -1)"
-          if [ -z "$tag" ]; then
-            echo "Error: no stable tag points at HEAD after release." >&2
-            exit 1
-          fi
-          git push origin "refs/tags/${tag}"
-
-      - name: Create GitHub Release
-        env:
-          GH_TOKEN: ${{ github.token }}
-          PUBLISH_REMOTE: origin
-        run: |
-          version="$(git tag --points-at HEAD | grep '^v' | head -1 | sed 's/^v//')"
-          if [ -z "$version" ]; then
-            echo "Error: no v* tag points at HEAD after stable release." >&2
-            exit 1
-          fi
-          ./scripts/create-github-release.sh "$version"

.gitignore

@@ -1,9 +1,5 @@
-node_modules
 node_modules/
-**/node_modules
-**/node_modules/
 dist/
-ui/storybook-static/
 .env
 *.tsbuildinfo
 drizzle/meta/
@@ -36,7 +32,6 @@ server/src/**/*.d.ts
 server/src/**/*.d.ts.map
 tmp/
 feedback-export-*
-diagnostics/
 
 # Editor / tool temp files
 *.tmp
@@ -55,6 +50,4 @@ tests/e2e/playwright-report/
 tests/release-smoke/test-results/
 tests/release-smoke/playwright-report/
 .superset/
-.superpowers/
 .claude/worktrees/
-.herenow

.mailmap

@@ -1,3 +1 @@
-Dotta <bippadotta@protonmail.com> <34892728+cryppadotta@users.noreply.github.com>
-Dotta <bippadotta@protonmail.com> <forgottenrunes@protonmail.com>
-Dotta <bippadotta@protonmail.com> <dotta@example.com>
+Dotta <bippadotta@protonmail.com> Forgotten <forgottenrunes@protonmail.com>

AGENTS.md

@@ -108,24 +108,7 @@ Notes:
 
 ## 7. Verification Before Hand-off
 
-Default local/agent test path:
-
-```sh
-pnpm test
-```
-
-This is the cheap default and only runs the Vitest suite. Browser suites stay opt-in:
-
-```sh
-pnpm test:e2e
-pnpm test:release-smoke
-```
-
-Run the browser suites only when your change touches them or when you are explicitly verifying CI/release flows.
-
-For normal issue work, run the smallest relevant verification first. Do not default to repo-wide typecheck/build/test on every heartbeat when a narrower check is enough to prove the change.
-
-Run this full check before claiming repo work done in a PR-ready hand-off, or when the change scope is broad enough that targeted checks are not sufficient:
+Run this full check before claiming done:
 
 ```sh
 pnpm -r typecheck

CONTRIBUTING.md

@@ -51,21 +51,6 @@ All tests must pass before a PR can be merged. Run them locally first and verify
 
 We use [Greptile](https://greptile.com) for automated code review. Your PR must achieve a **5/5 Greptile score** with **all Greptile comments addressed** before it can be merged. If Greptile leaves comments, fix or respond to each one and request a re-review.
 
-## Feature Contributions
-
-We actively manage the core Paperclip feature roadmap.
-
-Uncoordinated feature PRs against the core product may be closed, even when the implementation is thoughtful and high quality. That is about roadmap ownership, product coherence, and long-term maintenance commitment, not a judgment about the effort.
-
-If you want to contribute a feature:
-
-- Check [ROADMAP.md](ROADMAP.md) first
-- Start the discussion in Discord -> `#dev` before writing code
-- If the idea fits as an extension, prefer building it with the [plugin system](doc/plugins/PLUGIN_SPEC.md)
-- If you want to show a possible direction, reference implementations are welcome as feedback, but they generally will not be merged directly into core
-
-Bugs, docs improvements, and small targeted improvements are still the easiest path to getting merged, and we really do appreciate them.
-
 ## General Rules (both paths)
 
 - Write clear commit messages

Dockerfile

@@ -1,10 +1,12 @@
-# syntax=docker/dockerfile:1.20
 FROM node:lts-trixie-slim AS base
 ARG USER_UID=1000
 ARG USER_GID=1000
 RUN apt-get update \
-  && apt-get install -y --no-install-recommends ca-certificates gosu curl gh git wget ripgrep python3 \
+  && apt-get install -y --no-install-recommends ca-certificates gosu curl git wget ripgrep python3 passwd \
   && rm -rf /var/lib/apt/lists/* \
+  && curl -fsSL https://github.com/cli/cli/releases/download/v2.89.0/gh_2.89.0_linux_amd64.tar.gz | tar -xzf - -C /tmp \
+  && mv /tmp/gh_2.89.0_linux_amd64/bin/gh /usr/local/bin/ \
+  && rm -rf /tmp/gh_* \
   && corepack enable
 
 # Modify the existing node user/group to have the specified UID/GID to match host user
@@ -22,24 +24,15 @@ COPY packages/shared/package.json packages/shared/
 COPY packages/db/package.json packages/db/
 COPY packages/adapter-utils/package.json packages/adapter-utils/
 COPY packages/mcp-server/package.json packages/mcp-server/
-COPY packages/skills-catalog/package.json packages/skills-catalog/
-COPY packages/adapters/acpx-local/package.json packages/adapters/acpx-local/
 COPY packages/adapters/claude-local/package.json packages/adapters/claude-local/
 COPY packages/adapters/codex-local/package.json packages/adapters/codex-local/
-COPY packages/adapters/cursor-cloud/package.json packages/adapters/cursor-cloud/
 COPY packages/adapters/cursor-local/package.json packages/adapters/cursor-local/
 COPY packages/adapters/gemini-local/package.json packages/adapters/gemini-local/
-COPY packages/adapters/grok-local/package.json packages/adapters/grok-local/
 COPY packages/adapters/openclaw-gateway/package.json packages/adapters/openclaw-gateway/
 COPY packages/adapters/opencode-local/package.json packages/adapters/opencode-local/
 COPY packages/adapters/pi-local/package.json packages/adapters/pi-local/
 COPY packages/plugins/sdk/package.json packages/plugins/sdk/
-COPY --parents packages/plugins/sandbox-providers/./*/package.json packages/plugins/sandbox-providers/
-COPY packages/plugins/paperclip-plugin-fake-sandbox/package.json packages/plugins/paperclip-plugin-fake-sandbox/
-COPY packages/plugins/plugin-llm-wiki/package.json packages/plugins/plugin-llm-wiki/
-COPY packages/plugins/plugin-workspace-diff/package.json packages/plugins/plugin-workspace-diff/
 COPY patches/ patches/
-COPY scripts/link-plugin-dev-sdk.mjs scripts/
 
 RUN pnpm install --frozen-lockfile
 
@@ -57,10 +50,18 @@ ARG USER_UID=1000
 ARG USER_GID=1000
 WORKDIR /app
 COPY --chown=node:node --from=build /app /app
-RUN npm install --global --omit=dev @anthropic-ai/claude-code@latest @openai/codex@latest opencode-ai \
-  && apt-get update \
-  && apt-get install -y --no-install-recommends openssh-client jq \
+RUN apt-get update \
+  && apt-get install -y --no-install-recommends jq nano vim \
   && rm -rf /var/lib/apt/lists/* \
+  && curl -fsSL https://dl.k8s.io/release/v1.32.0/bin/linux/amd64/kubectl -o /usr/local/bin/kubectl \
+  && chmod +x /usr/local/bin/kubectl \
+  && curl -fsSL https://github.com/bitnami-labs/sealed-secrets/releases/download/v0.36.6/kubeseal-0.36.6-linux-amd64.tar.gz | tar -xzf - -C /tmp \
+  && mv /tmp/kubeseal /usr/local/bin/kubeseal \
+  && rm -rf /tmp/kubeseal /tmp/LICENSE /tmp/README.md \
+  && curl -LsSf https://astral.sh/uv/install.sh | sh \
+  && mv /root/.local/bin/uv /usr/local/bin/uv \
+  && mv /root/.local/bin/uvx /usr/local/bin/uvx \
+  && npm install --global --omit=dev @anthropic-ai/claude-code@latest @openai/codex@latest opencode-ai hermes-paperclip-adapter \
   && mkdir -p /paperclip \
   && chown node:node /paperclip
 

README.md

@@ -1,14 +1,12 @@
 <p align="center">
-  <img src="doc/assets/banner.jpg" alt="Paperclip is the app people use to manage AI agents for work." width="720" />
+  <img src="doc/assets/header.png" alt="Paperclip — runs your business" width="720" />
 </p>
 
 <p align="center">
   <a href="#quickstart"><strong>Quickstart</strong></a> &middot;
   <a href="https://paperclip.ing/docs"><strong>Docs</strong></a> &middot;
   <a href="https://github.com/paperclipai/paperclip"><strong>GitHub</strong></a> &middot;
-  <a href="https://discord.gg/m4HZY7xNG3"><strong>Discord</strong></a> &middot;
-  <a href="https://x.com/papercliping"><strong>Twitter</strong></a> &middot;
-  <a href="https://paperclip.ing"><strong>Website</strong></a>
+  <a href="https://discord.gg/m4HZY7xNG3"><strong>Discord</strong></a>
 </p>
 
 <p align="center">
@@ -25,15 +23,15 @@
 
 <br/>
 
-# Paperclip is the app people use to manage AI agents for work.
+## What is Paperclip?
 
-Open-source orchestration for teams of AI agents.
+# Open-source orchestration for zero-human companies
 
-**If OpenClaw is an _employee_, Paperclip is the _company_.**
+**If OpenClaw is an _employee_, Paperclip is the _company_**
 
-Paperclip is a Node.js server and React UI that orchestrates a team of AI agents to run a business. Bring your own agents, assign goals, and track work and costs from one dashboard.
+Paperclip is a Node.js server and React UI that orchestrates a team of AI agents to run a business. Bring your own agents, assign goals, and track your agents' work and costs from one dashboard.
 
-It looks like a task manager. Under the hood: org charts, budgets, governance, goal alignment, and agent coordination.
+It looks like a task manager — but under the hood it has org charts, budgets, governance, goal alignment, and agent coordination.
 
 **Manage business goals, not pull requests.**
 
@@ -45,6 +43,10 @@ It looks like a task manager. Under the hood: org charts, budgets, governance, g
 
 <br/>
 
+> **COMING SOON: Clipmart** — Download and run entire companies with one click. Browse pre-built company templates — full org structures, agent configs, and skills — and import them into your Paperclip instance in seconds.
+
+<br/>
+
 <div align="center">
 <table>
   <tr>
@@ -110,7 +112,7 @@ Every conversation traced. Every decision explained. Full tool-call tracing and
 <tr>
 <td align="center">
 <h3>🛡️ Governance</h3>
-Approve hires, override strategy, pause or terminate any agent — at any time.
+You're the board. Approve hires, override strategy, pause or terminate any agent — at any time.
 </td>
 <td align="center">
 <h3>📊 Org Chart</h3>
@@ -154,115 +156,6 @@ Paperclip handles the hard orchestration details correctly.
 
 <br/>
 
-## What's Under the Hood
-
-Paperclip is a full control plane, not a wrapper. Before you build any of this yourself, know that it already exists:
-
-```
-┌──────────────────────────────────────────────────────────────┐
-│                       PAPERCLIP SERVER                       │
-│                                                              │
-│  ┌───────────┐  ┌───────────┐  ┌───────────┐  ┌───────────┐  │
-│  │Identity & │  │  Work &   │  │ Heartbeat │  │Governance │  │
-│  │  Access   │  │   Tasks   │  │ Execution │  │& Approvals│  │
-│  └───────────┘  └───────────┘  └───────────┘  └───────────┘  │
-│                                                              │
-│  ┌───────────┐  ┌───────────┐  ┌───────────┐  ┌───────────┐  │
-│  │ Org Chart │  │Workspaces │  │  Plugins  │  │  Budget   │  │
-│  │ & Agents  │  │ & Runtime │  │           │  │ & Costs   │  │
-│  └───────────┘  └───────────┘  └───────────┘  └───────────┘  │
-│                                                              │
-│  ┌───────────┐  ┌───────────┐  ┌───────────┐  ┌───────────┐  │
-│  │ Routines  │  │ Secrets & │  │ Activity  │  │  Company  │  │
-│  │& Schedules│  │  Storage  │  │ & Events  │  │Portability│  │
-│  └───────────┘  └───────────┘  └───────────┘  └───────────┘  │
-└──────────────────────────────────────────────────────────────┘
-         ▲              ▲              ▲              ▲
-   ┌─────┴─────┐  ┌─────┴─────┐  ┌─────┴─────┐  ┌─────┴─────┐
-   │  Claude   │  │   Codex   │  │   CLI     │  │ HTTP/web  │
-   │   Code    │  │           │  │  agents   │  │   bots    │
-   └───────────┘  └───────────┘  └───────────┘  └───────────┘
-```
-
-### The Systems
-
-<table>
-<tr>
-<td width="50%">
-
-**Identity & Access** — Two deployment modes (trusted local or authenticated), board users, agent API keys, short-lived run JWTs, company memberships, invite flows, and OpenClaw onboarding. Every mutating request is traced to an actor.
-
-</td>
-<td width="50%">
-
-**Org Chart & Agents** — Agents have roles, titles, reporting lines, permissions, and budgets. Adapter examples match the diagram: Claude Code, Codex, CLI agents such as Cursor/Gemini/bash, HTTP/webhook bots such as OpenClaw, and external adapter plugins. If it can receive a heartbeat, it's hired.
-
-</td>
-</tr>
-<tr>
-<td>
-
-**Work & Task System** — Issues carry company/project/goal/parent links, atomic checkout with execution locks, first-class blocker dependencies, comments, documents, attachments, work products, labels, and inbox state. No double-work, no lost context.
-
-</td>
-<td>
-
-**Heartbeat Execution** — DB-backed wakeup queue with coalescing, budget checks, workspace resolution, secret injection, skill loading, and adapter invocation. Runs produce structured logs, cost events, session state, and audit trails. Recovery handles orphaned runs automatically.
-
-</td>
-</tr>
-<tr>
-<td>
-
-**Workspaces & Runtime** — Project workspaces, isolated execution workspaces (git worktrees, operator branches), and runtime services (dev servers, preview URLs). Agents work in the right directory with the right context every time.
-
-</td>
-<td>
-
-**Governance & Approvals** — Board approval workflows, execution policies with review/approval stages, decision tracking, budget hard-stops, agent pause/resume/terminate, and full audit logging. Nothing ships without your sign-off.
-
-</td>
-</tr>
-<tr>
-<td>
-
-**Budget & Cost Control** — Token and cost tracking by company, agent, project, goal, issue, provider, and model. Scoped budget policies with warning thresholds and hard stops. Overspend pauses agents and cancels queued work automatically.
-
-</td>
-<td>
-
-**Routines & Schedules** — Recurring tasks with cron, webhook, and API triggers. Concurrency and catch-up policies. Each routine execution creates a tracked issue and wakes the assigned agent — no manual kick-offs needed.
-
-</td>
-</tr>
-<tr>
-<td>
-
-**Plugins** — Instance-wide plugin system with out-of-process workers, capability-gated host services, job scheduling, tool exposure, and UI contributions. Extend Paperclip without forking it.
-
-</td>
-<td>
-
-**Secrets & Storage** — Instance and company secrets, encrypted local storage, provider-backed object storage, attachments, and work products. Sensitive values stay out of prompts unless a scoped run explicitly needs them.
-
-</td>
-</tr>
-<tr>
-<td>
-
-**Activity & Events** — Mutating actions, heartbeat state changes, cost events, approvals, comments, and work products are recorded as durable activity so operators can audit what happened and why.
-
-</td>
-<td>
-
-**Company Portability** — Export and import entire organizations — agents, skills, projects, routines, and issues — with secret scrubbing and collision handling. One deployment, many companies, complete data isolation.
-
-</td>
-</tr>
-</table>
-
-<br/>
-
 ## What Paperclip is not
 
 |                              |                                                                                                                      |
@@ -284,14 +177,6 @@ Open source. Self-hosted. No Paperclip account required.
 npx paperclipai onboard --yes
 ```
 
-That quickstart path now defaults to trusted local loopback mode for the fastest first run. To start in authenticated/private mode instead, choose a bind preset explicitly:
-
-```bash
-npx paperclipai onboard --yes --bind lan
-# or:
-npx paperclipai onboard --yes --bind tailnet
-```
-
 If you already have Paperclip configured, rerunning `onboard` keeps the existing config in place. Use `paperclipai configure` to edit settings.
 
 Or manually:
@@ -314,7 +199,7 @@ This starts the API server at `http://localhost:3100`. An embedded PostgreSQL da
 **What does a typical setup look like?**
 Locally, a single Node.js process manages an embedded Postgres and local file storage. For production, point it at your own Postgres and deploy however you like. Configure projects, agents, and goals — the agents take care of the rest.
 
-If you're a solo entrepreneur you can use Tailscale to access Paperclip on the go. Then later you can deploy to e.g. Vercel when you need it.
+If you're a solo-entreprenuer you can use Tailscale to access Paperclip on the go. Then later you can deploy to e.g. Vercel when you need it.
 
 **Can I run multiple companies?**
 Yes. A single deployment can run an unlimited number of companies with complete data isolation.
@@ -340,15 +225,11 @@ pnpm dev:once         # Full dev without file watching
 pnpm dev:server       # Server only
 pnpm build            # Build all
 pnpm typecheck        # Type checking
-pnpm test             # Cheap default test run (Vitest only)
-pnpm test:watch       # Vitest watch mode
-pnpm test:e2e         # Playwright browser suite
+pnpm test:run         # Run tests
 pnpm db:generate      # Generate DB migration
 pnpm db:migrate       # Apply migrations
 ```
 
-`pnpm test` does not run Playwright. Browser suites stay separate and are typically run only when working on those flows or in CI.
-
 See [doc/DEVELOPING.md](doc/DEVELOPING.md) for the full development guide.
 
 <br/>
@@ -362,23 +243,14 @@ See [doc/DEVELOPING.md](doc/DEVELOPING.md) for the full development guide.
 - ✅ Skills Manager
 - ✅ Scheduled Routines
 - ✅ Better Budgeting
-- ✅ Agent Reviews and Approvals
-- ✅ Multiple Human Users
-- ⚪ Cloud / Sandbox agents (e.g. Cursor / e2b agents)
-- ⚪ Artifacts & Work Products
-- ⚪ Memory / Knowledge
-- ⚪ Enforced Outcomes
-- ⚪ MAXIMIZER MODE
-- ⚪ Deep Planning
-- ⚪ Work Queues
-- ⚪ Self-Organization
-- ⚪ Automatic Organizational Learning
+- ⚪ Artifacts & Deployments
 - ⚪ CEO Chat
+- ⚪ MAXIMIZER MODE
+- ⚪ Multiple Human Users
+- ⚪ Cloud / Sandbox agents (e.g. Cursor / e2b agents)
 - ⚪ Cloud deployments
 - ⚪ Desktop App
 
-This is the short roadmap preview. See the full roadmap in [ROADMAP.md](ROADMAP.md).
-
 <br/>
 
 ## Community & Plugins
@@ -391,12 +263,12 @@ Paperclip collects anonymous usage telemetry to help us understand how the produ
 
 Telemetry is **enabled by default** and can be disabled with any of the following:
 
-| Method               | How                                                     |
-| -------------------- | ------------------------------------------------------- |
-| Environment variable | `PAPERCLIP_TELEMETRY_DISABLED=1`                        |
-| Standard convention  | `DO_NOT_TRACK=1`                                        |
-| CI environments      | Automatically disabled when `CI=true`                   |
-| Config file          | Set `telemetry.enabled: false` in your Paperclip config |
+| Method | How |
+|---|---|
+| Environment variable | `PAPERCLIP_TELEMETRY_DISABLED=1` |
+| Standard convention | `DO_NOT_TRACK=1` |
+| CI environments | Automatically disabled when `CI=true` |
+| Config file | Set `telemetry.enabled: false` in your Paperclip config |
 
 ## Contributing
 
@@ -407,7 +279,6 @@ We welcome contributions. See the [contributing guide](CONTRIBUTING.md) for deta
 ## Community
 
 - [Discord](https://discord.gg/m4HZY7xNG3) — Join the community
-- [Twitter / X](https://x.com/papercliping) — Follow updates and announcements
 - [GitHub Issues](https://github.com/paperclipai/paperclip/issues) — bugs and feature requests
 - [GitHub Discussions](https://github.com/paperclipai/paperclip/discussions) — ideas and RFC
 
@@ -415,7 +286,7 @@ We welcome contributions. See the [contributing guide](CONTRIBUTING.md) for deta
 
 ## License
 
-MIT &copy; 2026 [Paperclip Labs, Inc](https://paperclip.ing)
+MIT &copy; 2026 Paperclip
 
 ## Star History
 
@@ -426,5 +297,9 @@ MIT &copy; 2026 [Paperclip Labs, Inc](https://paperclip.ing)
 ---
 
 <p align="center">
-  <sub>Open source under MIT. Built for people who want to get work done, not babysit agents.</sub>
+  <img src="doc/assets/footer.jpg" alt="" width="720" />
+</p>
+
+<p align="center">
+  <sub>Open source under MIT. Built for people who want to run companies, not babysit agents.</sub>
 </p>

ROADMAP.md

@@ -1,97 +0,0 @@
-# Roadmap
-
-This document expands the roadmap preview in `README.md`.
-
-Paperclip is still moving quickly. The list below is directional, not promised, and priorities may shift as we learn from users and from operating real AI companies with the product.
-
-We value community involvement and want to make sure contributor energy goes toward areas where it can land.
-
-We may accept contributions in the areas below, but if you want to work on roadmap-level core features, please coordinate with us first in Discord (`#dev`) before writing code. Bugs, docs, polish, and tightly scoped improvements are still the easiest contributions to merge.
-
-If you want to extend Paperclip today, the best path is often the [plugin system](doc/plugins/PLUGIN_SPEC.md). Community reference implementations are also useful feedback even when they are not merged directly into core.
-
-## Milestones
-
-### ✅ Plugin system
-
-Paperclip should keep a thin core and rich edges. Plugins are the path for optional capabilities like knowledge bases, custom tracing, queues, doc editors, and other product-specific surfaces that do not need to live in the control plane itself.
-
-### ✅ Get OpenClaw / claw-style agent employees
-
-Paperclip should be able to hire and manage real claw-style agent workers, not just a narrow built-in runtime. This is part of the larger "bring your own agent" story and keeps the control plane useful across different agent ecosystems.
-
-### ✅ companies.sh - import and export entire organizations
-
-Reusable companies matter. Import/export is the foundation for moving org structures, agent definitions, and reusable company setups between environments and eventually for broader company-template distribution.
-
-### ✅ Easy AGENTS.md configurations
-
-Agent setup should feel repo-native and legible. Simple `AGENTS.md`-style configuration lowers the barrier to getting an agent team running and makes it easier for contributors to understand how a company is wired together.
-
-### ✅ Skills Manager
-
-Agents need a practical way to discover, install, and use skills without every setup becoming bespoke. The skills layer is part of making Paperclip companies more reusable and easier to operate.
-
-### ✅ Scheduled Routines
-
-Recurring work should be native. Routine tasks like reports, reviews, and other periodic work need first-class scheduling so the company keeps operating even when no human is manually kicking work off.
-
-### ✅ Better Budgeting
-
-Budgets are a core control-plane feature, not an afterthought. Better budgeting means clearer spend visibility, safer hard stops, and better operator control over how autonomy turns into real cost.
-
-### ✅ Agent Reviews and Approvals
-
-Paperclip should support explicit review and approval stages as first-class workflow steps, not just ad hoc comments. That means reviewer routing, approval gates, change requests, and durable audit trails that fit the same task model as the rest of the control plane.
-
-### ✅ Multiple Human Users
-
-Paperclip needs a clearer path from solo operator to real human teams. That means shared board access, safer collaboration, and a better model for several humans supervising the same autonomous company.
-
-### ⚪ Cloud / Sandbox agents (e.g. Cursor / e2b agents)
-
-We want agents to run in more remote and sandboxed environments while preserving the same Paperclip control-plane model. This makes the system safer, more flexible, and more useful outside a single trusted local machine.
-
-### ⚪ Artifacts & Work Products
-
-Paperclip should make outputs first-class. That means generated artifacts, previews, deployable outputs, and the handoff from "agent did work" to "here is the result" should become more visible and easier to operate.
-
-### ⚪ Memory / Knowledge
-
-We want a stronger memory and knowledge surface for companies, agents, and projects. That includes durable memory, better recall of prior decisions and context, and a clearer path for knowledge-style capabilities without turning Paperclip into a generic chat app.
-
-### ⚪ Enforced Outcomes
-
-Paperclip should get stricter about what counts as finished work. Tasks, approvals, and execution flows should resolve to clear outcomes like merged code, published artifacts, shipped docs, or explicit decisions instead of stopping at vague status updates.
-
-### ⚪ MAXIMIZER MODE
-
-This is the direction for higher-autonomy execution: more aggressive delegation, deeper follow-through, and stronger operating loops with clear budgets, visibility, and governance. The point is not hidden autonomy; the point is more output per human supervisor.
-
-### ⚪ Deep Planning
-
-Some work needs more than a task description before execution starts. Deeper planning means stronger issue documents, revisionable plans, and clearer review loops for strategy-heavy work before agents begin execution.
-
-### ⚪ Work Queues
-
-Paperclip should support queue-style work streams for repeatable inputs like support, triage, review, and backlog intake. That would make it easier to route work continuously without turning every system into a one-off workflow.
-
-### ⚪ Self-Organization
-
-As companies grow, agents should be able to propose useful structural changes such as role adjustments, delegation changes, and new recurring routines. The goal is adaptive organizations that still stay within governance and approval boundaries.
-
-### ⚪ Automatic Organizational Learning
-
-Paperclip should get better at turning completed work into reusable organizational knowledge. That includes capturing playbooks, recurring fixes, and decision patterns so future work starts from what the company has already learned.
-
-### ⚪ CEO Chat
-
-We want a lighter-weight way to talk to leadership agents, but those conversations should still resolve to real work objects like plans, issues, approvals, or decisions. This should improve interaction without changing the core task-and-comments model.
-
-### ⚪ Cloud deployments
-
-Local-first remains important, but Paperclip also needs a cleaner shared deployment story. Teams should be able to run the same product in hosted or semi-hosted environments without changing the mental model.
-
-### ⚪ Desktop App
-
-A desktop app can make Paperclip feel more accessible and persistent for day-to-day operators. The goal is easier access, better local ergonomics, and a smoother default experience for users who want the control plane always close at hand.

SECURITY.md

@@ -1,8 +0,0 @@
-# Security Policy
-
-## Reporting a Vulnerability
-
-Please report security vulnerabilities through GitHub's Security Advisory feature:
-[https://github.com/paperclipai/paperclip/security/advisories/new](https://github.com/paperclipai/paperclip/security/advisories/new)
-
-Do not open public issues for security vulnerabilities.

cli/README.md

@@ -6,14 +6,13 @@
   <a href="#quickstart"><strong>Quickstart</strong></a> &middot;
   <a href="https://paperclip.ing/docs"><strong>Docs</strong></a> &middot;
   <a href="https://github.com/paperclipai/paperclip"><strong>GitHub</strong></a> &middot;
-  <a href="https://discord.gg/m4HZY7xNG3"><strong>Discord</strong></a> &middot;
-  <a href="https://x.com/papercliping"><strong>Twitter</strong></a>
+  <a href="https://discord.gg/m4HZY7xNG3"><strong>Discord</strong></a>
 </p>
 
 <p align="center">
   <a href="https://github.com/paperclipai/paperclip/blob/master/LICENSE"><img src="https://img.shields.io/badge/license-MIT-blue" alt="MIT License" /></a>
   <a href="https://github.com/paperclipai/paperclip/stargazers"><img src="https://img.shields.io/github/stars/paperclipai/paperclip?style=flat" alt="Stars" /></a>
-  <a href="https://discord.gg/m4HZY7xNG3"><img src="https://img.shields.io/discord/000000000?label=discord" alt="Discord" /></a>
+  <a href="https://discord.gg/m4HZY7xNG3"><img src="https://img.shields.io/badge/discord-join%20chat-5865F2?logo=discord&logoColor=white" alt="Discord" /></a>
 </p>
 
 <br/>
@@ -178,14 +177,6 @@ Open source. Self-hosted. No Paperclip account required.
 npx paperclipai onboard --yes
 ```
 
-That quickstart path now defaults to trusted local loopback mode for the fastest first run. To start in authenticated/private mode instead, choose a bind preset explicitly:
-
-```bash
-npx paperclipai onboard --yes --bind lan
-# or:
-npx paperclipai onboard --yes --bind tailnet
-```
-
 If you already have Paperclip configured, rerunning `onboard` keeps the existing config in place. Use `paperclipai configure` to edit settings.
 
 Or manually:
@@ -226,21 +217,6 @@ By default, agents run on scheduled heartbeats and event-based triggers (task as
 
 <br/>
 
-## Paperclip Cloud Sync
-
-Cloud upstream sync is behind the `Cloud Sync` experimental setting. Enable it in Instance Settings before pushing.
-
-```bash
-paperclipai cloud connect https://your-stack.paperclip.app
-paperclipai cloud connect https://your-stack.paperclip.app --no-browser
-paperclipai cloud push --company <local-company-id> --dry-run
-paperclipai cloud push --company <local-company-id>
-```
-
-`cloud connect` authorizes the local instance against the target stack and stores the upstream token in the local instance secret store. The default path opens a browser for consent; `--no-browser` uses the device-code flow and prints the verification URL and user code.
-
-`cloud push --dry-run` exports the selected local company, sends a preview bundle to the connected Cloud stack, and exits with code `2` when conflicts need user resolution. A schema mismatch exits with code `3`. Running without `--dry-run` stages chunks idempotently, applies the run, and prints the final summary and recent progress events.
-
 ## Development
 
 ```bash
@@ -249,15 +225,11 @@ pnpm dev:once         # Full dev without file watching
 pnpm dev:server       # Server only
 pnpm build            # Build all
 pnpm typecheck        # Type checking
-pnpm test             # Cheap default test run (Vitest only)
-pnpm test:watch       # Vitest watch mode
-pnpm test:e2e         # Playwright browser suite
+pnpm test:run         # Run tests
 pnpm db:generate      # Generate DB migration
 pnpm db:migrate       # Apply migrations
 ```
 
-`pnpm test` does not run Playwright. Browser suites stay separate and are typically run only when working on those flows or in CI.
-
 See [doc/DEVELOPING.md](https://github.com/paperclipai/paperclip/blob/master/doc/DEVELOPING.md) for the full development guide.
 
 <br/>
@@ -274,7 +246,7 @@ See [doc/DEVELOPING.md](https://github.com/paperclipai/paperclip/blob/master/doc
 - ⚪ Artifacts & Deployments
 - ⚪ CEO Chat
 - ⚪ MAXIMIZER MODE
-- ✅ Multiple Human Users
+- ⚪ Multiple Human Users
 - ⚪ Cloud / Sandbox agents (e.g. Cursor / e2b agents)
 - ⚪ Cloud deployments
 - ⚪ Desktop App
@@ -294,7 +266,6 @@ We welcome contributions. See the [contributing guide](https://github.com/paperc
 ## Community
 
 - [Discord](https://discord.gg/m4HZY7xNG3) — Join the community
-- [Twitter / X](https://x.com/papercliping) — Follow updates and announcements
 - [GitHub Issues](https://github.com/paperclipai/paperclip/issues) — bugs and feature requests
 - [GitHub Discussions](https://github.com/paperclipai/paperclip/discussions) — ideas and RFC
 

cli/package.json

@@ -37,13 +37,10 @@
   },
   "dependencies": {
     "@clack/prompts": "^0.10.0",
-    "@paperclipai/adapter-acpx-local": "workspace:*",
     "@paperclipai/adapter-claude-local": "workspace:*",
     "@paperclipai/adapter-codex-local": "workspace:*",
-    "@paperclipai/adapter-cursor-cloud": "workspace:*",
     "@paperclipai/adapter-cursor-local": "workspace:*",
     "@paperclipai/adapter-gemini-local": "workspace:*",
-    "@paperclipai/adapter-grok-local": "workspace:*",
     "@paperclipai/adapter-opencode-local": "workspace:*",
     "@paperclipai/adapter-pi-local": "workspace:*",
     "@paperclipai/adapter-openclaw-gateway": "workspace:*",
@@ -51,7 +48,7 @@
     "@paperclipai/db": "workspace:*",
     "@paperclipai/server": "workspace:*",
     "@paperclipai/shared": "workspace:*",
-    "drizzle-orm": "0.45.2",
+    "drizzle-orm": "0.38.4",
     "dotenv": "^17.0.1",
     "commander": "^13.1.0",
     "embedded-postgres": "^18.1.0-beta.16",

cli/src/__tests__/cloud.test.ts

@@ -1,243 +0,0 @@
-import fs from "node:fs";
-import os from "node:os";
-import path from "node:path";
-import { afterEach, beforeEach, describe, expect, it, vi } from "vitest";
-import type { CompanyPortabilityExportResult } from "@paperclipai/shared";
-import {
-  assertDiscoveryCompatible,
-  buildBundleFromLocalCompany,
-  cloudCommandExitCodes,
-  connectCloud,
-  resolveDeviceCodeExpiresAt,
-} from "../commands/client/cloud.js";
-import {
-  LocalUpstreamPushCoordinator,
-  normalizedContentHash,
-  type LocalUpstreamExportBundle,
-} from "../commands/client/cloud-transfer.js";
-import { getCloudConnection } from "../commands/client/cloud-store.js";
-
-const originalEnv = { ...process.env };
-const originalFetch = globalThis.fetch;
-
-describe("cloud CLI helpers", () => {
-  let tempHome: string;
-
-  beforeEach(() => {
-    tempHome = fs.mkdtempSync(path.join(os.tmpdir(), "paperclip-cloud-cli-"));
-    process.env = { ...originalEnv, PAPERCLIP_HOME: tempHome };
-  });
-
-  afterEach(() => {
-    process.env = { ...originalEnv };
-    globalThis.fetch = originalFetch;
-    vi.restoreAllMocks();
-    fs.rmSync(tempHome, { recursive: true, force: true });
-  });
-
-  it("connects with the device-code flow and stores the resulting cloud connection", async () => {
-    globalThis.fetch = vi.fn(async (url, init) => {
-      const requestUrl = String(url);
-      if (requestUrl.endsWith("/.well-known/paperclip-upstream")) {
-        return jsonResponse(discovery());
-      }
-      if (requestUrl.endsWith("/api/upstream-sync/device-code")) {
-        expect(JSON.parse(String(init?.body))).toMatchObject({
-          stackId: "stack-1",
-          scopes: ["upstream_import:preview", "upstream_import:write", "upstream_import:read"],
-        });
-        return jsonResponse({
-          deviceCode: "device-1",
-          userCode: "ABCD-EFGH",
-          verificationUri: "https://cloud.example.test/api/upstream-sync/device-code/approve",
-          expiresAt: new Date(Date.now() + 60_000).toISOString(),
-          intervalSeconds: 0,
-        });
-      }
-      if (requestUrl.endsWith("/api/upstream-sync/token")) {
-        return jsonResponse({
-          accessToken: "upt_test",
-          scopes: ["upstream_import:preview"],
-          token: {
-            id: "token-1",
-            companyStackId: "stack-1",
-            targetOrigin: "https://cloud.example.test",
-            sourceInstanceId: "paperclip-local-default",
-            sourceInstanceFingerprint: "sha256:test",
-            scopes: ["upstream_import:preview"],
-            expiresAt: new Date(Date.now() + 60_000).toISOString(),
-          },
-        });
-      }
-      return jsonResponse({ error: "not_found" }, 404);
-    }) as typeof fetch;
-
-    const connection = await connectCloud("https://cloud.example.test", { noBrowser: true, json: true });
-
-    expect(connection.accessToken).toBe("upt_test");
-    expect(getCloudConnection("https://cloud.example.test")?.token.id).toBe("token-1");
-  });
-
-  it("hard-blocks incompatible transfer schema versions with the stable schema exit code", () => {
-    expect(() => assertDiscoveryCompatible(discovery({ supportedSchemaMajor: 99 }))).toThrow(/schema mismatch/i);
-    expect(cloudCommandExitCodes.schemaMismatch).toBe(3);
-  });
-
-  it("falls back to a bounded device-code expiry when the cloud omits or malforms expiresAt", () => {
-    const now = Date.UTC(2026, 4, 22, 13, 0, 0);
-    const validExpiry = "2026-05-22T13:05:00.000Z";
-
-    expect(resolveDeviceCodeExpiresAt(validExpiry, now)).toBe(Date.parse(validExpiry));
-    expect(resolveDeviceCodeExpiresAt(undefined, now)).toBe(now + 15 * 60_000);
-    expect(resolveDeviceCodeExpiresAt("not-a-date", now)).toBe(now + 15 * 60_000);
-  });
-
-  it("builds deterministic chunks with validated payload hashes", async () => {
-    const bundle = await buildTestBundle();
-
-    expect(bundle.chunks).toHaveLength(2);
-    expect(bundle.chunks[0]?.sha256).toBe(normalizedContentHash(bundle.chunks[0]?.payload));
-    expect(bundle.manifest.chunks[0]?.manifestHash).toBe(bundle.manifest.manifestHash);
-    expect(bundle.manifest.idempotencyKey).toBe((await buildTestBundle()).manifest.idempotencyKey);
-  });
-
-  it("reuses the same manifest and chunk identity when an interrupted apply is retried", async () => {
-    const bundle = await buildTestBundle();
-    const calls: Array<{ path: string; body: unknown }> = [];
-    const coordinator = new LocalUpstreamPushCoordinator({
-      targetOrigin: "https://cloud.example.test",
-      paperclipCompanyId: "target-company-1",
-      fetch: async (url, init) => {
-        const parsed = new URL(String(url));
-        const body = init?.body ? JSON.parse(String(init.body)) as unknown : {};
-        calls.push({ path: parsed.pathname, body });
-        if (parsed.pathname.endsWith("/runs")) return jsonResponse({ run: { id: "run-1" } });
-        return jsonResponse({ run: { id: "run-1" }, summary: { create: 0, update: 0, adopt: 0, skip: 2, conflict: 0, staleMapping: 0 } });
-      },
-    });
-
-    await coordinator.apply(bundle);
-    await coordinator.apply(bundle);
-
-    const runBodies = calls.filter((call) => call.path.endsWith("/runs")).map((call) => call.body as { manifest: { idempotencyKey: string } });
-    const chunkBodies = calls.filter((call) => call.path.endsWith("/chunks")).map((call) => call.body as { chunkIndex: number; sha256: string });
-    expect(runBodies).toHaveLength(2);
-    expect(runBodies[0]?.manifest.idempotencyKey).toBe(runBodies[1]?.manifest.idempotencyKey);
-    expect(chunkBodies[0]).toEqual(chunkBodies[2]);
-    expect(chunkBodies[1]).toEqual(chunkBodies[3]);
-  });
-});
-
-async function buildTestBundle(): Promise<LocalUpstreamExportBundle> {
-  return buildBundleFromLocalCompany({
-    localCompanyId: "local-company-1",
-    connection: {
-      id: "conn-1",
-      remoteUrl: "https://cloud.example.test",
-      targetOrigin: "https://cloud.example.test",
-      targetHost: "cloud.example.test",
-      stackId: "stack-1",
-      targetCompanyId: "target-company-1",
-      accessToken: "upt_test",
-      token: {
-        id: "token-1",
-        companyStackId: "stack-1",
-        targetOrigin: "https://cloud.example.test",
-        sourceInstanceId: "paperclip-local-default",
-        sourceInstanceFingerprint: "sha256:test",
-        scopes: ["upstream_import:preview"],
-        expiresAt: new Date(Date.now() + 60_000).toISOString(),
-      },
-      privateKeyPem: "unused",
-      sourcePublicKey: "unused",
-      sourceInstanceId: "paperclip-local-default",
-      sourceInstanceFingerprint: "sha256:test",
-      scopes: ["upstream_import:preview"],
-      createdAt: "2026-05-18T00:00:00.000Z",
-      updatedAt: "2026-05-18T00:00:00.000Z",
-    },
-    discovery: discovery(),
-    localApi: {
-      post: async <T>() => portabilityExport() as T,
-    },
-    maxEntitiesPerChunk: 1,
-    mode: "apply",
-  });
-}
-
-function discovery(overrides: Partial<{ supportedSchemaMajor: number }> = {}) {
-  return {
-    schema: "paperclip-upstream-discovery-v1",
-    stack: {
-      id: "stack-1",
-      slug: "cloud-test",
-      displayName: "Cloud Test",
-      companyId: "target-company-1",
-      origin: "https://cloud.example.test",
-    },
-    auth: {
-      deviceCode: {
-        deviceCodeUrl: "https://cloud.example.test/api/upstream-sync/device-code",
-        verificationUrl: "https://cloud.example.test/api/upstream-sync/device-code/approve",
-        tokenUrl: "https://cloud.example.test/api/upstream-sync/token",
-      },
-      scopes: ["upstream_import:preview", "upstream_import:write", "upstream_import:read"],
-    },
-    transfer: {
-      supportedSchemaMajor: overrides.supportedSchemaMajor ?? 1,
-      featureFlags: ["cloud_sync"],
-    },
-  };
-}
-
-function portabilityExport(): CompanyPortabilityExportResult {
-  return {
-    rootPath: ".",
-    paperclipExtensionPath: ".paperclip.yaml",
-    manifest: {
-      schemaVersion: 1,
-      generatedAt: "2026-05-18T00:00:00.000Z",
-      source: {
-        companyId: "local-company-1",
-        companyName: "Local Company",
-      },
-      includes: {
-        company: true,
-        agents: true,
-        projects: true,
-        issues: true,
-        skills: true,
-      },
-      company: {
-        path: "company.json",
-        name: "Local Company",
-        description: null,
-        brandColor: null,
-        logoPath: null,
-        attachmentMaxBytes: null,
-        requireBoardApprovalForNewAgents: false,
-        feedbackDataSharingEnabled: false,
-        feedbackDataSharingConsentAt: null,
-        feedbackDataSharingConsentByUserId: null,
-        feedbackDataSharingTermsVersion: null,
-      },
-      sidebar: null,
-      agents: [],
-      skills: [],
-      projects: [],
-      issues: [],
-      envInputs: [],
-    },
-    files: {
-      "README.md": "Local Company",
-    },
-    warnings: [],
-  };
-}
-
-function jsonResponse(body: unknown, status = 200): Response {
-  return new Response(JSON.stringify(body), {
-    status,
-    headers: { "Content-Type": "application/json" },
-  });
-}

cli/src/__tests__/company-delete.test.ts

@@ -14,7 +14,6 @@ function makeCompany(overrides: Partial<Company>): Company {
     issueCounter: 1,
     budgetMonthlyCents: 0,
     spentMonthlyCents: 0,
-    attachmentMaxBytes: 10 * 1024 * 1024,
     requireBoardApprovalForNewAgents: false,
     feedbackDataSharingEnabled: false,
     feedbackDataSharingConsentAt: null,

cli/src/__tests__/company-import-export-e2e.test.ts

@@ -1,5 +1,5 @@
 import { execFile, spawn } from "node:child_process";
-import { existsSync, mkdirSync, mkdtempSync, readFileSync, readdirSync, rmSync, writeFileSync } from "node:fs";
+import { mkdirSync, mkdtempSync, readFileSync, readdirSync, rmSync, writeFileSync } from "node:fs";
 import net from "node:net";
 import os from "node:os";
 import path from "node:path";
@@ -104,50 +104,20 @@ function writeTestConfig(configPath: string, tempRoot: string, port: number, con
   writeFileSync(configPath, `${JSON.stringify(config, null, 2)}\n`, "utf8");
 }
 
-interface TestPaperclipEnv {
-  configPath: string;
-  paperclipHome: string;
-  instanceId: string;
-  shellHome?: string;
-}
-
-function createBasePaperclipEnv(options: TestPaperclipEnv) {
+function createServerEnv(configPath: string, port: number, connectionString: string) {
   const env = { ...process.env };
   for (const key of Object.keys(env)) {
     if (key.startsWith("PAPERCLIP_")) {
       delete env[key];
     }
   }
-
-  env.PAPERCLIP_CONFIG = options.configPath;
-  env.PAPERCLIP_HOME = options.paperclipHome;
-  env.PAPERCLIP_INSTANCE_ID = options.instanceId;
-  env.PAPERCLIP_CONTEXT = path.join(options.paperclipHome, "context.json");
-  env.PAPERCLIP_AUTH_STORE = path.join(options.paperclipHome, "auth.json");
-  if (options.shellHome) {
-    env.HOME = options.shellHome;
-  }
-
-  return env;
-}
-
-function createServerEnv(
-  configPath: string,
-  port: number,
-  connectionString: string,
-  options: Omit<TestPaperclipEnv, "configPath">,
-) {
-  const env = createBasePaperclipEnv({
-    configPath,
-    ...options,
-  });
-
   delete env.DATABASE_URL;
   delete env.PORT;
   delete env.HOST;
   delete env.SERVE_UI;
   delete env.HEARTBEAT_SCHEDULER_ENABLED;
 
+  env.PAPERCLIP_CONFIG = configPath;
   env.DATABASE_URL = connectionString;
   env.HOST = "127.0.0.1";
   env.PORT = String(port);
@@ -160,8 +130,13 @@ function createServerEnv(
   return env;
 }
 
-function createCliEnv(options: TestPaperclipEnv) {
-  const env = createBasePaperclipEnv(options);
+function createCliEnv() {
+  const env = { ...process.env };
+  for (const key of Object.keys(env)) {
+    if (key.startsWith("PAPERCLIP_")) {
+      delete env[key];
+    }
+  }
   delete env.DATABASE_URL;
   delete env.PORT;
   delete env.HOST;
@@ -208,25 +183,14 @@ async function api<T>(baseUrl: string, pathname: string, init?: RequestInit): Pr
   return text ? JSON.parse(text) as T : (null as T);
 }
 
-async function runCliJson<T>(
-  args: string[],
-  opts: TestPaperclipEnv & { apiBase?: string; includeConfigArg?: boolean },
-) {
+async function runCliJson<T>(args: string[], opts: { apiBase: string; configPath: string }) {
   const repoRoot = path.resolve(path.dirname(fileURLToPath(import.meta.url)), "../../..");
-  const cliArgs = ["--silent", "paperclipai", ...args];
-  if (opts.apiBase) {
-    cliArgs.push("--api-base", opts.apiBase);
-  }
-  if (opts.includeConfigArg !== false) {
-    cliArgs.push("--config", opts.configPath);
-  }
-  cliArgs.push("--json");
   const result = await execFileAsync(
     "pnpm",
-    cliArgs,
+    ["--silent", "paperclipai", ...args, "--api-base", opts.apiBase, "--config", opts.configPath, "--json"],
     {
       cwd: repoRoot,
-      env: createCliEnv(opts),
+      env: createCliEnv(),
       maxBuffer: 10 * 1024 * 1024,
     },
   );
@@ -271,9 +235,6 @@ describeEmbeddedPostgres("paperclipai company import/export e2e", () => {
   let configPath = "";
   let exportDir = "";
   let apiBase = "";
-  let paperclipHome = "";
-  let cliShellHome = "";
-  let paperclipInstanceId = "";
   let serverProcess: ServerProcess | null = null;
   let tempDb: Awaited<ReturnType<typeof startEmbeddedPostgresTestDatabase>> | null = null;
 
@@ -281,11 +242,6 @@ describeEmbeddedPostgres("paperclipai company import/export e2e", () => {
     tempRoot = mkdtempSync(path.join(os.tmpdir(), "paperclip-company-cli-e2e-"));
     configPath = path.join(tempRoot, "config", "config.json");
     exportDir = path.join(tempRoot, "exported-company");
-    paperclipHome = path.join(tempRoot, "paperclip-home");
-    cliShellHome = path.join(tempRoot, "shell-home");
-    paperclipInstanceId = "company-cli-e2e";
-    mkdirSync(paperclipHome, { recursive: true });
-    mkdirSync(cliShellHome, { recursive: true });
 
     tempDb = await startEmbeddedPostgresTestDatabase("paperclip-company-cli-db-");
 
@@ -300,11 +256,7 @@ describeEmbeddedPostgres("paperclipai company import/export e2e", () => {
       ["paperclipai", "run", "--config", configPath],
       {
         cwd: repoRoot,
-        env: createServerEnv(configPath, port, tempDb.connectionString, {
-          paperclipHome,
-          instanceId: paperclipInstanceId,
-          shellHome: cliShellHome,
-        }),
+        env: createServerEnv(configPath, port, tempDb.connectionString),
         stdio: ["ignore", "pipe", "pipe"],
       },
     );
@@ -330,41 +282,11 @@ describeEmbeddedPostgres("paperclipai company import/export e2e", () => {
   it("exports a company package and imports it into new and existing companies", async () => {
     expect(serverProcess).not.toBeNull();
 
-    const cliContext = await runCliJson<{
-      contextPath: string;
-      profileName: string;
-      profile: { apiBase?: string };
-    }>(
-      ["context", "set", "--profile", "isolation-check", "--api-base", "https://example.test"],
-      {
-        configPath,
-        paperclipHome,
-        instanceId: paperclipInstanceId,
-        shellHome: cliShellHome,
-        includeConfigArg: false,
-      },
-    );
-
-    const expectedContextPath = path.join(paperclipHome, "context.json");
-    const leakedContextPath = path.join(cliShellHome, ".paperclip", "context.json");
-    expect(cliContext.contextPath).toBe(expectedContextPath);
-    expect(cliContext.profileName).toBe("isolation-check");
-    expect(cliContext.profile.apiBase).toBe("https://example.test");
-    expect(existsSync(expectedContextPath)).toBe(true);
-    expect(existsSync(leakedContextPath)).toBe(false);
-    rmSync(expectedContextPath, { force: true });
-    expect(existsSync(expectedContextPath)).toBe(false);
-
     const sourceCompany = await api<{ id: string; name: string; issuePrefix: string }>(apiBase, "/api/companies", {
       method: "POST",
       headers: { "content-type": "application/json" },
       body: JSON.stringify({ name: `CLI Export Source ${Date.now()}` }),
     });
-    await api(apiBase, `/api/companies/${sourceCompany.id}`, {
-      method: "PATCH",
-      headers: { "content-type": "application/json" },
-      body: JSON.stringify({ requireBoardApprovalForNewAgents: false }),
-    });
 
     const sourceAgent = await api<{ id: string; name: string }>(
       apiBase,
@@ -376,11 +298,8 @@ describeEmbeddedPostgres("paperclipai company import/export e2e", () => {
           name: "Export Engineer",
           role: "engineer",
           adapterType: "claude_local",
-          adapterConfig: {},
-          instructionsBundle: {
-            files: {
-              "AGENTS.md": "You verify company portability.",
-            },
+          adapterConfig: {
+            promptTemplate: "You verify company portability.",
           },
         }),
       },
@@ -431,13 +350,7 @@ describeEmbeddedPostgres("paperclipai company import/export e2e", () => {
         "--include",
         "company,agents,projects,issues",
       ],
-      {
-        apiBase,
-        configPath,
-        paperclipHome,
-        instanceId: paperclipInstanceId,
-        shellHome: cliShellHome,
-      },
+      { apiBase, configPath },
     );
 
     expect(exportResult.ok).toBe(true);
@@ -461,13 +374,7 @@ describeEmbeddedPostgres("paperclipai company import/export e2e", () => {
         "company,agents,projects,issues",
         "--yes",
       ],
-      {
-        apiBase,
-        configPath,
-        paperclipHome,
-        instanceId: paperclipInstanceId,
-        shellHome: cliShellHome,
-      },
+      { apiBase, configPath },
     );
 
     expect(importedNew.company.action).toBe("created");
@@ -486,11 +393,10 @@ describeEmbeddedPostgres("paperclipai company import/export e2e", () => {
       apiBase,
       `/api/companies/${importedNew.company.id}/issues`,
     );
-    const importedMatchingIssues = importedIssues.filter((issue) => issue.title === sourceIssue.title);
 
     expect(importedAgents.map((agent) => agent.name)).toContain(sourceAgent.name);
     expect(importedProjects.map((project) => project.name)).toContain(sourceProject.name);
-    expect(importedMatchingIssues).toHaveLength(1);
+    expect(importedIssues.map((issue) => issue.title)).toContain(sourceIssue.title);
 
     const previewExisting = await runCliJson<{
       errors: string[];
@@ -515,13 +421,7 @@ describeEmbeddedPostgres("paperclipai company import/export e2e", () => {
         "rename",
         "--dry-run",
       ],
-      {
-        apiBase,
-        configPath,
-        paperclipHome,
-        instanceId: paperclipInstanceId,
-        shellHome: cliShellHome,
-      },
+      { apiBase, configPath },
     );
 
     expect(previewExisting.errors).toEqual([]);
@@ -548,13 +448,7 @@ describeEmbeddedPostgres("paperclipai company import/export e2e", () => {
         "rename",
         "--yes",
       ],
-      {
-        apiBase,
-        configPath,
-        paperclipHome,
-        instanceId: paperclipInstanceId,
-        shellHome: cliShellHome,
-      },
+      { apiBase, configPath },
     );
 
     expect(importedExisting.company.action).toBe("unchanged");
@@ -572,13 +466,11 @@ describeEmbeddedPostgres("paperclipai company import/export e2e", () => {
       apiBase,
       `/api/companies/${importedNew.company.id}/issues`,
     );
-    const twiceImportedMatchingIssues = twiceImportedIssues.filter((issue) => issue.title === sourceIssue.title);
 
     expect(twiceImportedAgents).toHaveLength(2);
     expect(new Set(twiceImportedAgents.map((agent) => agent.name)).size).toBe(2);
     expect(twiceImportedProjects).toHaveLength(2);
-    expect(twiceImportedMatchingIssues).toHaveLength(2);
-    expect(new Set(twiceImportedMatchingIssues.map((issue) => issue.identifier)).size).toBe(2);
+    expect(twiceImportedIssues).toHaveLength(2);
 
     const zipPath = path.join(tempRoot, "exported-company.zip");
     const portableFiles: Record<string, string> = {};
@@ -601,16 +493,10 @@ describeEmbeddedPostgres("paperclipai company import/export e2e", () => {
         "company,agents,projects,issues",
         "--yes",
       ],
-      {
-        apiBase,
-        configPath,
-        paperclipHome,
-        instanceId: paperclipInstanceId,
-        shellHome: cliShellHome,
-      },
+      { apiBase, configPath },
     );
 
     expect(importedFromZip.company.action).toBe("created");
     expect(importedFromZip.agents.some((agent) => agent.action === "created")).toBe(true);
-  }, 90_000);
+  }, 60_000);
 });

cli/src/__tests__/company.test.ts

@@ -160,7 +160,6 @@ describe("renderCompanyImportPreview", () => {
           path: "COMPANY.md",
           name: "Source Co",
           description: null,
-          attachmentMaxBytes: null,
           brandColor: null,
           logoPath: null,
           requireBoardApprovalForNewAgents: false,
@@ -244,7 +243,6 @@ describe("renderCompanyImportPreview", () => {
             billingCode: null,
             executionWorkspaceSettings: null,
             assigneeAdapterOverrides: null,
-            comments: [],
             metadata: null,
           },
         ],
@@ -377,7 +375,6 @@ describe("import selection catalog", () => {
           path: "COMPANY.md",
           name: "Source Co",
           description: null,
-          attachmentMaxBytes: null,
           brandColor: null,
           logoPath: "images/company-logo.png",
           requireBoardApprovalForNewAgents: false,
@@ -461,7 +458,6 @@ describe("import selection catalog", () => {
             billingCode: null,
             executionWorkspaceSettings: null,
             assigneeAdapterOverrides: null,
-            comments: [],
             metadata: null,
           },
         ],

cli/src/__tests__/env-lab.test.ts

@@ -1,24 +0,0 @@
-import path from "node:path";
-import { describe, expect, it } from "vitest";
-import { collectEnvLabDoctorStatus, resolveEnvLabSshStatePath } from "../commands/env-lab.js";
-
-describe("env-lab command", () => {
-  it("resolves the default SSH fixture state path under the instance root", () => {
-    const statePath = resolveEnvLabSshStatePath("fixture-test");
-
-    expect(statePath).toContain(
-      path.join("instances", "fixture-test", "env-lab", "ssh-fixture", "state.json"),
-    );
-  });
-
-  it("reports doctor status for an instance without a running fixture", async () => {
-    const status = await collectEnvLabDoctorStatus({ instance: "fixture-test-missing" });
-
-    expect(status.statePath).toContain(
-      path.join("instances", "fixture-test-missing", "env-lab", "ssh-fixture", "state.json"),
-    );
-    expect(typeof status.ssh.supported).toBe("boolean");
-    expect(status.ssh.running).toBe(false);
-    expect(status.ssh.environment).toBeNull();
-  });
-});

cli/src/__tests__/home-paths.test.ts

@@ -1,4 +1,3 @@
-import fs from "node:fs";
 import os from "node:os";
 import path from "node:path";
 import { afterEach, describe, expect, it } from "vitest";
@@ -17,14 +16,13 @@ describe("home path resolution", () => {
   });
 
   it("defaults to ~/.paperclip and default instance", () => {
-    const home = fs.mkdtempSync(path.join(os.tmpdir(), "paperclip-home-paths-"));
-    process.env.PAPERCLIP_HOME = home;
+    delete process.env.PAPERCLIP_HOME;
     delete process.env.PAPERCLIP_INSTANCE_ID;
 
     const paths = describeLocalInstancePaths();
-    expect(paths.homeDir).toBe(home);
+    expect(paths.homeDir).toBe(path.resolve(os.homedir(), ".paperclip"));
     expect(paths.instanceId).toBe("default");
-    expect(paths.configPath).toBe(path.resolve(home, "instances", "default", "config.json"));
+    expect(paths.configPath).toBe(path.resolve(os.homedir(), ".paperclip", "instances", "default", "config.json"));
   });
 
   it("supports PAPERCLIP_HOME and explicit instance ids", () => {
@@ -36,7 +34,7 @@ describe("home path resolution", () => {
   });
 
   it("rejects invalid instance ids", () => {
-    expect(() => resolvePaperclipInstanceId("bad/id")).toThrow(/Invalid PAPERCLIP_INSTANCE_ID/);
+    expect(() => resolvePaperclipInstanceId("bad/id")).toThrow(/Invalid instance id/);
   });
 
   it("expands ~ prefixes", () => {

cli/src/__tests__/network-bind.test.ts

@@ -1,69 +0,0 @@
-import { describe, expect, it } from "vitest";
-import { resolveRuntimeBind, validateConfiguredBindMode } from "@paperclipai/shared";
-import { buildPresetServerConfig } from "../config/server-bind.js";
-
-const ORIGINAL_PATH = process.env.PATH;
-
-describe("network bind helpers", () => {
-  it("rejects non-loopback bind modes in local_trusted", () => {
-    expect(
-      validateConfiguredBindMode({
-        deploymentMode: "local_trusted",
-        deploymentExposure: "private",
-        bind: "lan",
-        host: "0.0.0.0",
-      }),
-    ).toContain("local_trusted requires server.bind=loopback");
-  });
-
-  it("resolves tailnet bind using the detected tailscale address", () => {
-    const resolved = resolveRuntimeBind({
-      bind: "tailnet",
-      host: "127.0.0.1",
-      tailnetBindHost: "100.64.0.8",
-    });
-
-    expect(resolved.errors).toEqual([]);
-    expect(resolved.host).toBe("100.64.0.8");
-  });
-
-  it("requires a custom bind host when bind=custom", () => {
-    const resolved = resolveRuntimeBind({
-      bind: "custom",
-      host: "127.0.0.1",
-    });
-
-    expect(resolved.errors).toContain("server.customBindHost is required when server.bind=custom");
-  });
-
-  it("stores the detected tailscale address for tailnet presets", () => {
-    process.env.PAPERCLIP_TAILNET_BIND_HOST = "100.64.0.8";
-
-    const preset = buildPresetServerConfig("tailnet", {
-      port: 3100,
-      allowedHostnames: [],
-      serveUi: true,
-    });
-
-    expect(preset.server.host).toBe("100.64.0.8");
-
-    delete process.env.PAPERCLIP_TAILNET_BIND_HOST;
-  });
-
-  it("falls back to loopback when no tailscale address is available for tailnet presets", () => {
-    delete process.env.PAPERCLIP_TAILNET_BIND_HOST;
-    process.env.PATH = "";
-
-    try {
-      const preset = buildPresetServerConfig("tailnet", {
-        port: 3100,
-        allowedHostnames: [],
-        serveUi: true,
-      });
-
-      expect(preset.server.host).toBe("127.0.0.1");
-    } finally {
-      process.env.PATH = ORIGINAL_PATH;
-    }
-  });
-});

cli/src/__tests__/onboard.test.ts

@@ -6,8 +6,6 @@ import { onboard } from "../commands/onboard.js";
 import type { PaperclipConfig } from "../config/schema.js";
 
 const ORIGINAL_ENV = { ...process.env };
-const ORIGINAL_CWD = process.cwd();
-const ORIGINAL_PATH = process.env.PATH;
 
 function createExistingConfigFixture() {
   const root = fs.mkdtempSync(path.join(os.tmpdir(), "paperclip-onboard-"));
@@ -76,29 +74,16 @@ function createExistingConfigFixture() {
   return { configPath, configText: fs.readFileSync(configPath, "utf8") };
 }
 
-function createFreshConfigPath() {
-  const root = fs.mkdtempSync(path.join(os.tmpdir(), "paperclip-onboard-fresh-"));
-  return path.join(root, ".paperclip", "config.json");
-}
-
 describe("onboard", () => {
   beforeEach(() => {
     process.env = { ...ORIGINAL_ENV };
     delete process.env.PAPERCLIP_AGENT_JWT_SECRET;
     delete process.env.PAPERCLIP_SECRETS_MASTER_KEY;
     delete process.env.PAPERCLIP_SECRETS_MASTER_KEY_FILE;
-    delete process.env.PAPERCLIP_HOME;
-    delete process.env.PAPERCLIP_CONFIG;
-    delete process.env.PAPERCLIP_INSTANCE_ID;
-    delete process.env.PAPERCLIP_BIND;
-    delete process.env.PAPERCLIP_BIND_HOST;
-    delete process.env.PAPERCLIP_TAILNET_BIND_HOST;
-    delete process.env.HOST;
   });
 
   afterEach(() => {
     process.env = { ...ORIGINAL_ENV };
-    process.chdir(ORIGINAL_CWD);
   });
 
   it("preserves an existing config when rerun without flags", async () => {
@@ -120,83 +105,4 @@ describe("onboard", () => {
     expect(fs.existsSync(`${fixture.configPath}.backup`)).toBe(false);
     expect(fs.existsSync(path.join(path.dirname(fixture.configPath), ".env"))).toBe(true);
   });
-
-  it("keeps --yes onboarding on local trusted loopback defaults", async () => {
-    const configPath = createFreshConfigPath();
-    process.env.HOST = "0.0.0.0";
-    process.env.PAPERCLIP_BIND = "lan";
-
-    await onboard({ config: configPath, yes: true, invokedByRun: true });
-
-    const raw = JSON.parse(fs.readFileSync(configPath, "utf8")) as PaperclipConfig;
-    expect(raw.server.deploymentMode).toBe("local_trusted");
-    expect(raw.server.exposure).toBe("private");
-    expect(raw.server.bind).toBe("loopback");
-    expect(raw.server.host).toBe("127.0.0.1");
-  });
-
-  it("creates instance-root config and data paths for a fresh PAPERCLIP_HOME", async () => {
-    const home = fs.mkdtempSync(path.join(os.tmpdir(), "paperclip-onboard-home-"));
-    const cwd = fs.mkdtempSync(path.join(os.tmpdir(), "paperclip-onboard-cwd-"));
-    process.chdir(cwd);
-    process.env.PAPERCLIP_HOME = home;
-
-    await onboard({ yes: true, invokedByRun: true });
-
-    const instanceRoot = path.join(home, "instances", "default");
-    const configPath = path.join(instanceRoot, "config.json");
-    const raw = JSON.parse(fs.readFileSync(configPath, "utf8")) as PaperclipConfig;
-
-    expect(raw.database.embeddedPostgresDataDir).toBe(path.join(instanceRoot, "db"));
-    expect(raw.database.backup.dir).toBe(path.join(instanceRoot, "data", "backups"));
-    expect(raw.logging.logDir).toBe(path.join(instanceRoot, "logs"));
-    expect(raw.storage.localDisk.baseDir).toBe(path.join(instanceRoot, "data", "storage"));
-    expect(raw.secrets.localEncrypted.keyFilePath).toBe(path.join(instanceRoot, "secrets", "master.key"));
-    expect(fs.existsSync(path.join(instanceRoot, ".env"))).toBe(true);
-    expect(fs.existsSync(path.join(instanceRoot, "secrets", "master.key"))).toBe(true);
-  });
-
-  it("supports authenticated/private quickstart bind presets", async () => {
-    const configPath = createFreshConfigPath();
-    process.env.PAPERCLIP_TAILNET_BIND_HOST = "100.64.0.8";
-
-    await onboard({ config: configPath, yes: true, invokedByRun: true, bind: "tailnet" });
-
-    const raw = JSON.parse(fs.readFileSync(configPath, "utf8")) as PaperclipConfig;
-    expect(raw.server.deploymentMode).toBe("authenticated");
-    expect(raw.server.exposure).toBe("private");
-    expect(raw.server.bind).toBe("tailnet");
-    expect(raw.server.host).toBe("100.64.0.8");
-  });
-
-  it("keeps tailnet quickstart on loopback until tailscale is available", async () => {
-    const configPath = createFreshConfigPath();
-    delete process.env.PAPERCLIP_TAILNET_BIND_HOST;
-    process.env.PATH = "";
-
-    try {
-      await onboard({ config: configPath, yes: true, invokedByRun: true, bind: "tailnet" });
-    } finally {
-      process.env.PATH = ORIGINAL_PATH;
-    }
-
-    const raw = JSON.parse(fs.readFileSync(configPath, "utf8")) as PaperclipConfig;
-    expect(raw.server.deploymentMode).toBe("authenticated");
-    expect(raw.server.exposure).toBe("private");
-    expect(raw.server.bind).toBe("tailnet");
-    expect(raw.server.host).toBe("127.0.0.1");
-  });
-
-  it("ignores deployment env overrides during --yes quickstart", async () => {
-    const configPath = createFreshConfigPath();
-    process.env.PAPERCLIP_DEPLOYMENT_MODE = "authenticated";
-
-    await onboard({ config: configPath, yes: true, invokedByRun: true });
-
-    const raw = JSON.parse(fs.readFileSync(configPath, "utf8")) as PaperclipConfig;
-    expect(raw.server.deploymentMode).toBe("local_trusted");
-    expect(raw.server.exposure).toBe("private");
-    expect(raw.server.bind).toBe("loopback");
-    expect(raw.server.host).toBe("127.0.0.1");
-  });
 });

cli/src/__tests__/plugin-init.test.ts

@@ -1,164 +0,0 @@
-import fs from "node:fs";
-import os from "node:os";
-import path from "node:path";
-import { Command } from "commander";
-import { afterEach, beforeEach, describe, expect, it, vi } from "vitest";
-
-const mocks = vi.hoisted(() => ({
-  scaffoldPluginProject: vi.fn((options: { outputDir: string }) => options.outputDir),
-}));
-
-vi.mock("../../../packages/plugins/create-paperclip-plugin/src/index.js", async () => {
-  const actual =
-    await vi.importActual<typeof import("../../../packages/plugins/create-paperclip-plugin/src/index.js")>(
-      "../../../packages/plugins/create-paperclip-plugin/src/index.js",
-    );
-  return {
-    ...actual,
-    scaffoldPluginProject: mocks.scaffoldPluginProject,
-  };
-});
-
-import {
-  buildPluginInstallRequest,
-  buildPluginInitNextCommands,
-  buildPluginInitScaffoldOptions,
-  registerPluginCommands,
-} from "../commands/client/plugin.js";
-
-const tempDirs: string[] = [];
-
-function makeTempDir(): string {
-  const dir = fs.mkdtempSync(path.join(os.tmpdir(), "paperclip-cli-plugin-"));
-  tempDirs.push(dir);
-  return dir;
-}
-
-afterEach(() => {
-  while (tempDirs.length > 0) {
-    const dir = tempDirs.pop();
-    if (dir) fs.rmSync(dir, { recursive: true, force: true });
-  }
-});
-
-describe("plugin init", () => {
-  beforeEach(() => {
-    mocks.scaffoldPluginProject.mockClear();
-  });
-
-  it("maps package name and flags to scaffolder options", () => {
-    const cwd = path.resolve("/tmp/paperclip-cli-test");
-    const options = buildPluginInitScaffoldOptions(
-      "@acme/plugin-linear",
-      {
-        output: "plugins",
-        template: "connector",
-        category: "automation",
-        displayName: "Linear Bridge",
-        description: "Syncs Linear issues",
-        author: "Acme",
-        sdkPath: "../paperclip/packages/plugins/sdk",
-      },
-      cwd,
-    );
-
-    expect(options).toEqual({
-      pluginName: "@acme/plugin-linear",
-      outputDir: path.resolve(cwd, "plugins", "plugin-linear"),
-      template: "connector",
-      category: "automation",
-      displayName: "Linear Bridge",
-      description: "Syncs Linear issues",
-      author: "Acme",
-      sdkPath: "../paperclip/packages/plugins/sdk",
-    });
-  });
-
-  it("builds exact next commands using the scaffold path", () => {
-    expect(buildPluginInitNextCommands("/tmp/acme plugin")).toEqual([
-      "cd '/tmp/acme plugin'",
-      "pnpm install",
-      "pnpm dev",
-      "paperclipai plugin install '/tmp/acme plugin'",
-    ]);
-  });
-
-  it("registers the CLI wrapper and invokes the existing scaffolder", async () => {
-    const program = new Command();
-    program.exitOverride();
-    program.configureOutput({ writeOut: () => {}, writeErr: () => {} });
-    registerPluginCommands(program);
-
-    await program.parseAsync(
-      [
-        "plugin",
-        "init",
-        "demo-plugin",
-        "--output",
-        "/tmp/paperclip-init-output",
-        "--template",
-        "workspace",
-        "--category",
-        "workspace",
-        "--display-name",
-        "Demo Plugin",
-        "--description",
-        "Demo description",
-        "--author",
-        "Paperclip",
-        "--sdk-path",
-        "/repo/packages/plugins/sdk",
-      ],
-      { from: "user" },
-    );
-
-    expect(mocks.scaffoldPluginProject).toHaveBeenCalledTimes(1);
-    expect(mocks.scaffoldPluginProject).toHaveBeenCalledWith({
-      pluginName: "demo-plugin",
-      outputDir: path.resolve("/tmp/paperclip-init-output", "demo-plugin"),
-      template: "workspace",
-      category: "workspace",
-      displayName: "Demo Plugin",
-      description: "Demo description",
-      author: "Paperclip",
-      sdkPath: "/repo/packages/plugins/sdk",
-    });
-  });
-});
-
-describe("plugin install", () => {
-  it("resolves an existing relative local path to an absolute local install request", () => {
-    const cwd = makeTempDir();
-    const pluginDir = path.join(cwd, "demo-plugin");
-    fs.mkdirSync(pluginDir);
-
-    expect(buildPluginInstallRequest("demo-plugin", {}, { cwd })).toEqual({
-      packageName: pluginDir,
-      version: undefined,
-      isLocalPath: true,
-    });
-  });
-
-  it("keeps an absolute local path absolute and marks it as local", () => {
-    const pluginDir = path.join(makeTempDir(), "demo-plugin");
-    fs.mkdirSync(pluginDir);
-
-    expect(buildPluginInstallRequest(pluginDir, {}, { cwd: "/" })).toEqual({
-      packageName: pluginDir,
-      version: undefined,
-      isLocalPath: true,
-    });
-  });
-
-  it("preserves npm package installs when no local path exists", () => {
-    expect(
-      buildPluginInstallRequest("@acme/plugin-linear", { version: "1.2.3" }, {
-        cwd: makeTempDir(),
-      }),
-    ).toEqual({
-      packageName: "@acme/plugin-linear",
-      version: "1.2.3",
-      isLocalPath: false,
-    });
-  });
-});

cli/src/__tests__/secrets.test.ts

@@ -1,257 +0,0 @@
-import { afterEach, beforeEach, describe, expect, it } from "vitest";
-import type { Agent, CompanySecret } from "@paperclipai/shared";
-import type { PaperclipConfig } from "../config/schema.js";
-import { secretsCheck } from "../checks/secrets-check.js";
-import {
-  buildInlineMigrationSecretName,
-  buildMigratedAgentEnv,
-  collectInlineSecretMigrationCandidates,
-  parseSecretsInclude,
-  toPlainEnvValue,
-} from "../commands/client/secrets.js";
-
-function agent(partial: Partial<Agent>): Agent {
-  return {
-    id: "agent-12345678",
-    companyId: "company-1",
-    name: "Coder",
-    urlKey: "coder",
-    role: "engineer",
-    title: null,
-    icon: null,
-    status: "idle",
-    reportsTo: null,
-    capabilities: null,
-    adapterType: "codex_local",
-    adapterConfig: {},
-    runtimeConfig: {},
-    budgetMonthlyCents: 0,
-    spentMonthlyCents: 0,
-    pauseReason: null,
-    pausedAt: null,
-    permissions: {
-      canCreateAgents: false,
-    },
-    lastHeartbeatAt: null,
-    metadata: null,
-    createdAt: new Date("2026-04-26T00:00:00.000Z"),
-    updatedAt: new Date("2026-04-26T00:00:00.000Z"),
-    ...partial,
-  };
-}
-
-function secret(partial: Partial<CompanySecret>): CompanySecret {
-  return {
-    id: "secret-1",
-    companyId: "company-1",
-    key: "agent_agent-12_anthropic_api_key",
-    name: "agent_agent-12_anthropic_api_key",
-    provider: "local_encrypted",
-    status: "active",
-    managedMode: "paperclip_managed",
-    externalRef: null,
-    providerConfigId: null,
-    providerMetadata: null,
-    latestVersion: 1,
-    description: null,
-    lastResolvedAt: null,
-    lastRotatedAt: null,
-    deletedAt: null,
-    createdByAgentId: null,
-    createdByUserId: null,
-    createdAt: new Date("2026-04-26T00:00:00.000Z"),
-    updatedAt: new Date("2026-04-26T00:00:00.000Z"),
-    ...partial,
-  };
-}
-
-function configWithSecretsProvider(provider: PaperclipConfig["secrets"]["provider"]): PaperclipConfig {
-  return {
-    $meta: {
-      version: 1,
-      updatedAt: "2026-05-02T00:00:00.000Z",
-      source: "configure",
-    },
-    database: {
-      mode: "embedded-postgres",
-      embeddedPostgresDataDir: "/tmp/paperclip/db",
-      embeddedPostgresPort: 55432,
-      backup: {
-        enabled: true,
-        intervalMinutes: 60,
-        retentionDays: 30,
-        dir: "/tmp/paperclip/backups",
-      },
-    },
-    logging: {
-      mode: "file",
-      logDir: "/tmp/paperclip/logs",
-    },
-    server: {
-      deploymentMode: "local_trusted",
-      exposure: "private",
-      host: "127.0.0.1",
-      port: 3100,
-      allowedHostnames: [],
-      serveUi: true,
-    },
-    auth: {
-      baseUrlMode: "auto",
-      disableSignUp: false,
-    },
-    telemetry: {
-      enabled: true,
-    },
-    storage: {
-      provider: "local_disk",
-      localDisk: {
-        baseDir: "/tmp/paperclip/storage",
-      },
-      s3: {
-        bucket: "paperclip",
-        region: "us-east-1",
-        prefix: "",
-        forcePathStyle: false,
-      },
-    },
-    secrets: {
-      provider,
-      strictMode: true,
-      localEncrypted: {
-        keyFilePath: "/tmp/paperclip/secrets/master.key",
-      },
-    },
-  };
-}
-
-describe("secrets CLI helpers", () => {
-  const originalEnv = { ...process.env };
-
-  beforeEach(() => {
-    process.env = { ...originalEnv };
-    delete process.env.PAPERCLIP_SECRETS_AWS_REGION;
-    delete process.env.AWS_REGION;
-    delete process.env.AWS_DEFAULT_REGION;
-    delete process.env.PAPERCLIP_SECRETS_AWS_DEPLOYMENT_ID;
-    delete process.env.PAPERCLIP_SECRETS_AWS_KMS_KEY_ID;
-  });
-
-  afterEach(() => {
-    process.env = { ...originalEnv };
-  });
-
-  it("parses declaration include filters", () => {
-    expect(parseSecretsInclude("agents,projects,tasks")).toEqual({
-      company: false,
-      agents: true,
-      projects: true,
-      issues: true,
-      skills: false,
-    });
-  });
-
-  it("detects inline sensitive env values that need migration", () => {
-    const rows = collectInlineSecretMigrationCandidates(
-      [
-        agent({
-          id: "agent-12345678",
-          adapterConfig: {
-            env: {
-              ANTHROPIC_API_KEY: "sk-ant-test",
-              GH_TOKEN: {
-                type: "plain",
-                value: "ghp-test",
-              },
-              PATH: {
-                type: "plain",
-                value: "/usr/bin",
-              },
-              OPENAI_API_KEY: {
-                type: "secret_ref",
-                secretId: "secret-existing",
-              },
-            },
-          },
-        }),
-      ],
-      [
-        secret({
-          id: "secret-gh-token",
-          name: buildInlineMigrationSecretName("agent-12345678", "GH_TOKEN"),
-        }),
-      ],
-    );
-
-    expect(rows).toEqual([
-      {
-        agentId: "agent-12345678",
-        agentName: "Coder",
-        envKey: "ANTHROPIC_API_KEY",
-        secretName: "agent_agent-12_anthropic_api_key",
-        existingSecretId: null,
-      },
-      {
-        agentId: "agent-12345678",
-        agentName: "Coder",
-        envKey: "GH_TOKEN",
-        secretName: "agent_agent-12_gh_token",
-        existingSecretId: "secret-gh-token",
-      },
-    ]);
-  });
-
-  it("builds migrated env bindings without preserving secret values", () => {
-    const next = buildMigratedAgentEnv(
-      {
-        ANTHROPIC_API_KEY: "sk-ant-test",
-        NODE_ENV: {
-          type: "plain",
-          value: "development",
-        },
-      },
-      new Map([["ANTHROPIC_API_KEY", "secret-1"]]),
-    );
-
-    expect(next).toEqual({
-      ANTHROPIC_API_KEY: {
-        type: "secret_ref",
-        secretId: "secret-1",
-        version: "latest",
-      },
-      NODE_ENV: {
-        type: "plain",
-        value: "development",
-      },
-    });
-    expect(JSON.stringify(next)).not.toContain("sk-ant-test");
-  });
-
-  it("reads only explicit plain env values", () => {
-    expect(toPlainEnvValue("plain-value")).toBe("plain-value");
-    expect(toPlainEnvValue({ type: "plain", value: "wrapped" })).toBe("wrapped");
-    expect(toPlainEnvValue({ type: "secret_ref", secretId: "secret-1" })).toBeNull();
-  });
-
-  it("reports the AWS bootstrap config required by doctor", () => {
-    const result = secretsCheck(configWithSecretsProvider("aws_secrets_manager"));
-
-    expect(result.status).toBe("fail");
-    expect(result.message).toContain("PAPERCLIP_SECRETS_AWS_DEPLOYMENT_ID");
-    expect(result.repairHint).toContain("AWS SDK default credential chain");
-    expect(result.repairHint).toContain("Do not store AWS root credentials");
-  });
-
-  it("passes AWS doctor checks when non-secret provider config is present", () => {
-    process.env.PAPERCLIP_SECRETS_AWS_REGION = "us-east-1";
-    process.env.PAPERCLIP_SECRETS_AWS_DEPLOYMENT_ID = "prod-us-1";
-    process.env.PAPERCLIP_SECRETS_AWS_KMS_KEY_ID =
-      "arn:aws:kms:us-east-1:123456789012:key/test";
-    process.env.AWS_PROFILE = "paperclip-prod";
-
-    const result = secretsCheck(configWithSecretsProvider("aws_secrets_manager"));
-
-    expect(result.status).toBe("pass");
-    expect(result.message).toContain("prod-us-1");
-    expect(result.message).toContain("AWS_PROFILE/shared config");
-  });
-});

cli/src/__tests__/skills.test.ts

@@ -1,506 +0,0 @@
-import { Command } from "commander";
-import { afterEach, beforeEach, describe, expect, it, vi } from "vitest";
-import { registerSkillsCommands } from "../commands/client/skills.js";
-import { resolveCompanySkillReference } from "../commands/client/skills.js";
-
-const ORIGINAL_ENV = { ...process.env };
-
-function makeProgram(): Command {
-  const program = new Command();
-  program.exitOverride();
-  program.configureOutput({
-    writeOut: () => undefined,
-    writeErr: () => undefined,
-  });
-  registerSkillsCommands(program);
-  return program;
-}
-
-async function runCommand(args: string[]): Promise<void> {
-  await makeProgram().parseAsync(args, { from: "user" });
-}
-
-function jsonResponse(body: unknown, status = 200): Response {
-  return new Response(JSON.stringify(body), {
-    status,
-    headers: { "content-type": "application/json" },
-  });
-}
-
-function skill(overrides: Record<string, unknown> = {}) {
-  return {
-    id: "11111111-1111-1111-1111-111111111111",
-    companyId: "company-1",
-    key: "paperclip/review-prs",
-    slug: "review-prs",
-    name: "Review PRs",
-    description: "Review pull requests",
-    markdown: "# Review PRs",
-    sourceType: "local_path",
-    sourceLocator: null,
-    sourceRef: null,
-    trustLevel: "markdown_only",
-    compatibility: "compatible",
-    fileInventory: [{ path: "SKILL.md", kind: "skill" }],
-    metadata: null,
-    createdAt: "2026-05-26T00:00:00.000Z",
-    updatedAt: "2026-05-26T00:00:00.000Z",
-    attachedAgentCount: 2,
-    editable: true,
-    editableReason: null,
-    sourceLabel: null,
-    sourceBadge: "local",
-    sourcePath: null,
-    ...overrides,
-  };
-}
-
-function catalogSkill(overrides: Record<string, unknown> = {}) {
-  return {
-    id: "paperclipai:bundled:software-development:github-pr-workflow",
-    key: "paperclipai/bundled/software-development/github-pr-workflow",
-    kind: "bundled",
-    category: "software-development",
-    slug: "github-pr-workflow",
-    name: "github-pr-workflow",
-    description: "Prepare pull requests, review responses, and verification notes.",
-    path: "catalog/bundled/software-development/github-pr-workflow",
-    entrypoint: "SKILL.md",
-    trustLevel: "markdown_only",
-    compatibility: "compatible",
-    defaultInstall: false,
-    recommendedForRoles: ["engineer"],
-    requires: [],
-    tags: ["github", "pull-requests"],
-    files: [{ path: "SKILL.md", kind: "skill", sizeBytes: 128, sha256: "sha256:abc" }],
-    contentHash: "sha256:catalog",
-    ...overrides,
-  };
-}
-
-function agent(overrides: Record<string, unknown> = {}) {
-  return {
-    id: "agent-1",
-    companyId: "company-1",
-    name: "Coder",
-    role: "engineer",
-    status: "active",
-    reportsTo: null,
-    budgetMonthlyCents: 0,
-    spentMonthlyCents: 0,
-    adapterType: "codex_local",
-    adapterConfig: {},
-    runtimeConfig: {},
-    permissions: {},
-    createdAt: "2026-05-26T00:00:00.000Z",
-    updatedAt: "2026-05-26T00:00:00.000Z",
-    ...overrides,
-  };
-}
-
-describe("skills CLI helpers", () => {
-  it("resolves skill refs by id, key, or unique normalized slug", () => {
-    const rows = [
-      skill({ id: "skill-a", key: "paperclip/a", slug: "alpha", name: "Alpha" }),
-      skill({ id: "skill-b", key: "paperclip/b", slug: "beta-skill", name: "Beta" }),
-    ];
-
-    expect(resolveCompanySkillReference(rows, "skill-a").key).toBe("paperclip/a");
-    expect(resolveCompanySkillReference(rows, "paperclip/b").id).toBe("skill-b");
-    expect(resolveCompanySkillReference(rows, "Beta Skill").id).toBe("skill-b");
-  });
-
-  it("rejects ambiguous slug refs", () => {
-    const rows = [
-      skill({ id: "skill-a", key: "paperclip/a", slug: "same", name: "A" }),
-      skill({ id: "skill-b", key: "paperclip/b", slug: "same", name: "B" }),
-    ];
-
-    expect(() => resolveCompanySkillReference(rows, "same")).toThrow(/Ambiguous skill slug/);
-  });
-});
-
-describe("skills CLI commands", () => {
-  let fetchMock: ReturnType<typeof vi.fn>;
-  let logSpy: ReturnType<typeof vi.spyOn>;
-  let writeChunks: unknown[];
-
-  beforeEach(() => {
-    process.env = { ...ORIGINAL_ENV };
-    delete process.env.PAPERCLIP_API_URL;
-    delete process.env.PAPERCLIP_API_KEY;
-    delete process.env.PAPERCLIP_COMPANY_ID;
-    fetchMock = vi.fn();
-    vi.stubGlobal("fetch", fetchMock);
-    logSpy = vi.spyOn(console, "log").mockImplementation(() => undefined);
-    writeChunks = [];
-    vi.spyOn(process.stdout, "write").mockImplementation((chunk: string | Uint8Array) => {
-      writeChunks.push(chunk);
-      return true;
-    });
-  });
-
-  afterEach(() => {
-    process.env = { ...ORIGINAL_ENV };
-    vi.unstubAllGlobals();
-    vi.restoreAllMocks();
-  });
-
-  it("lists company skills as JSON through the shared client context", async () => {
-    const rows = [skill()];
-    fetchMock.mockResolvedValueOnce(jsonResponse(rows));
-
-    await runCommand([
-      "skills",
-      "list",
-      "--company-id",
-      "company-1",
-      "--api-base",
-      "http://paperclip.test",
-      "--api-key",
-      "token",
-      "--json",
-    ]);
-
-    expect(fetchMock).toHaveBeenCalledWith(
-      "http://paperclip.test/api/companies/company-1/skills",
-      expect.objectContaining({
-        method: "GET",
-        headers: expect.objectContaining({ authorization: "Bearer token" }),
-      }),
-    );
-    expect(JSON.parse(String(logSpy.mock.calls[0]?.[0]))).toEqual(rows);
-  });
-
-  it("resolves a skill slug before reading detail", async () => {
-    fetchMock
-      .mockResolvedValueOnce(jsonResponse([skill()]))
-      .mockResolvedValueOnce(jsonResponse({ ...skill(), usedByAgents: [] }));
-
-    await runCommand([
-      "skills",
-      "show",
-      "Review PRs",
-      "--company-id",
-      "company-1",
-      "--api-base",
-      "http://paperclip.test",
-      "--api-key",
-      "token",
-      "--json",
-    ]);
-
-    expect(fetchMock).toHaveBeenNthCalledWith(
-      2,
-      "http://paperclip.test/api/companies/company-1/skills/11111111-1111-1111-1111-111111111111",
-      expect.objectContaining({ method: "GET" }),
-    );
-  });
-
-  it("prints skill files as raw pipeable content in human mode", async () => {
-    fetchMock
-      .mockResolvedValueOnce(jsonResponse([skill()]))
-      .mockResolvedValueOnce(jsonResponse({
-        skillId: "11111111-1111-1111-1111-111111111111",
-        path: "SKILL.md",
-        kind: "skill",
-        content: "# Review PRs",
-        language: "markdown",
-        markdown: true,
-        editable: true,
-      }));
-
-    await runCommand([
-      "skills",
-      "file",
-      "review-prs",
-      "--company-id",
-      "company-1",
-      "--api-base",
-      "http://paperclip.test",
-      "--api-key",
-      "token",
-    ]);
-
-    expect(logSpy).not.toHaveBeenCalled();
-    expect(writeChunks.join("")).toBe("# Review PRs\n");
-  });
-
-  it("browses catalog skills with filters in table output", async () => {
-    fetchMock.mockResolvedValueOnce(jsonResponse([catalogSkill()]));
-
-    await runCommand([
-      "skills",
-      "browse",
-      "--kind",
-      "bundled",
-      "--category",
-      "software-development",
-      "--query",
-      "github",
-      "--api-base",
-      "http://paperclip.test",
-      "--api-key",
-      "token",
-    ]);
-
-    expect(fetchMock).toHaveBeenCalledWith(
-      "http://paperclip.test/api/skills/catalog?kind=bundled&category=software-development&q=github",
-      expect.objectContaining({ method: "GET" }),
-    );
-    const rendered = logSpy.mock.calls.map((call) => String(call[0])).join("\n");
-    expect(rendered).toContain("id");
-    expect(rendered).toContain("paperclipai:bundled:software-development:github-pr-workflow");
-    expect(rendered).toContain("roles");
-  });
-
-  it("searches catalog skills as JSON", async () => {
-    const rows = [catalogSkill()];
-    fetchMock.mockResolvedValueOnce(jsonResponse(rows));
-
-    await runCommand([
-      "skills",
-      "search",
-      "pull requests",
-      "--kind",
-      "bundled",
-      "--api-base",
-      "http://paperclip.test",
-      "--api-key",
-      "token",
-      "--json",
-    ]);
-
-    expect(fetchMock).toHaveBeenCalledWith(
-      "http://paperclip.test/api/skills/catalog?kind=bundled&q=pull+requests",
-      expect.objectContaining({ method: "GET" }),
-    );
-    expect(JSON.parse(String(logSpy.mock.calls[0]?.[0]))).toEqual(rows);
-  });
-
-  it("inspects catalog skill detail by query ref so keys with slashes work", async () => {
-    const detail = catalogSkill();
-    fetchMock.mockResolvedValueOnce(jsonResponse(detail));
-
-    await runCommand([
-      "skills",
-      "inspect",
-      "paperclipai/bundled/software-development/github-pr-workflow",
-      "--api-base",
-      "http://paperclip.test",
-      "--api-key",
-      "token",
-      "--json",
-    ]);
-
-    expect(fetchMock).toHaveBeenCalledWith(
-      "http://paperclip.test/api/skills/catalog/ref?ref=paperclipai%2Fbundled%2Fsoftware-development%2Fgithub-pr-workflow",
-      expect.objectContaining({ method: "GET" }),
-    );
-    expect(JSON.parse(String(logSpy.mock.calls[0]?.[0]))).toEqual(detail);
-  });
-
-  it("installs catalog skills into the company library without agent sync", async () => {
-    const result = {
-      action: "created",
-      skill: skill({
-        key: "paperclipai/bundled/software-development/github-pr-workflow",
-        slug: "pr-flow",
-        sourceType: "catalog",
-      }),
-      catalogSkill: catalogSkill(),
-      warnings: [],
-    };
-    fetchMock.mockResolvedValueOnce(jsonResponse(result, 201));
-
-    await runCommand([
-      "skills",
-      "install",
-      "github-pr-workflow",
-      "--as",
-      "pr-flow",
-      "--force",
-      "--company-id",
-      "company-1",
-      "--api-base",
-      "http://paperclip.test",
-      "--api-key",
-      "token",
-      "--json",
-    ]);
-
-    expect(fetchMock).toHaveBeenCalledWith(
-      "http://paperclip.test/api/companies/company-1/skills/install-catalog",
-      expect.objectContaining({
-        method: "POST",
-        body: JSON.stringify({
-          catalogSkillId: "github-pr-workflow",
-          slug: "pr-flow",
-          force: true,
-        }),
-      }),
-    );
-    expect(JSON.parse(String(logSpy.mock.calls[0]?.[0]))).toEqual(result);
-  });
-
-  it("passes force to skill updates", async () => {
-    fetchMock
-      .mockResolvedValueOnce(jsonResponse([skill()]))
-      .mockResolvedValueOnce(jsonResponse(skill({ sourceRef: "sha256:new" })));
-
-    await runCommand([
-      "skills",
-      "update",
-      "review-prs",
-      "--force",
-      "--company-id",
-      "company-1",
-      "--api-base",
-      "http://paperclip.test",
-      "--api-key",
-      "token",
-      "--json",
-    ]);
-
-    expect(fetchMock).toHaveBeenNthCalledWith(
-      2,
-      "http://paperclip.test/api/companies/company-1/skills/11111111-1111-1111-1111-111111111111/install-update",
-      expect.objectContaining({
-        method: "POST",
-        body: JSON.stringify({ force: true }),
-      }),
-    );
-  });
-
-  it("audits installed skill bytes through the server", async () => {
-    const audit = {
-      skillId: "11111111-1111-1111-1111-111111111111",
-      installedHash: "sha256:installed",
-      originHash: "sha256:origin",
-      verdict: "warning",
-      codes: ["network_reference"],
-      findings: [{
-        code: "network_reference",
-        severity: "warning",
-        message: "Skill content references network-capable commands or URLs.",
-        path: "SKILL.md",
-      }],
-      scannedAt: "2026-05-26T00:00:00.000Z",
-      scanVersion: "skills-audit-v1",
-    };
-    fetchMock
-      .mockResolvedValueOnce(jsonResponse([skill()]))
-      .mockResolvedValueOnce(jsonResponse(audit));
-
-    await runCommand([
-      "skills",
-      "audit",
-      "review-prs",
-      "--company-id",
-      "company-1",
-      "--api-base",
-      "http://paperclip.test",
-      "--api-key",
-      "token",
-      "--json",
-    ]);
-
-    expect(fetchMock).toHaveBeenNthCalledWith(
-      2,
-      "http://paperclip.test/api/companies/company-1/skills/11111111-1111-1111-1111-111111111111/audit",
-      expect.objectContaining({
-        method: "POST",
-        body: JSON.stringify({}),
-      }),
-    );
-    expect(JSON.parse(String(logSpy.mock.calls[0]?.[0]))).toEqual(audit);
-  });
-
-  it("requires confirmation for reset and sends force when confirmed", async () => {
-    fetchMock
-      .mockResolvedValueOnce(jsonResponse([skill({ sourceType: "catalog" })]))
-      .mockResolvedValueOnce(jsonResponse(skill({ sourceType: "catalog" })));
-
-    await runCommand([
-      "skills",
-      "reset",
-      "review-prs",
-      "--yes",
-      "--force",
-      "--company-id",
-      "company-1",
-      "--api-base",
-      "http://paperclip.test",
-      "--api-key",
-      "token",
-      "--json",
-    ]);
-
-    expect(fetchMock).toHaveBeenNthCalledWith(
-      2,
-      "http://paperclip.test/api/companies/company-1/skills/11111111-1111-1111-1111-111111111111/reset",
-      expect.objectContaining({
-        method: "POST",
-        body: JSON.stringify({ force: true }),
-      }),
-    );
-  });
-
-  it("syncs desired company skill refs to an agent and returns the runtime snapshot", async () => {
-    const snapshot = {
-      adapterType: "codex_local",
-      supported: true,
-      mode: "persistent",
-      desiredSkills: ["paperclip/review-prs"],
-      entries: [
-        {
-          key: "paperclip/review-prs",
-          runtimeName: "review-prs",
-          desired: true,
-          managed: true,
-          required: false,
-          state: "installed",
-          origin: "company_managed",
-          detail: null,
-        },
-      ],
-      warnings: [],
-    };
-    fetchMock
-      .mockResolvedValueOnce(jsonResponse(agent()))
-      .mockResolvedValueOnce(jsonResponse(snapshot));
-
-    await runCommand([
-      "skills",
-      "agent",
-      "sync",
-      "coder",
-      "--skill",
-      "review-prs",
-      "--skill",
-      "paperclip/qa",
-      "--company-id",
-      "company-1",
-      "--api-base",
-      "http://paperclip.test",
-      "--api-key",
-      "token",
-      "--json",
-    ]);
-
-    expect(fetchMock).toHaveBeenNthCalledWith(
-      1,
-      "http://paperclip.test/api/agents/coder?companyId=company-1",
-      expect.objectContaining({ method: "GET" }),
-    );
-    expect(fetchMock).toHaveBeenNthCalledWith(
-      2,
-      "http://paperclip.test/api/agents/agent-1/skills/sync",
-      expect.objectContaining({
-        method: "POST",
-        body: JSON.stringify({ desiredSkills: ["review-prs", "paperclip/qa"] }),
-      }),
-    );
-    expect(JSON.parse(String(logSpy.mock.calls[0]?.[0]))).toEqual(snapshot);
-  });
-});

cli/src/__tests__/worktree.test.ts

@@ -2,25 +2,10 @@ import fs from "node:fs";
 import os from "node:os";
 import path from "node:path";
 import { execFileSync } from "node:child_process";
-import { randomUUID } from "node:crypto";
-import { eq } from "drizzle-orm";
 import { afterEach, describe, expect, it, vi } from "vitest";
-import {
-  agents,
-  authUsers,
-  companies,
-  createDb,
-  issueComments,
-  issues,
-  projects,
-  routines,
-  routineTriggers,
-} from "@paperclipai/db";
 import {
   copyGitHooksToWorktreeGitDir,
   copySeededSecretsKey,
-  pauseSeededScheduledRoutines,
-  quarantineSeededWorktreeExecutionState,
   readSourceAttachmentBody,
   rebindWorkspaceCwd,
   resolveSourceConfigPath,
@@ -28,7 +13,6 @@ import {
   resolveWorktreeReseedTargetPaths,
   resolveGitWorktreeAddArgs,
   resolveWorktreeMakeTargetPath,
-  worktreeRepairCommand,
   worktreeInitCommand,
   worktreeMakeCommand,
   worktreeReseedCommand,
@@ -44,22 +28,9 @@ import {
   sanitizeWorktreeInstanceId,
 } from "../commands/worktree-lib.js";
 import type { PaperclipConfig } from "../config/schema.js";
-import {
-  getEmbeddedPostgresTestSupport,
-  startEmbeddedPostgresTestDatabase,
-} from "./helpers/embedded-postgres.js";
 
 const ORIGINAL_CWD = process.cwd();
 const ORIGINAL_ENV = { ...process.env };
-const embeddedPostgresSupport = await getEmbeddedPostgresTestSupport();
-const itEmbeddedPostgres = embeddedPostgresSupport.supported ? it : it.skip;
-const describeEmbeddedPostgres = embeddedPostgresSupport.supported ? describe : describe.skip;
-
-if (!embeddedPostgresSupport.supported) {
-  console.warn(
-    `Skipping embedded Postgres worktree CLI tests on this host: ${embeddedPostgresSupport.reason ?? "unsupported environment"}`,
-  );
-}
 
 afterEach(() => {
   process.chdir(ORIGINAL_CWD);
@@ -190,9 +161,8 @@ describe("worktree helpers", () => {
     ).toEqual(["worktree", "add", "-b", "my-worktree", "/tmp/my-worktree", "origin/main"]);
   });
 
-  it("rewrites auth URLs only when they already include a port", () => {
+  it("rewrites loopback auth URLs to the new port only", () => {
     expect(rewriteLocalUrlPort("http://127.0.0.1:3100", 3110)).toBe("http://127.0.0.1:3110/");
-    expect(rewriteLocalUrlPort("http://my-host.ts.net:3100", 3110)).toBe("http://my-host.ts.net:3110/");
     expect(rewriteLocalUrlPort("https://paperclip.example", 3110)).toBe("https://paperclip.example");
   });
 
@@ -287,138 +257,6 @@ describe("worktree helpers", () => {
     expect(full.nullifyColumns).toEqual({});
   });
 
-  itEmbeddedPostgres("quarantines copied live execution state in seeded worktree databases", async () => {
-    const tempDb = await startEmbeddedPostgresTestDatabase("paperclip-worktree-quarantine-");
-    const db = createDb(tempDb.connectionString);
-    const companyId = randomUUID();
-    const agentId = randomUUID();
-    const idleAgentId = randomUUID();
-    const inProgressIssueId = randomUUID();
-    const todoIssueId = randomUUID();
-    const reviewIssueId = randomUUID();
-    const userIssueId = randomUUID();
-
-    try {
-      await db.insert(companies).values({
-        id: companyId,
-        name: "Paperclip",
-        issuePrefix: "WTQ",
-        requireBoardApprovalForNewAgents: false,
-      });
-      await db.insert(agents).values([
-        {
-          id: agentId,
-          companyId,
-          name: "CodexCoder",
-          role: "engineer",
-          status: "running",
-          adapterType: "codex_local",
-          adapterConfig: {},
-          runtimeConfig: {
-            heartbeat: { enabled: true, intervalSec: 60 },
-            wakeOnDemand: true,
-          },
-          permissions: {},
-        },
-        {
-          id: idleAgentId,
-          companyId,
-          name: "Reviewer",
-          role: "reviewer",
-          status: "idle",
-          adapterType: "codex_local",
-          adapterConfig: {},
-          runtimeConfig: { heartbeat: { enabled: false, intervalSec: 300 } },
-          permissions: {},
-        },
-      ]);
-      await db.insert(issues).values([
-        {
-          id: inProgressIssueId,
-          companyId,
-          title: "Copied in-flight issue",
-          status: "in_progress",
-          priority: "medium",
-          assigneeAgentId: agentId,
-          issueNumber: 1,
-          identifier: "WTQ-1",
-          executionAgentNameKey: "codexcoder",
-          executionLockedAt: new Date("2026-04-18T00:00:00.000Z"),
-        },
-        {
-          id: todoIssueId,
-          companyId,
-          title: "Copied assigned todo issue",
-          status: "todo",
-          priority: "medium",
-          assigneeAgentId: agentId,
-          issueNumber: 2,
-          identifier: "WTQ-2",
-        },
-        {
-          id: reviewIssueId,
-          companyId,
-          title: "Copied assigned review issue",
-          status: "in_review",
-          priority: "medium",
-          assigneeAgentId: idleAgentId,
-          issueNumber: 3,
-          identifier: "WTQ-3",
-        },
-        {
-          id: userIssueId,
-          companyId,
-          title: "Copied user issue",
-          status: "todo",
-          priority: "medium",
-          assigneeUserId: "user-1",
-          issueNumber: 4,
-          identifier: "WTQ-4",
-        },
-      ]);
-
-      await expect(quarantineSeededWorktreeExecutionState(tempDb.connectionString)).resolves.toEqual({
-        disabledTimerHeartbeats: 1,
-        resetRunningAgents: 1,
-        quarantinedInProgressIssues: 1,
-        unassignedTodoIssues: 1,
-        unassignedReviewIssues: 1,
-      });
-
-      const [quarantinedAgent] = await db.select().from(agents).where(eq(agents.id, agentId));
-      expect(quarantinedAgent?.status).toBe("idle");
-      expect(quarantinedAgent?.runtimeConfig).toMatchObject({
-        heartbeat: { enabled: false, intervalSec: 60 },
-        wakeOnDemand: true,
-      });
-
-      const [inProgressIssue] = await db.select().from(issues).where(eq(issues.id, inProgressIssueId));
-      expect(inProgressIssue?.status).toBe("blocked");
-      expect(inProgressIssue?.assigneeAgentId).toBeNull();
-      expect(inProgressIssue?.executionAgentNameKey).toBeNull();
-      expect(inProgressIssue?.executionLockedAt).toBeNull();
-
-      const [todoIssue] = await db.select().from(issues).where(eq(issues.id, todoIssueId));
-      expect(todoIssue?.status).toBe("todo");
-      expect(todoIssue?.assigneeAgentId).toBeNull();
-
-      const [reviewIssue] = await db.select().from(issues).where(eq(issues.id, reviewIssueId));
-      expect(reviewIssue?.status).toBe("in_review");
-      expect(reviewIssue?.assigneeAgentId).toBeNull();
-
-      const [userIssue] = await db.select().from(issues).where(eq(issues.id, userIssueId));
-      expect(userIssue?.status).toBe("todo");
-      expect(userIssue?.assigneeUserId).toBe("user-1");
-
-      const comments = await db.select().from(issueComments).where(eq(issueComments.issueId, inProgressIssueId));
-      expect(comments).toHaveLength(1);
-      expect(comments[0]?.body).toContain("Quarantined during worktree seed");
-    } finally {
-      await db.$client?.end?.({ timeout: 5 }).catch(() => undefined);
-      await tempDb.cleanup();
-    }
-  }, 20_000);
-
   it("copies the source local_encrypted secrets key into the seeded worktree instance", () => {
     const tempRoot = fs.mkdtempSync(path.join(os.tmpdir(), "paperclip-worktree-secrets-"));
     const originalInlineMasterKey = process.env.PAPERCLIP_SECRETS_MASTER_KEY;
@@ -512,136 +350,6 @@ describe("worktree helpers", () => {
     }
   });
 
-  it("preserves repo-managed worktree checkouts when --force re-runs from the source repo", async () => {
-    const tempRoot = fs.mkdtempSync(path.join(os.tmpdir(), "paperclip-worktree-force-preserve-"));
-    const repoRoot = path.join(tempRoot, "repo");
-    const originalCwd = process.cwd();
-
-    try {
-      fs.mkdirSync(repoRoot, { recursive: true });
-      const repoConfigDir = path.join(repoRoot, ".paperclip");
-      fs.mkdirSync(repoConfigDir, { recursive: true });
-      fs.writeFileSync(path.join(repoConfigDir, "config.json"), "stale", "utf8");
-      fs.writeFileSync(path.join(repoConfigDir, ".env"), "STALE=1", "utf8");
-
-      // Simulate the repo-managed worktrees subfolder that holds every
-      // worktree checkout (the directory PAPA-358 reported as nuked).
-      const worktreesDir = path.join(repoConfigDir, "worktrees");
-      const checkoutDir = path.join(worktreesDir, "PAP-100-feature");
-      fs.mkdirSync(checkoutDir, { recursive: true });
-      const sentinelPath = path.join(checkoutDir, "sentinel.txt");
-      fs.writeFileSync(sentinelPath, "do-not-delete", "utf8");
-
-      process.chdir(repoRoot);
-
-      await worktreeInitCommand({
-        seed: false,
-        force: true,
-        fromConfig: path.join(tempRoot, "missing", "config.json"),
-        home: path.join(tempRoot, ".paperclip-worktrees"),
-      });
-
-      expect(fs.existsSync(sentinelPath)).toBe(true);
-      expect(fs.readFileSync(sentinelPath, "utf8")).toBe("do-not-delete");
-      expect(fs.existsSync(path.join(repoConfigDir, "config.json"))).toBe(true);
-      expect(fs.readFileSync(path.join(repoConfigDir, "config.json"), "utf8")).not.toBe("stale");
-    } finally {
-      process.chdir(originalCwd);
-      fs.rmSync(tempRoot, { recursive: true, force: true });
-    }
-  });
-
-  itEmbeddedPostgres(
-    "seeds authenticated users into minimally cloned worktree instances",
-    async () => {
-      const tempRoot = fs.mkdtempSync(path.join(os.tmpdir(), "paperclip-worktree-auth-seed-"));
-      const worktreeRoot = path.join(tempRoot, "PAP-999-auth-seed");
-      const sourceHome = path.join(tempRoot, "source-home");
-      const sourceConfigDir = path.join(sourceHome, "instances", "source");
-      const sourceConfigPath = path.join(sourceConfigDir, "config.json");
-      const sourceEnvPath = path.join(sourceConfigDir, ".env");
-      const sourceKeyPath = path.join(sourceConfigDir, "secrets", "master.key");
-      const worktreeHome = path.join(tempRoot, ".paperclip-worktrees");
-      const originalCwd = process.cwd();
-      const sourceDb = await startEmbeddedPostgresTestDatabase("paperclip-worktree-auth-source-");
-
-      try {
-        const sourceDbClient = createDb(sourceDb.connectionString);
-        await sourceDbClient.insert(authUsers).values({
-          id: "user-existing",
-          email: "existing@paperclip.ing",
-          name: "Existing User",
-          emailVerified: true,
-          createdAt: new Date(),
-          updatedAt: new Date(),
-        });
-
-        fs.mkdirSync(path.dirname(sourceKeyPath), { recursive: true });
-        fs.mkdirSync(worktreeRoot, { recursive: true });
-
-        const sourceConfig = buildSourceConfig();
-        sourceConfig.database = {
-          mode: "postgres",
-          embeddedPostgresDataDir: path.join(sourceConfigDir, "db"),
-          embeddedPostgresPort: 54329,
-          backup: {
-            enabled: true,
-            intervalMinutes: 60,
-            retentionDays: 30,
-            dir: path.join(sourceConfigDir, "backups"),
-          },
-          connectionString: sourceDb.connectionString,
-        };
-        sourceConfig.logging.logDir = path.join(sourceConfigDir, "logs");
-        sourceConfig.storage.localDisk.baseDir = path.join(sourceConfigDir, "storage");
-        sourceConfig.secrets.localEncrypted.keyFilePath = sourceKeyPath;
-
-        fs.writeFileSync(sourceConfigPath, JSON.stringify(sourceConfig, null, 2) + "\n", "utf8");
-        fs.writeFileSync(sourceEnvPath, "", "utf8");
-        fs.writeFileSync(sourceKeyPath, "source-master-key", "utf8");
-
-        process.chdir(worktreeRoot);
-        await worktreeInitCommand({
-          name: "PAP-999-auth-seed",
-          home: worktreeHome,
-          fromConfig: sourceConfigPath,
-          force: true,
-        });
-
-        const targetConfig = JSON.parse(
-          fs.readFileSync(path.join(worktreeRoot, ".paperclip", "config.json"), "utf8"),
-        ) as PaperclipConfig;
-        const { default: EmbeddedPostgres } = await import("embedded-postgres");
-        const targetPg = new EmbeddedPostgres({
-          databaseDir: targetConfig.database.embeddedPostgresDataDir,
-          user: "paperclip",
-          password: "paperclip",
-          port: targetConfig.database.embeddedPostgresPort,
-          persistent: true,
-          initdbFlags: ["--encoding=UTF8", "--locale=C", "--lc-messages=C"],
-          onLog: () => {},
-          onError: () => {},
-        });
-
-        await targetPg.start();
-        try {
-          const targetDb = createDb(
-            `postgres://paperclip:paperclip@127.0.0.1:${targetConfig.database.embeddedPostgresPort}/paperclip`,
-          );
-          const seededUsers = await targetDb.select().from(authUsers);
-          expect(seededUsers.some((row) => row.email === "existing@paperclip.ing")).toBe(true);
-        } finally {
-          await targetPg.stop();
-        }
-      } finally {
-        process.chdir(originalCwd);
-        await sourceDb.cleanup();
-        fs.rmSync(tempRoot, { recursive: true, force: true });
-      }
-    },
-    30000,
-  );
-
   it("avoids ports already claimed by sibling worktree instance configs", async () => {
     const tempRoot = fs.mkdtempSync(path.join(os.tmpdir(), "paperclip-worktree-claimed-ports-"));
     const repoRoot = path.join(tempRoot, "repo");
@@ -921,7 +629,7 @@ describe("worktree helpers", () => {
       }
       fs.rmSync(tempRoot, { recursive: true, force: true });
     }
-  }, 30_000);
+  }, 20_000);
 
   it("restores the current worktree config and instance data if reseed fails", async () => {
     const tempRoot = fs.mkdtempSync(path.join(os.tmpdir(), "paperclip-worktree-reseed-rollback-"));
@@ -1078,7 +786,7 @@ describe("worktree helpers", () => {
       execFileSync("git", ["worktree", "remove", "--force", worktreePath], { cwd: repoRoot, stdio: "ignore" });
       fs.rmSync(tempRoot, { recursive: true, force: true });
     }
-  }, 15_000);
+  });
 
   it("creates and initializes a worktree from the top-level worktree:make command", async () => {
     const tempRoot = fs.mkdtempSync(path.join(os.tmpdir(), "paperclip-worktree-make-"));
@@ -1114,246 +822,4 @@ describe("worktree helpers", () => {
       fs.rmSync(tempRoot, { recursive: true, force: true });
     }
   }, 20_000);
-
-  it("no-ops on the primary checkout unless --branch is provided", async () => {
-    const tempRoot = fs.mkdtempSync(path.join(os.tmpdir(), "paperclip-worktree-repair-primary-"));
-    const repoRoot = path.join(tempRoot, "repo");
-    const originalCwd = process.cwd();
-
-    try {
-      fs.mkdirSync(repoRoot, { recursive: true });
-      execFileSync("git", ["init"], { cwd: repoRoot, stdio: "ignore" });
-      execFileSync("git", ["config", "user.email", "test@example.com"], { cwd: repoRoot, stdio: "ignore" });
-      execFileSync("git", ["config", "user.name", "Test User"], { cwd: repoRoot, stdio: "ignore" });
-      fs.writeFileSync(path.join(repoRoot, "README.md"), "# temp\n", "utf8");
-      execFileSync("git", ["add", "README.md"], { cwd: repoRoot, stdio: "ignore" });
-      execFileSync("git", ["commit", "-m", "Initial commit"], { cwd: repoRoot, stdio: "ignore" });
-
-      process.chdir(repoRoot);
-      await worktreeRepairCommand({});
-
-      expect(fs.existsSync(path.join(repoRoot, ".paperclip", "config.json"))).toBe(false);
-      expect(fs.existsSync(path.join(repoRoot, ".paperclip", "worktrees"))).toBe(false);
-    } finally {
-      process.chdir(originalCwd);
-      fs.rmSync(tempRoot, { recursive: true, force: true });
-    }
-  });
-
-  it("repairs the current linked worktree when Paperclip metadata is missing", async () => {
-    const tempRoot = fs.mkdtempSync(path.join(os.tmpdir(), "paperclip-worktree-repair-current-"));
-    const repoRoot = path.join(tempRoot, "repo");
-    const worktreePath = path.join(repoRoot, ".paperclip", "worktrees", "repair-me");
-    const sourceConfigPath = path.join(tempRoot, "source-config.json");
-    const worktreeHome = path.join(tempRoot, ".paperclip-worktrees");
-    const worktreePaths = resolveWorktreeLocalPaths({
-      cwd: worktreePath,
-      homeDir: worktreeHome,
-      instanceId: sanitizeWorktreeInstanceId(path.basename(worktreePath)),
-    });
-    const originalCwd = process.cwd();
-
-    try {
-      fs.mkdirSync(repoRoot, { recursive: true });
-      execFileSync("git", ["init"], { cwd: repoRoot, stdio: "ignore" });
-      execFileSync("git", ["config", "user.email", "test@example.com"], { cwd: repoRoot, stdio: "ignore" });
-      execFileSync("git", ["config", "user.name", "Test User"], { cwd: repoRoot, stdio: "ignore" });
-      fs.writeFileSync(path.join(repoRoot, "README.md"), "# temp\n", "utf8");
-      execFileSync("git", ["add", "README.md"], { cwd: repoRoot, stdio: "ignore" });
-      execFileSync("git", ["commit", "-m", "Initial commit"], { cwd: repoRoot, stdio: "ignore" });
-      fs.mkdirSync(path.dirname(worktreePath), { recursive: true });
-      execFileSync("git", ["worktree", "add", "-b", "repair-me", worktreePath, "HEAD"], {
-        cwd: repoRoot,
-        stdio: "ignore",
-      });
-
-      fs.writeFileSync(sourceConfigPath, JSON.stringify(buildSourceConfig(), null, 2), "utf8");
-      fs.mkdirSync(worktreePaths.instanceRoot, { recursive: true });
-      fs.writeFileSync(path.join(worktreePaths.instanceRoot, "marker.txt"), "stale", "utf8");
-
-      process.chdir(worktreePath);
-      await worktreeRepairCommand({
-        fromConfig: sourceConfigPath,
-        home: worktreeHome,
-        noSeed: true,
-      });
-
-      expect(fs.existsSync(path.join(worktreePath, ".paperclip", "config.json"))).toBe(true);
-      expect(fs.existsSync(path.join(worktreePath, ".paperclip", ".env"))).toBe(true);
-      expect(fs.existsSync(path.join(worktreePaths.instanceRoot, "marker.txt"))).toBe(false);
-    } finally {
-      process.chdir(originalCwd);
-      fs.rmSync(tempRoot, { recursive: true, force: true });
-    }
-  }, 20_000);
-
-  it("creates and repairs a missing branch worktree when --branch is provided", async () => {
-    const tempRoot = fs.mkdtempSync(path.join(os.tmpdir(), "paperclip-worktree-repair-branch-"));
-    const repoRoot = path.join(tempRoot, "repo");
-    const sourceConfigPath = path.join(tempRoot, "source-config.json");
-    const worktreeHome = path.join(tempRoot, ".paperclip-worktrees");
-    const originalCwd = process.cwd();
-    const expectedWorktreePath = path.join(repoRoot, ".paperclip", "worktrees", "feature-repair-me");
-
-    try {
-      fs.mkdirSync(repoRoot, { recursive: true });
-      execFileSync("git", ["init"], { cwd: repoRoot, stdio: "ignore" });
-      execFileSync("git", ["config", "user.email", "test@example.com"], { cwd: repoRoot, stdio: "ignore" });
-      execFileSync("git", ["config", "user.name", "Test User"], { cwd: repoRoot, stdio: "ignore" });
-      fs.writeFileSync(path.join(repoRoot, "README.md"), "# temp\n", "utf8");
-      execFileSync("git", ["add", "README.md"], { cwd: repoRoot, stdio: "ignore" });
-      execFileSync("git", ["commit", "-m", "Initial commit"], { cwd: repoRoot, stdio: "ignore" });
-      fs.writeFileSync(sourceConfigPath, JSON.stringify(buildSourceConfig(), null, 2), "utf8");
-
-      process.chdir(repoRoot);
-      await worktreeRepairCommand({
-        branch: "feature/repair-me",
-        fromConfig: sourceConfigPath,
-        home: worktreeHome,
-        noSeed: true,
-      });
-
-      expect(fs.existsSync(path.join(expectedWorktreePath, ".git"))).toBe(true);
-      expect(fs.existsSync(path.join(expectedWorktreePath, ".paperclip", "config.json"))).toBe(true);
-      expect(fs.existsSync(path.join(expectedWorktreePath, ".paperclip", ".env"))).toBe(true);
-    } finally {
-      process.chdir(originalCwd);
-      fs.rmSync(tempRoot, { recursive: true, force: true });
-    }
-  }, 20_000);
-});
-
-describeEmbeddedPostgres("pauseSeededScheduledRoutines", () => {
-  it("pauses only routines with enabled schedule triggers", async () => {
-    const tempDb = await startEmbeddedPostgresTestDatabase("paperclip-worktree-routines-");
-    const db = createDb(tempDb.connectionString);
-    const companyId = randomUUID();
-    const projectId = randomUUID();
-    const agentId = randomUUID();
-    const activeScheduledRoutineId = randomUUID();
-    const activeApiRoutineId = randomUUID();
-    const pausedScheduledRoutineId = randomUUID();
-    const archivedScheduledRoutineId = randomUUID();
-    const disabledScheduleRoutineId = randomUUID();
-
-    try {
-      await db.insert(companies).values({
-        id: companyId,
-        name: "Paperclip",
-        issuePrefix: `T${companyId.replace(/-/g, "").slice(0, 6).toUpperCase()}`,
-        requireBoardApprovalForNewAgents: false,
-      });
-      await db.insert(agents).values({
-        id: agentId,
-        companyId,
-        name: "Coder",
-        adapterType: "process",
-        adapterConfig: {},
-        runtimeConfig: {},
-        permissions: {},
-      });
-      await db.insert(projects).values({
-        id: projectId,
-        companyId,
-        name: "Project",
-        status: "in_progress",
-      });
-      await db.insert(routines).values([
-        {
-          id: activeScheduledRoutineId,
-          companyId,
-          projectId,
-          assigneeAgentId: agentId,
-          title: "Active scheduled",
-          status: "active",
-        },
-        {
-          id: activeApiRoutineId,
-          companyId,
-          projectId,
-          assigneeAgentId: agentId,
-          title: "Active API",
-          status: "active",
-        },
-        {
-          id: pausedScheduledRoutineId,
-          companyId,
-          projectId,
-          assigneeAgentId: agentId,
-          title: "Paused scheduled",
-          status: "paused",
-        },
-        {
-          id: archivedScheduledRoutineId,
-          companyId,
-          projectId,
-          assigneeAgentId: agentId,
-          title: "Archived scheduled",
-          status: "archived",
-        },
-        {
-          id: disabledScheduleRoutineId,
-          companyId,
-          projectId,
-          assigneeAgentId: agentId,
-          title: "Disabled schedule",
-          status: "active",
-        },
-      ]);
-      await db.insert(routineTriggers).values([
-        {
-          companyId,
-          routineId: activeScheduledRoutineId,
-          kind: "schedule",
-          enabled: true,
-          cronExpression: "0 9 * * *",
-          timezone: "UTC",
-        },
-        {
-          companyId,
-          routineId: activeApiRoutineId,
-          kind: "api",
-          enabled: true,
-        },
-        {
-          companyId,
-          routineId: pausedScheduledRoutineId,
-          kind: "schedule",
-          enabled: true,
-          cronExpression: "0 10 * * *",
-          timezone: "UTC",
-        },
-        {
-          companyId,
-          routineId: archivedScheduledRoutineId,
-          kind: "schedule",
-          enabled: true,
-          cronExpression: "0 11 * * *",
-          timezone: "UTC",
-        },
-        {
-          companyId,
-          routineId: disabledScheduleRoutineId,
-          kind: "schedule",
-          enabled: false,
-          cronExpression: "0 12 * * *",
-          timezone: "UTC",
-        },
-      ]);
-
-      const pausedCount = await pauseSeededScheduledRoutines(tempDb.connectionString);
-      expect(pausedCount).toBe(1);
-
-      const rows = await db.select({ id: routines.id, status: routines.status }).from(routines);
-      const statusById = new Map(rows.map((row) => [row.id, row.status]));
-      expect(statusById.get(activeScheduledRoutineId)).toBe("paused");
-      expect(statusById.get(activeApiRoutineId)).toBe("active");
-      expect(statusById.get(pausedScheduledRoutineId)).toBe("paused");
-      expect(statusById.get(archivedScheduledRoutineId)).toBe("archived");
-      expect(statusById.get(disabledScheduleRoutineId)).toBe("active");
-    } finally {
-      await db.$client?.end?.({ timeout: 5 }).catch(() => undefined);
-      await tempDb.cleanup();
-    }
-  }, 20_000);
 });

cli/src/adapters/registry.ts

@@ -1,11 +1,8 @@
 import type { CLIAdapterModule } from "@paperclipai/adapter-utils";
-import { printAcpxStreamEvent } from "@paperclipai/adapter-acpx-local/cli";
 import { printClaudeStreamEvent } from "@paperclipai/adapter-claude-local/cli";
 import { printCodexStreamEvent } from "@paperclipai/adapter-codex-local/cli";
 import { printCursorStreamEvent } from "@paperclipai/adapter-cursor-local/cli";
-import { printCursorCloudEvent } from "@paperclipai/adapter-cursor-cloud/cli";
 import { printGeminiStreamEvent } from "@paperclipai/adapter-gemini-local/cli";
-import { printGrokStreamEvent } from "@paperclipai/adapter-grok-local/cli";
 import { printOpenCodeStreamEvent } from "@paperclipai/adapter-opencode-local/cli";
 import { printPiStreamEvent } from "@paperclipai/adapter-pi-local/cli";
 import { printOpenClawGatewayStreamEvent } from "@paperclipai/adapter-openclaw-gateway/cli";
@@ -17,11 +14,6 @@ const claudeLocalCLIAdapter: CLIAdapterModule = {
   formatStdoutEvent: printClaudeStreamEvent,
 };
 
-const acpxLocalCLIAdapter: CLIAdapterModule = {
-  type: "acpx_local",
-  formatStdoutEvent: printAcpxStreamEvent,
-};
-
 const codexLocalCLIAdapter: CLIAdapterModule = {
   type: "codex_local",
   formatStdoutEvent: printCodexStreamEvent,
@@ -42,21 +34,11 @@ const cursorLocalCLIAdapter: CLIAdapterModule = {
   formatStdoutEvent: printCursorStreamEvent,
 };
 
-const cursorCloudCLIAdapter: CLIAdapterModule = {
-  type: "cursor_cloud",
-  formatStdoutEvent: printCursorCloudEvent,
-};
-
 const geminiLocalCLIAdapter: CLIAdapterModule = {
   type: "gemini_local",
   formatStdoutEvent: printGeminiStreamEvent,
 };
 
-const grokLocalCLIAdapter: CLIAdapterModule = {
-  type: "grok_local",
-  formatStdoutEvent: printGrokStreamEvent,
-};
-
 const openclawGatewayCLIAdapter: CLIAdapterModule = {
   type: "openclaw_gateway",
   formatStdoutEvent: printOpenClawGatewayStreamEvent,
@@ -64,15 +46,12 @@ const openclawGatewayCLIAdapter: CLIAdapterModule = {
 
 const adaptersByType = new Map<string, CLIAdapterModule>(
   [
-    acpxLocalCLIAdapter,
     claudeLocalCLIAdapter,
     codexLocalCLIAdapter,
     openCodeLocalCLIAdapter,
     piLocalCLIAdapter,
     cursorLocalCLIAdapter,
-    cursorCloudCLIAdapter,
     geminiLocalCLIAdapter,
-    grokLocalCLIAdapter,
     openclawGatewayCLIAdapter,
     processCLIAdapter,
     httpCLIAdapter,

cli/src/checks/deployment-auth-check.ts

@@ -1,21 +1,24 @@
-import { inferBindModeFromHost } from "@paperclipai/shared";
 import type { PaperclipConfig } from "../config/schema.js";
 import type { CheckResult } from "./index.js";
 
+function isLoopbackHost(host: string) {
+  const normalized = host.trim().toLowerCase();
+  return normalized === "127.0.0.1" || normalized === "localhost" || normalized === "::1";
+}
+
 export function deploymentAuthCheck(config: PaperclipConfig): CheckResult {
   const mode = config.server.deploymentMode;
   const exposure = config.server.exposure;
   const auth = config.auth;
-  const bind = config.server.bind ?? inferBindModeFromHost(config.server.host);
 
   if (mode === "local_trusted") {
-    if (bind !== "loopback") {
+    if (!isLoopbackHost(config.server.host)) {
       return {
         name: "Deployment/auth mode",
         status: "fail",
-        message: `local_trusted requires loopback binding (found ${bind})`,
+        message: `local_trusted requires loopback host binding (found ${config.server.host})`,
         canRepair: false,
-        repairHint: "Run `paperclipai configure --section server` and choose Local trusted / loopback reachability",
+        repairHint: "Run `paperclipai configure --section server` and set host to 127.0.0.1",
       };
     }
     return {
@@ -83,6 +86,6 @@ export function deploymentAuthCheck(config: PaperclipConfig): CheckResult {
   return {
     name: "Deployment/auth mode",
     status: "pass",
-    message: `Mode ${mode}/${exposure} with bind ${bind} and auth URL mode ${auth.baseUrlMode}`,
+    message: `Mode ${mode}/${exposure} with auth URL mode ${auth.baseUrlMode}`,
   };
 }

cli/src/checks/secrets-check.ts

@@ -5,9 +5,6 @@ import type { PaperclipConfig } from "../config/schema.js";
 import type { CheckResult } from "./index.js";
 import { resolveRuntimeLikePath } from "./path-resolver.js";
 
-const AWS_CREDENTIAL_SOURCE_HINT =
-  "Provide AWS runtime credentials through the AWS SDK default credential chain: IAM role/workload identity, AWS_PROFILE/SSO/shared credentials, web identity, container/instance metadata, or short-lived shell credentials";
-
 function decodeMasterKey(raw: string): Buffer | null {
   const trimmed = raw.trim();
   if (!trimmed) return null;
@@ -50,16 +47,13 @@ function withStrictModeNote(
 
 export function secretsCheck(config: PaperclipConfig, configPath?: string): CheckResult {
   const provider = config.secrets.provider;
-  if (provider === "aws_secrets_manager") {
-    return withStrictModeNote(awsSecretsManagerCheck(), config);
-  }
   if (provider !== "local_encrypted") {
     return {
       name: "Secrets adapter",
       status: "fail",
-      message: `${provider} is configured, but this build only supports local_encrypted and aws_secrets_manager`,
+      message: `${provider} is configured, but this build only supports local_encrypted`,
       canRepair: false,
-      repairHint: "Run `paperclipai configure --section secrets` and choose local_encrypted or aws_secrets_manager",
+      repairHint: "Run `paperclipai configure --section secrets` and set provider to local_encrypted",
     };
   }
 
@@ -141,100 +135,12 @@ export function secretsCheck(config: PaperclipConfig, configPath?: string): Chec
     };
   }
 
-  const keyMode = fs.statSync(keyFilePath).mode & 0o777;
-  const permissionWarning =
-    (keyMode & 0o077) !== 0
-      ? `; key file permissions are ${keyMode.toString(8)} (run chmod 600 ${keyFilePath})`
-      : "";
-
   return withStrictModeNote(
     {
       name: "Secrets adapter",
-      status: permissionWarning ? "warn" : "pass",
-      message: `Local encrypted provider configured with key file ${keyFilePath}${permissionWarning}`,
-      repairHint: permissionWarning
-        ? "Restrict the local encrypted secrets key file to owner read/write permissions"
-        : undefined,
+      status: "pass",
+      message: `Local encrypted provider configured with key file ${keyFilePath}`,
     },
     config,
   );
 }
-
-function awsSecretsManagerCheck(): CheckResult {
-  const missingConfig = missingAwsSecretsManagerConfig();
-  if (missingConfig.length > 0) {
-    return {
-      name: "Secrets adapter",
-      status: "fail",
-      message: `AWS Secrets Manager provider is missing non-secret config: ${missingConfig.join(", ")}`,
-      canRepair: false,
-      repairHint:
-        `Set ${missingConfig.join(", ")} in the Paperclip server runtime. ${AWS_CREDENTIAL_SOURCE_HINT}. Do not store AWS root credentials or long-lived IAM user keys in Paperclip secrets.`,
-    };
-  }
-
-  const staticEnvCredentials =
-    process.env.AWS_ACCESS_KEY_ID?.trim() && process.env.AWS_SECRET_ACCESS_KEY?.trim();
-  const credentialSource = detectedAwsCredentialSources().join(", ");
-  const message =
-    `AWS Secrets Manager provider configured for deployment ${process.env.PAPERCLIP_SECRETS_AWS_DEPLOYMENT_ID}; ` +
-    `runtime credentials source: ${credentialSource || "AWS SDK default credential chain"}`;
-
-  if (staticEnvCredentials) {
-    return {
-      name: "Secrets adapter",
-      status: "warn",
-      message,
-      canRepair: false,
-      repairHint:
-        "AWS static environment credentials are visible. Use only short-lived shell credentials locally; prefer IAM role/workload identity for hosted deployments and never store AWS access keys in Paperclip company secrets.",
-    };
-  }
-
-  return {
-    name: "Secrets adapter",
-    status: "pass",
-    message,
-  };
-}
-
-function missingAwsSecretsManagerConfig(): string[] {
-  const missing: string[] = [];
-  if (
-    !(
-      process.env.PAPERCLIP_SECRETS_AWS_REGION?.trim() ||
-      process.env.AWS_REGION?.trim() ||
-      process.env.AWS_DEFAULT_REGION?.trim()
-    )
-  ) {
-    missing.push("PAPERCLIP_SECRETS_AWS_REGION or AWS_REGION/AWS_DEFAULT_REGION");
-  }
-  if (!process.env.PAPERCLIP_SECRETS_AWS_DEPLOYMENT_ID?.trim()) {
-    missing.push("PAPERCLIP_SECRETS_AWS_DEPLOYMENT_ID");
-  }
-  if (!process.env.PAPERCLIP_SECRETS_AWS_KMS_KEY_ID?.trim()) {
-    missing.push("PAPERCLIP_SECRETS_AWS_KMS_KEY_ID");
-  }
-  return missing;
-}
-
-function detectedAwsCredentialSources(): string[] {
-  const sources: string[] = [];
-  if (process.env.AWS_PROFILE?.trim()) sources.push("AWS_PROFILE/shared config");
-  if (process.env.AWS_ACCESS_KEY_ID?.trim() && process.env.AWS_SECRET_ACCESS_KEY?.trim()) {
-    sources.push("temporary AWS_ACCESS_KEY_ID/AWS_SECRET_ACCESS_KEY environment credentials");
-  }
-  if (process.env.AWS_WEB_IDENTITY_TOKEN_FILE?.trim() && process.env.AWS_ROLE_ARN?.trim()) {
-    sources.push("AWS web identity token");
-  }
-  if (
-    process.env.AWS_CONTAINER_CREDENTIALS_RELATIVE_URI?.trim() ||
-    process.env.AWS_CONTAINER_CREDENTIALS_FULL_URI?.trim()
-  ) {
-    sources.push("AWS container credentials endpoint");
-  }
-  if (process.env.AWS_SHARED_CREDENTIALS_FILE?.trim() || process.env.AWS_CONFIG_FILE?.trim()) {
-    sources.push("custom AWS shared credentials/config file");
-  }
-  return sources;
-}

cli/src/commands/auth-bootstrap-ceo.ts

@@ -3,7 +3,6 @@ import * as p from "@clack/prompts";
 import pc from "picocolors";
 import { and, eq, gt, isNull } from "drizzle-orm";
 import { createDb, instanceUserRoles, invites } from "@paperclipai/db";
-import { inferBindModeFromHost } from "@paperclipai/shared";
 import { loadPaperclipEnvFile } from "../config/env.js";
 import { readConfig, resolveConfigPath } from "../config/store.js";
 
@@ -41,13 +40,9 @@ function resolveBaseUrl(configPath?: string, explicitBaseUrl?: string) {
   if (config?.auth.baseUrlMode === "explicit" && config.auth.publicBaseUrl) {
     return config.auth.publicBaseUrl.replace(/\/+$/, "");
   }
-  const bind = config?.server.bind ?? inferBindModeFromHost(config?.server.host);
-  const host =
-    bind === "custom"
-      ? config?.server.customBindHost ?? config?.server.host ?? "localhost"
-      : config?.server.host ?? "localhost";
+  const host = config?.server.host ?? "localhost";
   const port = config?.server.port ?? 3100;
-  const publicHost = host === "0.0.0.0" || bind === "lan" ? "localhost" : host;
+  const publicHost = host === "0.0.0.0" ? "localhost" : host;
   return `http://${publicHost}:${port}`;
 }
 

cli/src/commands/client/cloud-store.ts

@@ -1,177 +0,0 @@
-import fs from "node:fs";
-import path from "node:path";
-import { resolvePaperclipInstanceRoot } from "../../config/home.js";
-
-export interface CloudConnectionTokenRecord {
-  id: string;
-  companyStackId: string;
-  targetOrigin: string;
-  sourceInstanceId: string;
-  sourceInstanceFingerprint: string;
-  scopes: string[];
-  expiresAt: string;
-  [key: string]: unknown;
-}
-
-export interface CloudConnection {
-  id: string;
-  remoteUrl: string;
-  targetOrigin: string;
-  targetHost: string;
-  stackId: string;
-  stackSlug?: string | null;
-  stackDisplayName?: string | null;
-  targetCompanyId: string;
-  accessToken: string;
-  token: CloudConnectionTokenRecord;
-  privateKeyPem: string;
-  sourcePublicKey: string;
-  sourceInstanceId: string;
-  sourceInstanceFingerprint: string;
-  scopes: string[];
-  createdAt: string;
-  updatedAt: string;
-}
-
-interface CloudConnectionStore {
-  version: 1;
-  connections: Record<string, CloudConnection>;
-  currentConnectionId?: string;
-}
-
-function defaultStore(): CloudConnectionStore {
-  return {
-    version: 1,
-    connections: {},
-  };
-}
-
-export function resolveCloudConnectionStorePath(): string {
-  return path.resolve(resolvePaperclipInstanceRoot(), "secrets", "cloud-upstream-connections.json");
-}
-
-export function readCloudConnectionStore(storePath = resolveCloudConnectionStorePath()): CloudConnectionStore {
-  if (!fs.existsSync(storePath)) return defaultStore();
-  const raw = JSON.parse(fs.readFileSync(storePath, "utf8")) as Partial<CloudConnectionStore> | null;
-  const connections: Record<string, CloudConnection> = {};
-  if (raw?.connections && typeof raw.connections === "object") {
-    for (const [id, value] of Object.entries(raw.connections)) {
-      const normalized = normalizeConnection(value);
-      if (normalized) connections[id] = normalized;
-    }
-  }
-  const currentConnectionId =
-    typeof raw?.currentConnectionId === "string" && connections[raw.currentConnectionId]
-      ? raw.currentConnectionId
-      : Object.values(connections).sort((left, right) => right.updatedAt.localeCompare(left.updatedAt))[0]?.id;
-  return {
-    version: 1,
-    connections,
-    currentConnectionId,
-  };
-}
-
-export function writeCloudConnectionStore(
-  store: CloudConnectionStore,
-  storePath = resolveCloudConnectionStorePath(),
-): void {
-  fs.mkdirSync(path.dirname(storePath), { recursive: true });
-  fs.writeFileSync(storePath, `${JSON.stringify(store, null, 2)}\n`, { mode: 0o600 });
-}
-
-export function upsertCloudConnection(
-  connection: CloudConnection,
-  storePath = resolveCloudConnectionStorePath(),
-): CloudConnection {
-  const store = readCloudConnectionStore(storePath);
-  const existing = store.connections[connection.id];
-  const now = new Date().toISOString();
-  const next = {
-    ...connection,
-    createdAt: existing?.createdAt ?? connection.createdAt ?? now,
-    updatedAt: now,
-  };
-  store.connections[next.id] = next;
-  store.currentConnectionId = next.id;
-  writeCloudConnectionStore(store, storePath);
-  return next;
-}
-
-export function getCloudConnection(
-  remoteUrlOrOrigin?: string,
-  storePath = resolveCloudConnectionStorePath(),
-): CloudConnection | null {
-  const store = readCloudConnectionStore(storePath);
-  if (remoteUrlOrOrigin?.trim()) {
-    const needle = normalizeRemoteLookup(remoteUrlOrOrigin);
-    return Object.values(store.connections).find((connection) =>
-      normalizeRemoteLookup(connection.remoteUrl) === needle ||
-      normalizeRemoteLookup(connection.targetOrigin) === needle
-    ) ?? null;
-  }
-  return store.currentConnectionId ? store.connections[store.currentConnectionId] ?? null : null;
-}
-
-function normalizeRemoteLookup(value: string): string {
-  try {
-    const url = new URL(value);
-    return url.origin.replace(/\/+$/u, "");
-  } catch {
-    return value.trim().replace(/\/+$/u, "");
-  }
-}
-
-function normalizeConnection(value: unknown): CloudConnection | null {
-  if (typeof value !== "object" || value === null || Array.isArray(value)) return null;
-  const record = value as Record<string, unknown>;
-  const id = stringValue(record.id);
-  const remoteUrl = stringValue(record.remoteUrl);
-  const targetOrigin = stringValue(record.targetOrigin);
-  const targetHost = stringValue(record.targetHost);
-  const stackId = stringValue(record.stackId);
-  const targetCompanyId = stringValue(record.targetCompanyId);
-  const accessToken = stringValue(record.accessToken);
-  const token = typeof record.token === "object" && record.token !== null && !Array.isArray(record.token)
-    ? record.token as CloudConnectionTokenRecord
-    : null;
-  const privateKeyPem = stringValue(record.privateKeyPem);
-  const sourcePublicKey = stringValue(record.sourcePublicKey);
-  const sourceInstanceId = stringValue(record.sourceInstanceId);
-  const sourceInstanceFingerprint = stringValue(record.sourceInstanceFingerprint);
-  const createdAt = stringValue(record.createdAt);
-  const updatedAt = stringValue(record.updatedAt);
-  if (
-    !id || !remoteUrl || !targetOrigin || !targetHost || !stackId || !targetCompanyId ||
-    !accessToken || !token || !privateKeyPem || !sourcePublicKey || !sourceInstanceId ||
-    !sourceInstanceFingerprint || !createdAt || !updatedAt
-  ) {
-    return null;
-  }
-  return {
-    id,
-    remoteUrl,
-    targetOrigin,
-    targetHost,
-    stackId,
-    stackSlug: stringValue(record.stackSlug),
-    stackDisplayName: stringValue(record.stackDisplayName),
-    targetCompanyId,
-    accessToken,
-    token,
-    privateKeyPem,
-    sourcePublicKey,
-    sourceInstanceId,
-    sourceInstanceFingerprint,
-    scopes: stringArray(record.scopes),
-    createdAt,
-    updatedAt,
-  };
-}
-
-function stringValue(value: unknown): string | null {
-  return typeof value === "string" && value.trim().length > 0 ? value.trim() : null;
-}
-
-function stringArray(value: unknown): string[] {
-  return Array.isArray(value) ? value.filter((entry): entry is string => typeof entry === "string") : [];
-}

cli/src/commands/client/cloud-transfer.ts

@@ -1,297 +0,0 @@
-import { createHash } from "node:crypto";
-
-export const upstreamTransferSchema = {
-  family: "paperclip-upstream-transfer",
-  version: "1.0.0",
-  major: 1,
-  minor: 0,
-} as const;
-
-export type NormalizedSha256 = `sha256:${string}`;
-
-export interface SourceEntityKey {
-  sourceInstanceId: string;
-  sourceCompanyId: string;
-  sourceEntityType: string;
-  sourceEntityId: string;
-  sourceNaturalKey?: string;
-}
-
-export interface UpstreamTransferWarning {
-  code: string;
-  severity: "info" | "warning" | "blocker";
-  message: string;
-  entity?: SourceEntityKey;
-}
-
-export interface UpstreamTransferEntityRecord {
-  key: SourceEntityKey;
-  contentHash: NormalizedSha256;
-  dependencies: SourceEntityKey[];
-  warnings: UpstreamTransferWarning[];
-}
-
-export interface UpstreamTransferManifestSource {
-  sourceInstanceId: string;
-  sourceCompanyId: string;
-  sourceInstanceKeyFingerprint: string;
-  exporterVersion: string;
-  sourceSchemaVersion: string;
-}
-
-export interface UpstreamTransferManifestTarget {
-  targetStackId: string;
-  targetCompanyId: string;
-  targetOrigin: string;
-  supportedSchemaMajor: number;
-}
-
-export interface UpstreamTransferChunk {
-  chunkIndex: number;
-  totalChunks: number;
-  byteLength: number;
-  sha256: NormalizedSha256;
-  manifestHash: NormalizedSha256;
-}
-
-export interface UpstreamTransferManifest {
-  schema: typeof upstreamTransferSchema;
-  source: UpstreamTransferManifestSource;
-  target: UpstreamTransferManifestTarget;
-  runId: string;
-  idempotencyKey: string;
-  generatedAt: string;
-  entityCount: number;
-  entities: UpstreamTransferEntityRecord[];
-  chunks: UpstreamTransferChunk[];
-  warnings: UpstreamTransferWarning[];
-  featureFlags: string[];
-  manifestHash: NormalizedSha256;
-}
-
-export interface LocalUpstreamExportEntityInput {
-  key: SourceEntityKey;
-  body: Record<string, unknown>;
-  dependencies?: SourceEntityKey[];
-  warnings?: UpstreamTransferWarning[];
-  conflictKeys?: string[];
-}
-
-export interface LocalUpstreamExportEntity {
-  record: UpstreamTransferEntityRecord;
-  body: Record<string, unknown>;
-  conflictKeys?: string[];
-}
-
-export interface LocalUpstreamExportChunk {
-  chunkIndex: number;
-  totalChunks: number;
-  byteLength: number;
-  sha256: NormalizedSha256;
-  payload: {
-    entityKeys: SourceEntityKey[];
-  };
-}
-
-export interface LocalUpstreamExportBundle {
-  manifest: UpstreamTransferManifest;
-  entities: LocalUpstreamExportEntity[];
-  chunks: LocalUpstreamExportChunk[];
-}
-
-export interface BuildLocalUpstreamExportBundleInput {
-  source: UpstreamTransferManifestSource;
-  target: UpstreamTransferManifestTarget;
-  runId: string;
-  idempotencyKey: string;
-  entities: LocalUpstreamExportEntityInput[];
-  warnings?: UpstreamTransferWarning[];
-  featureFlags?: string[];
-  maxEntitiesPerChunk?: number;
-}
-
-export interface LocalUpstreamPushCoordinatorOptions {
-  targetOrigin: string;
-  paperclipCompanyId: string;
-  fetch?: typeof fetch;
-  headers?: (input: { method: string; path: string }) => HeadersInit | Promise<HeadersInit>;
-}
-
-export class UpstreamImportRequestError extends Error {
-  readonly status: number;
-  readonly body: unknown;
-
-  constructor(status: number, message: string, body: unknown) {
-    super(message);
-    this.status = status;
-    this.body = body;
-  }
-}
-
-export class LocalUpstreamPushCoordinator {
-  readonly #targetOrigin: string;
-  readonly #paperclipCompanyId: string;
-  readonly #fetch: typeof fetch;
-  readonly #headers: NonNullable<LocalUpstreamPushCoordinatorOptions["headers"]>;
-
-  constructor(options: LocalUpstreamPushCoordinatorOptions) {
-    this.#targetOrigin = options.targetOrigin.replace(/\/+$/u, "");
-    this.#paperclipCompanyId = options.paperclipCompanyId;
-    this.#fetch = options.fetch ?? fetch;
-    this.#headers = options.headers ?? (() => ({}));
-  }
-
-  async preview(bundle: LocalUpstreamExportBundle): Promise<unknown> {
-    return this.post(`/api/companies/${encodeURIComponent(this.#paperclipCompanyId)}/upstream-imports/preview`, {
-      manifest: bundle.manifest,
-      entities: bundle.entities,
-    });
-  }
-
-  async apply(bundle: LocalUpstreamExportBundle): Promise<unknown> {
-    const run = await this.post(`/api/companies/${encodeURIComponent(this.#paperclipCompanyId)}/upstream-imports/runs`, {
-      mode: "apply",
-      manifest: bundle.manifest,
-      entities: bundle.entities,
-    }) as { run?: { id?: unknown } };
-    const runId = typeof run.run?.id === "string" ? run.run.id : undefined;
-    if (!runId) {
-      throw new Error("Remote upstream importer did not return a run id");
-    }
-
-    for (const chunk of bundle.chunks) {
-      await this.post(`/api/upstream-import-runs/${encodeURIComponent(runId)}/chunks`, chunk);
-    }
-
-    return this.post(`/api/upstream-import-runs/${encodeURIComponent(runId)}/apply`, {});
-  }
-
-  async events(runId: string): Promise<unknown> {
-    return this.get(`/api/upstream-import-runs/${encodeURIComponent(runId)}/events`);
-  }
-
-  private async get(path: string): Promise<unknown> {
-    const response = await this.#fetch(`${this.#targetOrigin}${path}`, {
-      method: "GET",
-      headers: await this.#headers({ method: "GET", path }),
-    });
-    return parseCoordinatorResponse(response);
-  }
-
-  private async post(path: string, body: unknown): Promise<unknown> {
-    const response = await this.#fetch(`${this.#targetOrigin}${path}`, {
-      method: "POST",
-      headers: {
-        "Content-Type": "application/json",
-        ...(await this.#headers({ method: "POST", path })),
-      },
-      body: JSON.stringify(body),
-    });
-    return parseCoordinatorResponse(response);
-  }
-}
-
-export function buildLocalUpstreamExportBundle(
-  input: BuildLocalUpstreamExportBundleInput,
-): LocalUpstreamExportBundle {
-  const entities = input.entities.map<LocalUpstreamExportEntity>((entity) => ({
-    record: {
-      key: entity.key,
-      contentHash: normalizedContentHash(entity.body),
-      dependencies: entity.dependencies ?? [],
-      warnings: entity.warnings ?? [],
-    },
-    body: entity.body,
-    conflictKeys: entity.conflictKeys,
-  }));
-  const chunks = buildLocalChunks(entities, input.maxEntitiesPerChunk ?? 100);
-  const manifestWithoutHash = {
-    schema: upstreamTransferSchema,
-    source: input.source,
-    target: input.target,
-    runId: input.runId,
-    idempotencyKey: input.idempotencyKey,
-    generatedAt: new Date(0).toISOString(),
-    entityCount: entities.length,
-    entities: entities.map((entity) => entity.record),
-    chunks: chunks.map(({ payload: _payload, ...chunk }) => chunk),
-    warnings: input.warnings ?? [],
-    featureFlags: (input.featureFlags ?? ["cloud_sync"]).slice().sort(),
-  };
-  const manifestHash = normalizedContentHash(manifestWithoutHash);
-  return {
-    manifest: {
-      ...manifestWithoutHash,
-      chunks: manifestWithoutHash.chunks.map((chunk) => ({ ...chunk, manifestHash })),
-      manifestHash,
-    },
-    entities,
-    chunks,
-  };
-}
-
-export function normalizedContentHash(value: unknown): NormalizedSha256 {
-  return `sha256:${createHash("sha256").update(canonicalJson(value)).digest("hex")}`;
-}
-
-export function canonicalJson(value: unknown): string {
-  return JSON.stringify(sortJson(value));
-}
-
-function buildLocalChunks(
-  entities: LocalUpstreamExportEntity[],
-  maxEntitiesPerChunk: number,
-): LocalUpstreamExportChunk[] {
-  if (!Number.isInteger(maxEntitiesPerChunk) || maxEntitiesPerChunk < 1) {
-    throw new Error("maxEntitiesPerChunk must be a positive integer");
-  }
-  if (entities.length === 0) return [];
-
-  const groups: LocalUpstreamExportEntity[][] = [];
-  for (let index = 0; index < entities.length; index += maxEntitiesPerChunk) {
-    groups.push(entities.slice(index, index + maxEntitiesPerChunk));
-  }
-
-  return groups.map((group, index) => {
-    const payload = {
-      entityKeys: group.map((entity) => entity.record.key),
-    };
-    return {
-      chunkIndex: index,
-      totalChunks: groups.length,
-      byteLength: Buffer.byteLength(canonicalJson(payload)),
-      sha256: normalizedContentHash(payload),
-      payload,
-    };
-  });
-}
-
-function sortJson(value: unknown): unknown {
-  if (Array.isArray(value)) return value.map(sortJson);
-  if (typeof value !== "object" || value === null) return value;
-  return Object.fromEntries(
-    Object.entries(value as Record<string, unknown>)
-      .sort(([left], [right]) => left.localeCompare(right))
-      .map(([key, entry]) => [key, sortJson(entry)]),
-  );
-}
-
-async function parseCoordinatorResponse(response: Response): Promise<unknown> {
-  const text = await response.text();
-  const parsed = text.trim() ? safeParseJson(text) : {};
-  if (!response.ok) {
-    const message = typeof parsed === "object" && parsed !== null && "error" in parsed
-      ? String((parsed as { error: unknown }).error)
-      : `Upstream importer request failed with ${response.status}`;
-    throw new UpstreamImportRequestError(response.status, message, parsed);
-  }
-  return parsed;
-}
-
-function safeParseJson(text: string): unknown {
-  try {
-    return JSON.parse(text);
-  } catch {
-    return text;
-  }
-}

cli/src/commands/client/cloud.ts

@@ -1,721 +0,0 @@
-import { createHash, generateKeyPairSync, randomBytes, randomUUID, sign } from "node:crypto";
-import { createServer, type Server } from "node:http";
-import { URL } from "node:url";
-import { Command } from "commander";
-import pc from "picocolors";
-import type {
-  CompanyPortabilityExportResult,
-  CompanyPortabilityFileEntry,
-  InstanceExperimentalSettings,
-} from "@paperclipai/shared";
-import { openUrl } from "../../client/board-auth.js";
-import { resolvePaperclipInstanceId } from "../../config/home.js";
-import {
-  addCommonClientOptions,
-  handleCommandError,
-  printOutput,
-  resolveCommandContext,
-  type BaseClientOptions,
-} from "./common.js";
-import {
-  buildLocalUpstreamExportBundle,
-  LocalUpstreamPushCoordinator,
-  normalizedContentHash,
-  upstreamTransferSchema,
-  UpstreamImportRequestError,
-  type LocalUpstreamExportBundle,
-  type LocalUpstreamExportEntityInput,
-  type SourceEntityKey,
-  type UpstreamTransferManifestSource,
-  type UpstreamTransferManifestTarget,
-  type UpstreamTransferWarning,
-} from "./cloud-transfer.js";
-import {
-  getCloudConnection,
-  upsertCloudConnection,
-  type CloudConnection,
-  type CloudConnectionTokenRecord,
-} from "./cloud-store.js";
-
-const CLOUD_SYNC_CONFLICT_EXIT_CODE = 2;
-const CLOUD_SYNC_SCHEMA_MISMATCH_EXIT_CODE = 3;
-const CLOUD_SYNC_SCOPES = ["upstream_import:preview", "upstream_import:write", "upstream_import:read"];
-const DEVICE_CODE_FALLBACK_EXPIRES_MS = 15 * 60_000;
-
-interface CloudConnectOptions extends BaseClientOptions {
-  noBrowser?: boolean;
-}
-
-interface CloudPushOptions extends BaseClientOptions {
-  company?: string;
-  remoteUrl?: string;
-  dryRun?: boolean;
-  maxEntitiesPerChunk?: number;
-}
-
-interface UpstreamDiscovery {
-  schema: string;
-  stack: {
-    id: string;
-    slug?: string;
-    displayName?: string;
-    companyId: string;
-    origin: string;
-  };
-  auth: {
-    pkce?: {
-      authorizeUrl: string;
-      tokenUrl: string;
-      codeChallengeMethod: string;
-    };
-    deviceCode?: {
-      deviceCodeUrl: string;
-      verificationUrl: string;
-      tokenUrl: string;
-    };
-    scopes?: string[];
-  };
-  transfer: {
-    supportedSchemaMajor: number;
-    featureFlags?: string[];
-  };
-}
-
-interface TokenResponse {
-  accessToken: string;
-  token: CloudConnectionTokenRecord;
-  scopes?: string[];
-  expiresAt?: string;
-}
-
-class CloudAuthRequestError extends Error {
-  readonly status: number;
-  readonly body: unknown;
-
-  constructor(status: number, message: string, body: unknown) {
-    super(message);
-    this.status = status;
-    this.body = body;
-  }
-}
-
-export function registerCloudCommands(program: Command): void {
-  const cloud = program.command("cloud").description("Paperclip Cloud upstream sync commands");
-
-  addCommonClientOptions(
-    cloud
-      .command("connect")
-      .description("Authorize this local instance to push into a Paperclip Cloud stack")
-      .argument("<remote-url>", "Paperclip Cloud stack URL")
-      .option("--no-browser", "Use the device-code flow instead of opening a browser", false)
-      .action(async (remoteUrl: string, opts: CloudConnectOptions) => {
-        try {
-          await connectCloud(remoteUrl, opts);
-        } catch (err) {
-          handleCommandError(err);
-        }
-      }),
-  );
-
-  addCommonClientOptions(
-    cloud
-      .command("push")
-      .description("Preview or apply a local company push into the connected Paperclip Cloud stack")
-      .requiredOption("--company <local-company-id>", "Local company ID to export")
-      .option("--remote-url <remote-url>", "Use a specific stored cloud connection")
-      .option("--dry-run", "Preview without applying", false)
-      .option("--max-entities-per-chunk <count>", "Chunk size for upstream uploads", (value) => Number(value), 100)
-      .action(async (opts: CloudPushOptions) => {
-        try {
-          await pushCloud(opts);
-        } catch (err) {
-          if (isSchemaMismatchError(err)) {
-            console.error(pc.red(err instanceof Error ? err.message : String(err)));
-            process.exitCode = CLOUD_SYNC_SCHEMA_MISMATCH_EXIT_CODE;
-            return;
-          }
-          handleCommandError(err);
-        }
-      }),
-  );
-}
-
-export async function connectCloud(remoteUrl: string, opts: CloudConnectOptions = {}): Promise<CloudConnection> {
-  const ctx = resolveCommandContext(opts);
-  const discovery = await discoverUpstream(remoteUrl);
-  assertDiscoveryCompatible(discovery);
-  const source = createSourceIdentity();
-  const token = await authorizeConnection(discovery, source, {
-    noBrowser: Boolean(opts.noBrowser),
-  });
-  const targetOrigin = discovery.stack.origin.replace(/\/+$/u, "");
-  const targetHost = new URL(targetOrigin).host;
-  const now = new Date().toISOString();
-  const connection = upsertCloudConnection({
-    id: connectionId(targetOrigin),
-    remoteUrl,
-    targetOrigin,
-    targetHost,
-    stackId: discovery.stack.id,
-    stackSlug: discovery.stack.slug ?? null,
-    stackDisplayName: discovery.stack.displayName ?? null,
-    targetCompanyId: discovery.stack.companyId,
-    accessToken: token.accessToken,
-    token: token.token,
-    privateKeyPem: source.privateKeyPem,
-    sourcePublicKey: source.sourcePublicKey,
-    sourceInstanceId: source.sourceInstanceId,
-    sourceInstanceFingerprint: source.sourceInstanceFingerprint,
-    scopes: token.scopes ?? token.token.scopes ?? CLOUD_SYNC_SCOPES,
-    createdAt: now,
-    updatedAt: now,
-  });
-
-  if (ctx.json) {
-    printOutput(redactConnection(connection), { json: true });
-  } else {
-    console.log(pc.bold("Connected to Paperclip Cloud"));
-    console.log(`stack=${connection.stackDisplayName ?? connection.stackSlug ?? connection.stackId}`);
-    console.log(`origin=${connection.targetOrigin}`);
-    console.log(`company=${connection.targetCompanyId}`);
-  }
-  return connection;
-}
-
-export async function pushCloud(opts: CloudPushOptions): Promise<unknown> {
-  const ctx = resolveCommandContext(opts, { requireCompany: false });
-  const localCompanyId = requiredString(opts.company, "--company");
-  await assertCloudSyncEnabled(ctx.api.get<InstanceExperimentalSettings>("/api/instance/settings/experimental"));
-  const connection = getCloudConnection(opts.remoteUrl);
-  if (!connection) {
-    throw new Error("No cloud connection found. Run `paperclipai cloud connect <remote-url>` first.");
-  }
-
-  const discovery = await discoverUpstream(connection.targetOrigin);
-  assertDiscoveryCompatible(discovery);
-  const bundle = await buildBundleFromLocalCompany({
-    localCompanyId,
-    connection,
-    discovery,
-    localApi: ctx.api,
-    maxEntitiesPerChunk: opts.maxEntitiesPerChunk,
-    mode: opts.dryRun ? "preview" : "apply",
-  });
-  const coordinator = new LocalUpstreamPushCoordinator({
-    targetOrigin: connection.targetOrigin,
-    paperclipCompanyId: connection.targetCompanyId,
-    headers: ({ method, path }) => cloudProofHeaders(connection, method, path),
-  });
-
-  const result = opts.dryRun ? await coordinator.preview(bundle) : await coordinator.apply(bundle);
-  const runId = getRunId(result);
-  const events = !opts.dryRun && runId ? await coordinator.events(runId).catch(() => null) : null;
-  const summary = summarizeResult(result);
-  const conflictCount = summary.conflict + summary.staleMapping;
-
-  if (ctx.json) {
-    printOutput({ result, events }, { json: true });
-  } else {
-    console.log(pc.bold(opts.dryRun ? "Cloud Push Preview" : "Cloud Push Applied"));
-    console.log(`run=${runId ?? "-"}`);
-    console.log(`manifest=${bundle.manifest.manifestHash}`);
-    console.log(
-      `create=${summary.create} update=${summary.update} adopt=${summary.adopt} ` +
-        `skip=${summary.skip} conflict=${summary.conflict} staleMapping=${summary.staleMapping}`,
-    );
-    printWarnings(result);
-    printConflicts(result);
-    printEvents(events);
-  }
-
-  if (conflictCount > 0) {
-    process.exitCode = CLOUD_SYNC_CONFLICT_EXIT_CODE;
-  }
-  return result;
-}
-
-export async function discoverUpstream(remoteUrl: string): Promise<UpstreamDiscovery> {
-  const base = new URL(remoteUrl);
-  const discoveryUrl = new URL("/.well-known/paperclip-upstream", base);
-  return requestCloudJson<UpstreamDiscovery>(discoveryUrl.toString(), { method: "GET" });
-}
-
-export function assertDiscoveryCompatible(discovery: UpstreamDiscovery): void {
-  if (discovery.schema !== "paperclip-upstream-discovery-v1") {
-    throw new Error("Remote URL is not a Paperclip Cloud upstream target.");
-  }
-  if (discovery.transfer.supportedSchemaMajor !== upstreamTransferSchema.major) {
-    throw new Error(
-      `Cloud upstream schema mismatch: local major ${upstreamTransferSchema.major}, remote supports ${discovery.transfer.supportedSchemaMajor}.`,
-    );
-  }
-  if (!discovery.transfer.featureFlags?.includes("cloud_sync")) {
-    throw new Error("Remote Paperclip Cloud stack does not advertise the cloud_sync transfer flag.");
-  }
-}
-
-export function resolveDeviceCodeExpiresAt(expiresAt: string | undefined, nowMs = Date.now()): number {
-  const parsed = typeof expiresAt === "string" ? Date.parse(expiresAt) : NaN;
-  return Number.isFinite(parsed) ? parsed : nowMs + DEVICE_CODE_FALLBACK_EXPIRES_MS;
-}
-
-export async function buildBundleFromLocalCompany(input: {
-  localCompanyId: string;
-  connection: CloudConnection;
-  discovery: UpstreamDiscovery;
-  localApi: {
-    post<T>(path: string, body?: unknown): Promise<T | null>;
-  };
-  maxEntitiesPerChunk?: number;
-  mode: "preview" | "apply";
-}): Promise<LocalUpstreamExportBundle> {
-  const exported = await input.localApi.post<CompanyPortabilityExportResult>(
-    `/api/companies/${input.localCompanyId}/export`,
-    {
-      include: {
-        company: true,
-        agents: true,
-        projects: true,
-        issues: true,
-        skills: true,
-      },
-      expandReferencedSkills: true,
-    },
-  );
-  if (!exported) throw new Error("Local company export returned no data.");
-
-  const sourceHash = normalizedContentHash({
-    manifest: exported.manifest,
-    files: exported.files,
-  });
-  const source: UpstreamTransferManifestSource = {
-    sourceInstanceId: input.connection.sourceInstanceId,
-    sourceCompanyId: input.localCompanyId,
-    sourceInstanceKeyFingerprint: input.connection.sourceInstanceFingerprint,
-    exporterVersion: "paperclipai-cli-cloud-v1",
-    sourceSchemaVersion: "paperclip-local-portability-v1",
-  };
-  const target: UpstreamTransferManifestTarget = {
-    targetStackId: input.discovery.stack.id,
-    targetCompanyId: input.discovery.stack.companyId,
-    targetOrigin: input.discovery.stack.origin,
-    supportedSchemaMajor: input.discovery.transfer.supportedSchemaMajor,
-  };
-  const entities = buildEntitiesFromPortableExport(input.localCompanyId, input.connection.sourceInstanceId, exported);
-  const idempotencyKey = [
-    input.mode,
-    input.connection.sourceInstanceId,
-    input.localCompanyId,
-    input.discovery.stack.id,
-    sourceHash,
-  ].join(":");
-  return buildLocalUpstreamExportBundle({
-    source,
-    target,
-    runId: `local-${input.mode}-${shortHash(idempotencyKey)}`,
-    idempotencyKey,
-    entities,
-    warnings: exported.warnings.map((message): UpstreamTransferWarning => ({
-      code: "local_company_export_warning",
-      severity: "warning",
-      message,
-    })),
-    featureFlags: ["cloud_sync"],
-    maxEntitiesPerChunk: input.maxEntitiesPerChunk,
-  });
-}
-
-async function authorizeConnection(
-  discovery: UpstreamDiscovery,
-  source: ReturnType<typeof createSourceIdentity>,
-  opts: { noBrowser: boolean },
-): Promise<TokenResponse> {
-  if (!opts.noBrowser && canOpenBrowser() && discovery.auth.pkce) {
-    try {
-      return await authorizeWithBrowser(discovery, source);
-    } catch (error) {
-      console.error(pc.yellow(`Browser authorization failed; falling back to device-code flow. ${errorMessage(error)}`));
-    }
-  }
-  if (!discovery.auth.deviceCode) {
-    throw new Error("Remote Paperclip Cloud stack does not support device-code authorization.");
-  }
-  return authorizeWithDeviceCode(discovery, source, { openBrowser: !opts.noBrowser && canOpenBrowser() });
-}
-
-async function authorizeWithBrowser(
-  discovery: UpstreamDiscovery,
-  source: ReturnType<typeof createSourceIdentity>,
-): Promise<TokenResponse> {
-  const pkce = discovery.auth.pkce;
-  if (!pkce) throw new Error("Remote did not advertise PKCE authorization.");
-  const callback = await startPkceCallbackServer();
-  const verifier = randomBytes(32).toString("base64url");
-  const challenge = createHash("sha256").update(verifier).digest("base64url");
-  const state = randomUUID();
-  const authorizeUrl = new URL(pkce.authorizeUrl);
-  authorizeUrl.searchParams.set("redirectUri", callback.redirectUri);
-  authorizeUrl.searchParams.set("state", state);
-  authorizeUrl.searchParams.set("codeChallenge", challenge);
-  authorizeUrl.searchParams.set("codeChallengeMethod", "S256");
-  authorizeUrl.searchParams.set("sourceInstanceId", source.sourceInstanceId);
-  authorizeUrl.searchParams.set("sourceInstanceFingerprint", source.sourceInstanceFingerprint);
-  authorizeUrl.searchParams.set("sourcePublicKey", source.sourcePublicKey);
-  authorizeUrl.searchParams.set("scopes", CLOUD_SYNC_SCOPES.join(" "));
-
-  try {
-    console.error(`Open this URL to approve cloud sync:\n${authorizeUrl.toString()}`);
-    if (!openUrl(authorizeUrl.toString())) {
-      throw new Error("Could not open a browser.");
-    }
-    const code = await callback.waitForCode(state);
-    return requestCloudJson<TokenResponse>(pkce.tokenUrl, {
-      method: "POST",
-      body: JSON.stringify({
-        grantType: "authorization_code",
-        code,
-        redirectUri: callback.redirectUri,
-        codeVerifier: verifier,
-      }),
-    });
-  } finally {
-    await callback.close();
-  }
-}
-
-async function authorizeWithDeviceCode(
-  discovery: UpstreamDiscovery,
-  source: ReturnType<typeof createSourceIdentity>,
-  opts: { openBrowser: boolean },
-): Promise<TokenResponse> {
-  const device = discovery.auth.deviceCode;
-  if (!device) throw new Error("Remote did not advertise device-code authorization.");
-  const response = await requestCloudJson<{
-    deviceCode: string;
-    userCode: string;
-    verificationUri: string;
-    expiresAt?: string;
-    intervalSeconds?: number;
-  }>(device.deviceCodeUrl, {
-    method: "POST",
-    body: JSON.stringify({
-      stackId: discovery.stack.id,
-      sourceInstanceId: source.sourceInstanceId,
-      sourceInstanceFingerprint: source.sourceInstanceFingerprint,
-      sourcePublicKey: source.sourcePublicKey,
-      scopes: CLOUD_SYNC_SCOPES,
-    }),
-  });
-  console.error(pc.bold("Cloud device authorization required"));
-  console.error(`Open: ${response.verificationUri}`);
-  console.error(`Code: ${response.userCode}`);
-  if (opts.openBrowser) openUrl(response.verificationUri);
-
-  const expiresAt = resolveDeviceCodeExpiresAt(response.expiresAt);
-  const intervalMs = Math.max(500, (response.intervalSeconds ?? 5) * 1000);
-  while (Date.now() < expiresAt) {
-    await sleep(intervalMs);
-    try {
-      return await requestCloudJson<TokenResponse>(device.tokenUrl, {
-        method: "POST",
-        body: JSON.stringify({
-          grantType: "device_code",
-          deviceCode: response.deviceCode,
-        }),
-      });
-    } catch (error) {
-      if (error instanceof CloudAuthRequestError && error.body && typeof error.body === "object") {
-        const code = (error.body as { error?: unknown }).error;
-        if (code === "authorization_pending") continue;
-      }
-      throw error;
-    }
-  }
-  throw new Error("Device-code authorization expired before it was approved.");
-}
-
-function buildEntitiesFromPortableExport(
-  localCompanyId: string,
-  sourceInstanceId: string,
-  exported: CompanyPortabilityExportResult,
-): LocalUpstreamExportEntityInput[] {
-  const companyKey: SourceEntityKey = {
-    sourceInstanceId,
-    sourceCompanyId: localCompanyId,
-    sourceEntityType: "company",
-    sourceEntityId: localCompanyId,
-    sourceNaturalKey: exported.manifest.company?.name ?? localCompanyId,
-  };
-  const entities: LocalUpstreamExportEntityInput[] = [
-    {
-      key: companyKey,
-      body: {
-        kind: "paperclip_company_portability_manifest",
-        manifest: exported.manifest,
-        rootPath: exported.rootPath,
-        paperclipExtensionPath: exported.paperclipExtensionPath,
-        fileCount: Object.keys(exported.files).length,
-      },
-      conflictKeys: [`company:${companyKey.sourceNaturalKey ?? localCompanyId}`],
-    },
-  ];
-
-  for (const [filePath, entry] of Object.entries(exported.files).sort(([left], [right]) => left.localeCompare(right))) {
-    entities.push({
-      key: {
-        sourceInstanceId,
-        sourceCompanyId: localCompanyId,
-        sourceEntityType: "company_setting",
-        sourceEntityId: shortHash(filePath),
-        sourceNaturalKey: filePath,
-      },
-      body: {
-        kind: "paperclip_portable_file",
-        path: filePath,
-        entry: normalizePortableFileEntry(entry),
-      },
-      dependencies: [companyKey],
-      conflictKeys: [`portable_file:${filePath}`],
-    });
-  }
-  return entities;
-}
-
-function normalizePortableFileEntry(entry: CompanyPortabilityFileEntry): Record<string, unknown> {
-  if (typeof entry === "string") {
-    return { encoding: "utf8", data: entry };
-  }
-  return { ...entry };
-}
-
-async function assertCloudSyncEnabled(settingsPromise: Promise<InstanceExperimentalSettings | null>): Promise<void> {
-  const settings = await settingsPromise;
-  if (settings?.enableCloudSync !== true) {
-    throw new Error(
-      "Cloud sync is disabled. Enable the cloud sync experimental setting before running `paperclipai cloud push`.",
-    );
-  }
-}
-
-function cloudProofHeaders(connection: CloudConnection, method: string, pathAndSearch: string): Record<string, string> {
-  const timestamp = new Date().toISOString();
-  const nonce = randomUUID();
-  const payload = [
-    method,
-    connection.targetHost.toLowerCase(),
-    pathAndSearch,
-    connection.token.id,
-    connection.sourceInstanceId,
-    timestamp,
-    nonce,
-  ].join("\n");
-  return {
-    Authorization: `Bearer ${connection.accessToken}`,
-    "X-Paperclip-Upstream-Source-Instance-Id": connection.sourceInstanceId,
-    "X-Paperclip-Upstream-Proof-Timestamp": timestamp,
-    "X-Paperclip-Upstream-Proof-Nonce": nonce,
-    "X-Paperclip-Upstream-Proof-Signature": sign(
-      null,
-      Buffer.from(payload, "utf8"),
-      connection.privateKeyPem,
-    ).toString("base64url"),
-  };
-}
-
-async function requestCloudJson<T>(url: string, init: RequestInit): Promise<T> {
-  const headers = new Headers(init.headers);
-  headers.set("accept", "application/json");
-  if (init.body !== undefined && !headers.has("content-type")) {
-    headers.set("content-type", "application/json");
-  }
-  const response = await fetch(url, { ...init, headers });
-  const text = await response.text();
-  const parsed = text.trim() ? JSON.parse(text) as unknown : {};
-  if (!response.ok) {
-    const message = typeof parsed === "object" && parsed !== null && "error" in parsed
-      ? String((parsed as { error: unknown }).error)
-      : `Cloud request failed with ${response.status}`;
-    throw new CloudAuthRequestError(response.status, message, parsed);
-  }
-  return parsed as T;
-}
-
-function createSourceIdentity() {
-  const { publicKey, privateKey } = generateKeyPairSync("ed25519");
-  const sourcePublicKey = publicKey.export({ type: "spki", format: "pem" }).toString();
-  const sourceInstanceFingerprint = `sha256:${createHash("sha256")
-    .update(publicKey.export({ type: "spki", format: "der" }))
-    .digest("hex")}`;
-  return {
-    sourceInstanceId: `paperclip-local-${resolvePaperclipInstanceId()}`,
-    sourceInstanceFingerprint,
-    sourcePublicKey,
-    privateKeyPem: privateKey.export({ type: "pkcs8", format: "pem" }).toString(),
-  };
-}
-
-async function startPkceCallbackServer(): Promise<{
-  redirectUri: string;
-  waitForCode: (state: string) => Promise<string>;
-  close: () => Promise<void>;
-}> {
-  let resolveCode: ((code: string) => void) | null = null;
-  let rejectCode: ((error: Error) => void) | null = null;
-  let expectedState = "";
-  const codePromise = new Promise<string>((resolve, reject) => {
-    resolveCode = resolve;
-    rejectCode = reject;
-  });
-  const server = createServer((req, res) => {
-    const url = new URL(req.url ?? "/", "http://127.0.0.1");
-    const code = url.searchParams.get("code");
-    const state = url.searchParams.get("state");
-    if (!code || state !== expectedState) {
-      res.writeHead(400, { "Content-Type": "text/plain" });
-      res.end("Paperclip Cloud authorization failed. You can close this tab.");
-      rejectCode?.(new Error("Authorization callback was missing a valid code or state."));
-      return;
-    }
-    res.writeHead(200, { "Content-Type": "text/plain" });
-    res.end("Paperclip Cloud authorization complete. You can close this tab.");
-    resolveCode?.(code);
-  });
-  await listenOnLoopback(server);
-  const address = server.address();
-  if (typeof address !== "object" || !address?.port) {
-    throw new Error("Failed to start local authorization callback server.");
-  }
-  return {
-    redirectUri: `http://127.0.0.1:${address.port}/cloud/callback`,
-    waitForCode: (state: string) => {
-      expectedState = state;
-      return codePromise;
-    },
-    close: () => closeServer(server),
-  };
-}
-
-function listenOnLoopback(server: Server): Promise<void> {
-  return new Promise((resolve, reject) => {
-    server.once("error", reject);
-    server.listen(0, "127.0.0.1", () => {
-      server.off("error", reject);
-      resolve();
-    });
-  });
-}
-
-function closeServer(server: Server): Promise<void> {
-  return new Promise((resolve, reject) => {
-    server.close((error) => error ? reject(error) : resolve());
-  });
-}
-
-function canOpenBrowser(): boolean {
-  if (process.platform === "darwin" || process.platform === "win32") return true;
-  return Boolean(process.env.DISPLAY || process.env.WAYLAND_DISPLAY);
-}
-
-function summarizeResult(result: unknown): {
-  create: number;
-  update: number;
-  adopt: number;
-  skip: number;
-  conflict: number;
-  staleMapping: number;
-} {
-  const summary = asRecord(asRecord(result)?.summary);
-  return {
-    create: numberValue(summary?.create),
-    update: numberValue(summary?.update),
-    adopt: numberValue(summary?.adopt),
-    skip: numberValue(summary?.skip),
-    conflict: numberValue(summary?.conflict),
-    staleMapping: numberValue(summary?.staleMapping),
-  };
-}
-
-function printWarnings(result: unknown): void {
-  const warnings = Array.isArray(asRecord(result)?.warnings) ? asRecord(result)?.warnings as unknown[] : [];
-  for (const warning of warnings) {
-    const record = asRecord(warning);
-    console.log(pc.yellow(`warning=${record?.code ?? "warning"} ${record?.message ?? ""}`.trim()));
-  }
-}
-
-function printConflicts(result: unknown): void {
-  const conflicts = Array.isArray(asRecord(result)?.conflicts) ? asRecord(result)?.conflicts as unknown[] : [];
-  for (const conflict of conflicts.slice(0, 10)) {
-    const record = asRecord(conflict);
-    console.log(pc.red(`conflict=${record?.conflictKind ?? "target_conflict"} target=${record?.targetEntityId ?? "-"}`));
-  }
-  if (conflicts.length > 10) console.log(pc.red(`conflicts_truncated=${conflicts.length - 10}`));
-}
-
-function printEvents(events: unknown): void {
-  const rows = Array.isArray(asRecord(events)?.events) ? asRecord(events)?.events as unknown[] : [];
-  for (const row of rows.slice(-10)) {
-    const event = asRecord(row);
-    console.log(pc.dim(`event=${event?.action ?? "-"} target=${event?.targetEntityId ?? "-"}`));
-  }
-}
-
-function getRunId(result: unknown): string | null {
-  const run = asRecord(asRecord(result)?.run);
-  return typeof run?.id === "string" ? run.id : null;
-}
-
-function redactConnection(connection: CloudConnection): Record<string, unknown> {
-  return {
-    id: connection.id,
-    remoteUrl: connection.remoteUrl,
-    targetOrigin: connection.targetOrigin,
-    stackId: connection.stackId,
-    targetCompanyId: connection.targetCompanyId,
-    scopes: connection.scopes,
-    expiresAt: connection.token.expiresAt,
-  };
-}
-
-function connectionId(targetOrigin: string): string {
-  return `cloud-${shortHash(targetOrigin)}`;
-}
-
-function shortHash(value: string): string {
-  return createHash("sha256").update(value).digest("hex").slice(0, 16);
-}
-
-function requiredString(value: unknown, label: string): string {
-  if (typeof value === "string" && value.trim()) return value.trim();
-  throw new Error(`${label} is required.`);
-}
-
-function numberValue(value: unknown): number {
-  return typeof value === "number" && Number.isFinite(value) ? value : 0;
-}
-
-function asRecord(value: unknown): Record<string, unknown> | null {
-  return typeof value === "object" && value !== null && !Array.isArray(value)
-    ? value as Record<string, unknown>
-    : null;
-}
-
-function isSchemaMismatchError(error: unknown): boolean {
-  if (error instanceof UpstreamImportRequestError) {
-    return JSON.stringify(error.body).toLowerCase().includes("schema");
-  }
-  return error instanceof Error && error.message.toLowerCase().includes("schema mismatch");
-}
-
-function errorMessage(error: unknown): string {
-  return error instanceof Error ? error.message : String(error);
-}
-
-function sleep(ms: number): Promise<void> {
-  return new Promise((resolve) => setTimeout(resolve, ms));
-}
-
-export const cloudCommandExitCodes = {
-  conflict: CLOUD_SYNC_CONFLICT_EXIT_CODE,
-  schemaMismatch: CLOUD_SYNC_SCHEMA_MISMATCH_EXIT_CODE,
-} as const;

cli/src/commands/client/issue.ts

@@ -61,7 +61,6 @@ interface IssueUpdateOptions extends BaseClientOptions {
 interface IssueCommentOptions extends BaseClientOptions {
   body: string;
   reopen?: boolean;
-  resume?: boolean;
 }
 
 interface IssueCheckoutOptions extends BaseClientOptions {
@@ -242,14 +241,12 @@ export function registerIssueCommands(program: Command): void {
       .argument("<issueId>", "Issue ID")
       .requiredOption("--body <text>", "Comment body")
       .option("--reopen", "Reopen if issue is done/cancelled")
-      .option("--resume", "Request explicit follow-up and wake the assignee when resumable")
       .action(async (issueId: string, opts: IssueCommentOptions) => {
         try {
           const ctx = resolveCommandContext(opts);
           const payload = addIssueCommentSchema.parse({
             body: opts.body,
             reopen: opts.reopen,
-            resume: opts.resume,
           });
           const comment = await ctx.api.post<IssueComment>(`/api/issues/${issueId}/comments`, payload);
           printOutput(comment, { json: ctx.json });

cli/src/commands/client/plugin.ts

@@ -1,11 +1,5 @@
 import path from "node:path";
-import { existsSync } from "node:fs";
-import { Command, Option } from "commander";
-import {
-  scaffoldPluginProject,
-  shellQuote,
-  type ScaffoldPluginOptions,
-} from "../../../../packages/plugins/create-paperclip-plugin/src/index.js";
+import { Command } from "commander";
 import pc from "picocolors";
 import {
   addCommonClientOptions,
@@ -45,101 +39,28 @@ interface PluginInstallOptions extends BaseClientOptions {
   version?: string;
 }
 
-interface PluginInstallRequest {
-  packageName: string;
-  version?: string;
-  isLocalPath: boolean;
-}
-
 interface PluginUninstallOptions extends BaseClientOptions {
   force?: boolean;
 }
 
-interface PluginInitOptions extends BaseClientOptions {
-  output?: string;
-  template?: ScaffoldPluginOptions["template"];
-  category?: ScaffoldPluginOptions["category"];
-  displayName?: string;
-  description?: string;
-  author?: string;
-  sdkPath?: string;
-}
-
-interface PluginInitResult {
-  outputDir: string;
-  nextCommands: string[];
-}
-
 // ---------------------------------------------------------------------------
 // Helpers
 // ---------------------------------------------------------------------------
 
-function expandHomePath(packageArg: string): string {
-  if (!packageArg.startsWith("~")) return packageArg;
-  const home = process.env.HOME ?? process.env.USERPROFILE ?? "";
-  return path.resolve(home, packageArg.slice(1).replace(/^[\\/]/, ""));
-}
-
-function hasLocalPathSyntax(packageArg: string): boolean {
-  return (
-    path.isAbsolute(packageArg) ||
-    packageArg.startsWith("./") ||
-    packageArg.startsWith("../") ||
-    packageArg.startsWith("~") ||
-    packageArg.startsWith(".\\") ||
-    packageArg.startsWith("..\\")
-  );
-}
-
-function isExistingRelativePath(
-  packageArg: string,
-  cwd: string,
-  pathExists: (targetPath: string) => boolean,
-): boolean {
-  if (packageArg.trim() === "") return false;
-  if (hasLocalPathSyntax(packageArg)) return false;
-  return pathExists(path.resolve(cwd, packageArg));
-}
-
 /**
  * Resolve a local path argument to an absolute path so the server can find the
  * plugin on disk regardless of where the user ran the CLI.
  */
-function resolvePackageArg(packageArg: string, isLocal: boolean, cwd = process.cwd()): string {
+function resolvePackageArg(packageArg: string, isLocal: boolean): string {
   if (!isLocal) return packageArg;
+  // Already absolute
   if (path.isAbsolute(packageArg)) return packageArg;
-  if (packageArg.startsWith("~")) return expandHomePath(packageArg);
-  return path.resolve(cwd, packageArg);
-}
-
-export function buildPluginInstallRequest(
-  packageArg: string,
-  opts: Pick<PluginInstallOptions, "local" | "version"> = {},
-  deps: { cwd?: string; existsSync?: (targetPath: string) => boolean } = {},
-): PluginInstallRequest {
-  const cwd = deps.cwd ?? process.cwd();
-  const pathExists = deps.existsSync ?? existsSync;
-  const isLocal =
-    opts.local ||
-    hasLocalPathSyntax(packageArg) ||
-    (opts.version ? false : isExistingRelativePath(packageArg, cwd, pathExists));
-
-  if (isLocal && opts.version) {
-    throw new Error("--version is only supported for npm package installs, not local plugin paths.");
+  // Expand leading ~ to home directory
+  if (packageArg.startsWith("~")) {
+    const home = process.env.HOME ?? process.env.USERPROFILE ?? "";
+    return path.resolve(home, packageArg.slice(1).replace(/^[\\/]/, ""));
   }
-
-  return {
-    packageName: resolvePackageArg(packageArg, Boolean(isLocal), cwd),
-    version: opts.version,
-    isLocalPath: Boolean(isLocal),
-  };
-}
-
-export function renderLocalPluginInstallHint(packagePath: string): string {
-  return [
-    pc.dim("Local plugin installs run trusted local code from your machine."),
-    pc.dim(`Keep ${pc.cyan("pnpm dev")} running in ${packagePath}; Paperclip watches rebuilt dist output and reloads the plugin worker.`),
-  ].join("\n");
+  return path.resolve(process.cwd(), packageArg);
 }
 
 function formatPlugin(p: PluginRecord): string {
@@ -166,58 +87,6 @@ function formatPlugin(p: PluginRecord): string {
   return parts.join("  ");
 }
 
-function packageToDirName(pluginName: string): string {
-  return pluginName.replace(/^@[^/]+\//, "");
-}
-
-export function buildPluginInitScaffoldOptions(
-  packageName: string,
-  opts: PluginInitOptions,
-  cwd = process.cwd(),
-): ScaffoldPluginOptions {
-  const outputRoot = path.resolve(cwd, opts.output ?? ".");
-  const outputDir = path.resolve(outputRoot, packageToDirName(packageName));
-
-  return {
-    pluginName: packageName,
-    outputDir,
-    template: opts.template,
-    category: opts.category,
-    displayName: opts.displayName,
-    description: opts.description,
-    author: opts.author,
-    sdkPath: opts.sdkPath,
-  };
-}
-
-export function buildPluginInitNextCommands(outputDir: string): string[] {
-  const quotedOutputDir = shellQuote(outputDir);
-  return [
-    `cd ${quotedOutputDir}`,
-    "pnpm install",
-    "pnpm dev",
-    `paperclipai plugin install ${quotedOutputDir}`,
-  ];
-}
-
-export function renderPluginInitSuccess(result: PluginInitResult): string {
-  return [
-    pc.green(`✓ Created plugin scaffold at ${result.outputDir}`),
-    "",
-    "Next commands:",
-    ...result.nextCommands.map((command) => `  ${pc.cyan(command)}`),
-  ].join("\n");
-}
-
-export function runPluginInitCommand(packageName: string, opts: PluginInitOptions): PluginInitResult {
-  const scaffoldOptions = buildPluginInitScaffoldOptions(packageName, opts);
-  const outputDir = scaffoldPluginProject(scaffoldOptions);
-  return {
-    outputDir,
-    nextCommands: buildPluginInitNextCommands(outputDir),
-  };
-}
-
 // ---------------------------------------------------------------------------
 // Command registration
 // ---------------------------------------------------------------------------
@@ -225,43 +94,6 @@ export function runPluginInitCommand(packageName: string, opts: PluginInitOption
 export function registerPluginCommands(program: Command): void {
   const plugin = program.command("plugin").description("Plugin lifecycle management");
 
-  // -------------------------------------------------------------------------
-  // plugin init <package-name>
-  // -------------------------------------------------------------------------
-  addCommonClientOptions(
-    plugin
-      .command("init <packageName>")
-      .description("Scaffold a local Paperclip plugin project")
-      .option("--output <dir>", "Directory to create the plugin folder in")
-      .addOption(
-        new Option("--template <template>", "Starter template")
-          .choices(["default", "connector", "workspace", "environment"])
-          .default("default"),
-      )
-      .addOption(
-        new Option("--category <category>", "Manifest category")
-          .choices(["connector", "workspace", "automation", "ui", "environment"]),
-      )
-      .option("--display-name <name>", "Manifest display name")
-      .option("--description <description>", "Manifest description")
-      .option("--author <author>", "Manifest author")
-      .option("--sdk-path <path>", "Local @paperclipai/plugin-sdk package path")
-      .action((packageName: string, opts: PluginInitOptions) => {
-        try {
-          const result = runPluginInitCommand(packageName, opts);
-
-          if (opts.json) {
-            printOutput(result, { json: true });
-            return;
-          }
-
-          console.log(renderPluginInitSuccess(result));
-        } catch (err) {
-          handleCommandError(err);
-        }
-      }),
-  );
-
   // -------------------------------------------------------------------------
   // plugin list
   // -------------------------------------------------------------------------
@@ -315,19 +147,31 @@ export function registerPluginCommands(program: Command): void {
         try {
           const ctx = resolveCommandContext(opts);
 
-          const installRequest = buildPluginInstallRequest(packageArg, opts);
+          // Auto-detect local paths: starts with . or / or ~ or is an absolute path
+          const isLocal =
+            opts.local ||
+            packageArg.startsWith("./") ||
+            packageArg.startsWith("../") ||
+            packageArg.startsWith("/") ||
+            packageArg.startsWith("~");
+
+          const resolvedPackage = resolvePackageArg(packageArg, isLocal);
 
           if (!ctx.json) {
             console.log(
               pc.dim(
-                installRequest.isLocalPath
-                  ? `Installing plugin from local path: ${installRequest.packageName}`
-                  : `Installing plugin: ${installRequest.packageName}${opts.version ? `@${opts.version}` : ""}`,
+                isLocal
+                  ? `Installing plugin from local path: ${resolvedPackage}`
+                  : `Installing plugin: ${resolvedPackage}${opts.version ? `@${opts.version}` : ""}`,
               ),
             );
           }
 
-          const installedPlugin = await ctx.api.post<PluginRecord>("/api/plugins/install", installRequest);
+          const installedPlugin = await ctx.api.post<PluginRecord>("/api/plugins/install", {
+            packageName: resolvedPackage,
+            version: opts.version,
+            isLocalPath: isLocal,
+          });
 
           if (ctx.json) {
             printOutput(installedPlugin, { json: true });
@@ -348,10 +192,6 @@ export function registerPluginCommands(program: Command): void {
           if (installedPlugin.lastError) {
             console.log(pc.red(`  Warning: ${installedPlugin.lastError}`));
           }
-
-          if (installRequest.isLocalPath) {
-            console.log(renderLocalPluginInstallHint(installRequest.packageName));
-          }
         } catch (err) {
           handleCommandError(err);
         }

cli/src/commands/client/secrets.ts

@@ -1,501 +0,0 @@
-import { Command } from "commander";
-import pc from "picocolors";
-import type {
-  Agent,
-  AgentEnvConfig,
-  CompanyPortabilityEnvInput,
-  CompanyPortabilityExportPreviewResult,
-  CompanyPortabilityInclude,
-  CompanySecret,
-  EnvBinding,
-  SecretProvider,
-  SecretProviderDescriptor,
-} from "@paperclipai/shared";
-import {
-  addCommonClientOptions,
-  formatInlineRecord,
-  handleCommandError,
-  printOutput,
-  resolveCommandContext,
-  type BaseClientOptions,
-} from "./common.js";
-
-interface SecretListOptions extends BaseClientOptions {
-  companyId?: string;
-}
-
-interface SecretDeclarationsOptions extends BaseClientOptions {
-  companyId?: string;
-  include?: string;
-  kind?: "all" | "secret" | "plain";
-}
-
-interface SecretCreateOptions extends BaseClientOptions {
-  companyId?: string;
-  name?: string;
-  key?: string;
-  provider?: SecretProvider;
-  value?: string;
-  valueEnv?: string;
-  description?: string;
-}
-
-interface SecretLinkOptions extends BaseClientOptions {
-  companyId?: string;
-  name?: string;
-  key?: string;
-  provider?: SecretProvider;
-  externalRef?: string;
-  providerVersionRef?: string;
-  description?: string;
-}
-
-interface SecretDoctorOptions extends BaseClientOptions {
-  companyId?: string;
-}
-
-interface SecretMigrateInlineEnvOptions extends BaseClientOptions {
-  companyId?: string;
-  apply?: boolean;
-}
-
-interface SecretProviderHealth {
-  provider: SecretProvider;
-  status: "ok" | "warn" | "error";
-  message: string;
-  warnings?: string[];
-  backupGuidance?: string[];
-  details?: Record<string, unknown>;
-}
-
-interface SecretProviderHealthResponse {
-  providers: SecretProviderHealth[];
-}
-
-export interface InlineSecretMigrationCandidate {
-  agentId: string;
-  agentName: string;
-  envKey: string;
-  secretName: string;
-  existingSecretId: string | null;
-}
-
-const SENSITIVE_ENV_KEY_RE =
-  /(^token$|[-_]?token$|api[-_]?key|access[-_]?token|auth(?:_?token)?|authorization|bearer|secret|passwd|password|credential|jwt|private[-_]?key|cookie|connectionstring)/i;
-
-const DEFAULT_DECLARATION_INCLUDE: CompanyPortabilityInclude = {
-  company: true,
-  agents: true,
-  projects: true,
-  issues: false,
-  skills: false,
-};
-
-export function parseSecretsInclude(input: string | undefined): CompanyPortabilityInclude {
-  if (!input?.trim()) return { ...DEFAULT_DECLARATION_INCLUDE };
-  const values = input.split(",").map((part) => part.trim().toLowerCase()).filter(Boolean);
-  const include = {
-    company: values.includes("company"),
-    agents: values.includes("agents"),
-    projects: values.includes("projects"),
-    issues: values.includes("issues") || values.includes("tasks"),
-    skills: values.includes("skills"),
-  };
-  if (!Object.values(include).some(Boolean)) {
-    throw new Error("Invalid --include value. Use one or more of: company,agents,projects,issues,tasks,skills");
-  }
-  return include;
-}
-
-export function isSensitiveEnvKey(key: string): boolean {
-  return SENSITIVE_ENV_KEY_RE.test(key);
-}
-
-export function toPlainEnvValue(binding: unknown): string | null {
-  if (typeof binding === "string") return binding;
-  if (typeof binding !== "object" || binding === null || Array.isArray(binding)) return null;
-  const record = binding as Record<string, unknown>;
-  if (record.type === "plain" && typeof record.value === "string") return record.value;
-  return null;
-}
-
-export function buildInlineMigrationSecretName(agentId: string, key: string): string {
-  return `agent_${agentId.slice(0, 8)}_${key.toLowerCase()}`;
-}
-
-export function collectInlineSecretMigrationCandidates(
-  agents: Agent[],
-  existingSecrets: CompanySecret[],
-): InlineSecretMigrationCandidate[] {
-  const secretByName = new Map(existingSecrets.map((secret) => [secret.name, secret]));
-  const candidates: InlineSecretMigrationCandidate[] = [];
-
-  for (const agent of agents) {
-    const env = asRecord(agent.adapterConfig.env);
-    if (!env) continue;
-    for (const [envKey, binding] of Object.entries(env)) {
-      if (!isSensitiveEnvKey(envKey)) continue;
-      const plain = toPlainEnvValue(binding);
-      if (plain === null || plain.trim().length === 0) continue;
-      const secretName = buildInlineMigrationSecretName(agent.id, envKey);
-      candidates.push({
-        agentId: agent.id,
-        agentName: agent.name,
-        envKey,
-        secretName,
-        existingSecretId: secretByName.get(secretName)?.id ?? null,
-      });
-    }
-  }
-
-  return candidates;
-}
-
-export function buildMigratedAgentEnv(
-  env: Record<string, unknown>,
-  secretIdByEnvKey: Map<string, string>,
-): AgentEnvConfig {
-  const next: AgentEnvConfig = { ...(env as Record<string, EnvBinding>) };
-  for (const [envKey, secretId] of secretIdByEnvKey) {
-    next[envKey] = {
-      type: "secret_ref",
-      secretId,
-      version: "latest",
-    };
-  }
-  return next;
-}
-
-function asRecord(value: unknown): Record<string, unknown> | null {
-  if (typeof value !== "object" || value === null || Array.isArray(value)) return null;
-  return value as Record<string, unknown>;
-}
-
-function readValueFromOptions(opts: SecretCreateOptions): string {
-  if (opts.value !== undefined && opts.valueEnv !== undefined) {
-    throw new Error("Use only one of --value or --value-env.");
-  }
-  if (opts.valueEnv !== undefined) {
-    const value = process.env[opts.valueEnv];
-    if (!value) throw new Error(`Environment variable ${opts.valueEnv} is empty or unset.`);
-    return value;
-  }
-  if (opts.value !== undefined) return opts.value;
-  throw new Error("Secret value is required. Pass --value or --value-env.");
-}
-
-function renderDeclaration(input: CompanyPortabilityEnvInput): Record<string, unknown> {
-  const scope = input.agentSlug
-    ? `agent:${input.agentSlug}`
-    : input.projectSlug
-      ? `project:${input.projectSlug}`
-      : "company";
-  return {
-    key: input.key,
-    scope,
-    kind: input.kind,
-    requirement: input.requirement,
-    portability: input.portability,
-    hasDefault: input.defaultValue !== null && input.defaultValue.length > 0,
-    description: input.description,
-  };
-}
-
-function renderSecret(secret: CompanySecret): Record<string, unknown> {
-  return {
-    id: secret.id,
-    name: secret.name,
-    key: secret.key,
-    provider: secret.provider,
-    status: secret.status,
-    managedMode: secret.managedMode,
-    latestVersion: secret.latestVersion,
-    externalRef: secret.externalRef ? "yes" : "no",
-  };
-}
-
-function printProviderHealth(rows: SecretProviderHealth[], json: boolean): void {
-  if (json) {
-    printOutput(rows, { json: true });
-    return;
-  }
-  if (rows.length === 0) {
-    printOutput([], { json: false });
-    return;
-  }
-  for (const row of rows) {
-    console.log(
-      formatInlineRecord({
-        id: row.provider,
-        status: row.status,
-        message: row.message,
-      }),
-    );
-    for (const warning of row.warnings ?? []) {
-      console.log(pc.yellow(`warning=${warning}`));
-    }
-    const missingConfig = asStringArray(row.details?.missingConfig);
-    if (missingConfig.length > 0) {
-      console.log(pc.dim(`missingConfig=${missingConfig.join(",")}`));
-    }
-    const credentialSource = typeof row.details?.credentialSource === "string"
-      ? row.details.credentialSource
-      : null;
-    if (credentialSource) {
-      console.log(pc.dim(`credentialSource=${credentialSource}`));
-    }
-    const detectedCredentialSources = asStringArray(row.details?.detectedCredentialSources);
-    if (detectedCredentialSources.length > 0) {
-      console.log(pc.dim(`detectedCredentialSources=${detectedCredentialSources.join(",")}`));
-    }
-    for (const guidance of row.backupGuidance ?? []) {
-      console.log(pc.dim(`backup=${guidance}`));
-    }
-  }
-}
-
-function asStringArray(value: unknown): string[] {
-  return Array.isArray(value)
-    ? value.filter((entry): entry is string => typeof entry === "string" && entry.length > 0)
-    : [];
-}
-
-async function migrateInlineEnv(opts: SecretMigrateInlineEnvOptions): Promise<void> {
-  const ctx = resolveCommandContext(opts, { requireCompany: true });
-  const companyId = ctx.companyId!;
-  const agents = (await ctx.api.get<Agent[]>(`/api/companies/${companyId}/agents`)) ?? [];
-  const secrets = (await ctx.api.get<CompanySecret[]>(`/api/companies/${companyId}/secrets`)) ?? [];
-  const candidates = collectInlineSecretMigrationCandidates(agents, secrets);
-
-  if (!opts.apply) {
-    printOutput(
-      {
-        apply: false,
-        agentsToUpdate: new Set(candidates.map((candidate) => candidate.agentId)).size,
-        secretsToCreate: candidates.filter((candidate) => !candidate.existingSecretId).length,
-        secretsToRotate: candidates.filter((candidate) => candidate.existingSecretId).length,
-        candidates,
-      },
-      { json: ctx.json },
-    );
-    if (!ctx.json) {
-      console.log(pc.dim("Re-run with --apply to create/rotate secrets and update agent env bindings."));
-    }
-    return;
-  }
-
-  const createdOrRotated = new Map<string, string>();
-  let createdSecrets = 0;
-  let rotatedSecrets = 0;
-
-  for (const candidate of candidates) {
-    const agent = agents.find((row) => row.id === candidate.agentId);
-    const env = asRecord(agent?.adapterConfig.env);
-    const value = env ? toPlainEnvValue(env[candidate.envKey]) : null;
-    if (!value) continue;
-
-    if (candidate.existingSecretId) {
-      await ctx.api.post(`/api/secrets/${candidate.existingSecretId}/rotate`, { value });
-      createdOrRotated.set(`${candidate.agentId}:${candidate.envKey}`, candidate.existingSecretId);
-      rotatedSecrets += 1;
-      continue;
-    }
-
-    const created = await ctx.api.post<CompanySecret>(`/api/companies/${companyId}/secrets`, {
-      name: candidate.secretName,
-      provider: "local_encrypted",
-      value,
-      description: `Migrated from agent ${candidate.agentId} env ${candidate.envKey}`,
-    });
-    if (!created) throw new Error(`Secret create returned no data for ${candidate.secretName}`);
-    createdOrRotated.set(`${candidate.agentId}:${candidate.envKey}`, created.id);
-    createdSecrets += 1;
-  }
-
-  let updatedAgents = 0;
-  for (const agent of agents) {
-    const env = asRecord(agent.adapterConfig.env);
-    if (!env) continue;
-    const secretIdByEnvKey = new Map<string, string>();
-    for (const [key] of Object.entries(env)) {
-      const secretId = createdOrRotated.get(`${agent.id}:${key}`);
-      if (secretId) secretIdByEnvKey.set(key, secretId);
-    }
-    if (secretIdByEnvKey.size === 0) continue;
-    const adapterConfig = {
-      ...agent.adapterConfig,
-      env: buildMigratedAgentEnv(env, secretIdByEnvKey),
-    };
-    await ctx.api.patch(`/api/agents/${agent.id}`, {
-      adapterConfig,
-      replaceAdapterConfig: true,
-    });
-    updatedAgents += 1;
-  }
-
-  printOutput(
-    {
-      apply: true,
-      updatedAgents,
-      createdSecrets,
-      rotatedSecrets,
-    },
-    { json: ctx.json },
-  );
-}
-
-export function registerSecretCommands(program: Command): void {
-  const secrets = program.command("secrets").description("Secret declaration and provider operations");
-
-  addCommonClientOptions(
-    secrets
-      .command("list")
-      .description("List secret metadata for a company")
-      .requiredOption("-C, --company-id <id>", "Company ID")
-      .action(async (opts: SecretListOptions) => {
-        try {
-          const ctx = resolveCommandContext(opts, { requireCompany: true });
-          const rows = (await ctx.api.get<CompanySecret[]>(`/api/companies/${ctx.companyId}/secrets`)) ?? [];
-          printOutput(ctx.json ? rows : rows.map(renderSecret), { json: ctx.json });
-        } catch (err) {
-          handleCommandError(err);
-        }
-      }),
-  );
-
-  addCommonClientOptions(
-    secrets
-      .command("declarations")
-      .description("List portable env declarations emitted by company export")
-      .requiredOption("-C, --company-id <id>", "Company ID")
-      .option("--include <values>", "Comma-separated include set: company,agents,projects,issues,tasks,skills", "company,agents,projects")
-      .option("--kind <kind>", "Filter declarations: all | secret | plain", "all")
-      .action(async (opts: SecretDeclarationsOptions) => {
-        try {
-          const ctx = resolveCommandContext(opts, { requireCompany: true });
-          const kind = opts.kind ?? "all";
-          if (!["all", "secret", "plain"].includes(kind)) {
-            throw new Error("Invalid --kind value. Use: all, secret, plain");
-          }
-          const preview = await ctx.api.post<CompanyPortabilityExportPreviewResult>(
-            `/api/companies/${ctx.companyId}/exports/preview`,
-            { include: parseSecretsInclude(opts.include) },
-          );
-          const declarations = (preview?.manifest.envInputs ?? [])
-            .filter((entry) => kind === "all" || entry.kind === kind);
-          printOutput(ctx.json ? declarations : declarations.map(renderDeclaration), { json: ctx.json });
-        } catch (err) {
-          handleCommandError(err);
-        }
-      }),
-  );
-
-  addCommonClientOptions(
-    secrets
-      .command("create")
-      .description("Create a Paperclip-managed secret")
-      .requiredOption("-C, --company-id <id>", "Company ID")
-      .requiredOption("--name <name>", "Secret display name")
-      .option("--key <key>", "Portable secret key")
-      .option("--provider <provider>", "Secret provider id")
-      .option("--value <value>", "Secret value")
-      .option("--value-env <name>", "Read secret value from an environment variable")
-      .option("--description <text>", "Description")
-      .action(async (opts: SecretCreateOptions) => {
-        try {
-          const ctx = resolveCommandContext(opts, { requireCompany: true });
-          const created = await ctx.api.post<CompanySecret>(`/api/companies/${ctx.companyId}/secrets`, {
-            name: opts.name,
-            key: opts.key,
-            provider: opts.provider,
-            value: readValueFromOptions(opts),
-            description: opts.description,
-          });
-          printOutput(ctx.json ? created : renderSecret(created!), { json: ctx.json });
-        } catch (err) {
-          handleCommandError(err);
-        }
-      }),
-  );
-
-  addCommonClientOptions(
-    secrets
-      .command("link")
-      .description("Link an external provider-owned secret without storing its value in Paperclip")
-      .requiredOption("-C, --company-id <id>", "Company ID")
-      .requiredOption("--name <name>", "Secret display name")
-      .requiredOption("--provider <provider>", "Secret provider id")
-      .requiredOption("--external-ref <ref>", "Provider secret ARN/name/path/reference")
-      .option("--key <key>", "Portable secret key")
-      .option("--provider-version-ref <ref>", "Provider version id or label")
-      .option("--description <text>", "Description")
-      .action(async (opts: SecretLinkOptions) => {
-        try {
-          const ctx = resolveCommandContext(opts, { requireCompany: true });
-          const created = await ctx.api.post<CompanySecret>(`/api/companies/${ctx.companyId}/secrets`, {
-            name: opts.name,
-            key: opts.key,
-            provider: opts.provider,
-            managedMode: "external_reference",
-            externalRef: opts.externalRef,
-            providerVersionRef: opts.providerVersionRef,
-            description: opts.description,
-          });
-          printOutput(ctx.json ? created : renderSecret(created!), { json: ctx.json });
-        } catch (err) {
-          handleCommandError(err);
-        }
-      }),
-  );
-
-  addCommonClientOptions(
-    secrets
-      .command("doctor")
-      .description("Run secret provider health checks through the Paperclip API")
-      .requiredOption("-C, --company-id <id>", "Company ID")
-      .action(async (opts: SecretDoctorOptions) => {
-        try {
-          const ctx = resolveCommandContext(opts, { requireCompany: true });
-          const health = await ctx.api.get<SecretProviderHealthResponse>(
-            `/api/companies/${ctx.companyId}/secret-providers/health`,
-          );
-          printProviderHealth(health?.providers ?? [], ctx.json);
-        } catch (err) {
-          handleCommandError(err);
-        }
-      }),
-  );
-
-  addCommonClientOptions(
-    secrets
-      .command("providers")
-      .description("List configured secret provider descriptors")
-      .requiredOption("-C, --company-id <id>", "Company ID")
-      .action(async (opts: SecretDoctorOptions) => {
-        try {
-          const ctx = resolveCommandContext(opts, { requireCompany: true });
-          const rows = (await ctx.api.get<SecretProviderDescriptor[]>(
-            `/api/companies/${ctx.companyId}/secret-providers`,
-          )) ?? [];
-          printOutput(rows, { json: ctx.json });
-        } catch (err) {
-          handleCommandError(err);
-        }
-      }),
-  );
-
-  addCommonClientOptions(
-    secrets
-      .command("migrate-inline-env")
-      .description("Migrate inline sensitive agent env values into secret references")
-      .requiredOption("-C, --company-id <id>", "Company ID")
-      .option("--apply", "Persist changes; default is a dry run", false)
-      .action(async (opts: SecretMigrateInlineEnvOptions) => {
-        try {
-          await migrateInlineEnv(opts);
-        } catch (err) {
-          handleCommandError(err);
-        }
-      }),
-  );
-}

cli/src/commands/configure.ts

@@ -54,7 +54,6 @@ function defaultConfig(): PaperclipConfig {
     server: {
       deploymentMode: "local_trusted",
       exposure: "private",
-      bind: "loopback",
       host: "127.0.0.1",
       port: 3100,
       allowedHostnames: [],

cli/src/commands/db-backup.ts

@@ -73,7 +73,7 @@ export async function dbBackupCommand(opts: DbBackupOptions): Promise<void> {
     const result = await runDatabaseBackup({
       connectionString: connection.value,
       backupDir,
-      retention: { dailyDays: retentionDays, weeklyWeeks: 4, monthlyMonths: 1 },
+      retentionDays,
       filenamePrefix,
     });
     spinner.stop(`Backup saved: ${formatDatabaseBackupResult(result)}`);

cli/src/commands/env-lab.ts

@@ -1,174 +0,0 @@
-import path from "node:path";
-import type { Command } from "commander";
-import * as p from "@clack/prompts";
-import pc from "picocolors";
-import {
-  buildSshEnvLabFixtureConfig,
-  getSshEnvLabSupport,
-  readSshEnvLabFixtureStatus,
-  startSshEnvLabFixture,
-  stopSshEnvLabFixture,
-} from "@paperclipai/adapter-utils/ssh";
-import { resolvePaperclipInstanceId, resolvePaperclipInstanceRoot } from "../config/home.js";
-
-export function resolveEnvLabSshStatePath(instanceId?: string): string {
-  const resolvedInstanceId = resolvePaperclipInstanceId(instanceId);
-  return path.resolve(
-    resolvePaperclipInstanceRoot(resolvedInstanceId),
-    "env-lab",
-    "ssh-fixture",
-    "state.json",
-  );
-}
-
-function printJson(value: unknown) {
-  process.stdout.write(`${JSON.stringify(value, null, 2)}\n`);
-}
-
-function summarizeFixture(state: {
-  host: string;
-  port: number;
-  username: string;
-  workspaceDir: string;
-  sshdLogPath: string;
-}) {
-  p.log.message(`Host: ${pc.cyan(state.host)}:${pc.cyan(String(state.port))}`);
-  p.log.message(`User: ${pc.cyan(state.username)}`);
-  p.log.message(`Workspace: ${pc.cyan(state.workspaceDir)}`);
-  p.log.message(`Log: ${pc.dim(state.sshdLogPath)}`);
-}
-
-export async function collectEnvLabDoctorStatus(opts: { instance?: string }) {
-  const statePath = resolveEnvLabSshStatePath(opts.instance);
-  const [sshSupport, sshStatus] = await Promise.all([
-    getSshEnvLabSupport(),
-    readSshEnvLabFixtureStatus(statePath),
-  ]);
-  const environment = sshStatus.state ? await buildSshEnvLabFixtureConfig(sshStatus.state) : null;
-
-  return {
-    statePath,
-    ssh: {
-      supported: sshSupport.supported,
-      reason: sshSupport.reason,
-      running: sshStatus.running,
-      state: sshStatus.state,
-      environment,
-    },
-  };
-}
-
-export async function envLabUpCommand(opts: { instance?: string; json?: boolean }) {
-  const statePath = resolveEnvLabSshStatePath(opts.instance);
-  const state = await startSshEnvLabFixture({ statePath });
-  const environment = await buildSshEnvLabFixtureConfig(state);
-
-  if (opts.json) {
-    printJson({ state, environment });
-    return;
-  }
-
-  p.log.success("SSH env-lab fixture is running.");
-  summarizeFixture(state);
-  p.log.message(`State: ${pc.dim(statePath)}`);
-}
-
-export async function envLabStatusCommand(opts: { instance?: string; json?: boolean }) {
-  const statePath = resolveEnvLabSshStatePath(opts.instance);
-  const status = await readSshEnvLabFixtureStatus(statePath);
-  const environment = status.state ? await buildSshEnvLabFixtureConfig(status.state) : null;
-
-  if (opts.json) {
-    printJson({ ...status, environment, statePath });
-    return;
-  }
-
-  if (!status.state || !status.running) {
-    p.log.info(`SSH env-lab fixture is not running (${pc.dim(statePath)}).`);
-    return;
-  }
-
-  p.log.success("SSH env-lab fixture is running.");
-  summarizeFixture(status.state);
-  p.log.message(`State: ${pc.dim(statePath)}`);
-}
-
-export async function envLabDownCommand(opts: { instance?: string; json?: boolean }) {
-  const statePath = resolveEnvLabSshStatePath(opts.instance);
-  const stopped = await stopSshEnvLabFixture(statePath);
-
-  if (opts.json) {
-    printJson({ stopped, statePath });
-    return;
-  }
-
-  if (!stopped) {
-    p.log.info(`No SSH env-lab fixture was running (${pc.dim(statePath)}).`);
-    return;
-  }
-
-  p.log.success("SSH env-lab fixture stopped.");
-  p.log.message(`State: ${pc.dim(statePath)}`);
-}
-
-export async function envLabDoctorCommand(opts: { instance?: string; json?: boolean }) {
-  const status = await collectEnvLabDoctorStatus(opts);
-
-  if (opts.json) {
-    printJson(status);
-    return;
-  }
-
-  if (status.ssh.supported) {
-    p.log.success("SSH fixture prerequisites are installed.");
-  } else {
-    p.log.warn(`SSH fixture prerequisites are incomplete: ${status.ssh.reason ?? "unknown reason"}`);
-  }
-
-  if (status.ssh.state && status.ssh.running) {
-    p.log.success("SSH env-lab fixture is running.");
-    summarizeFixture(status.ssh.state);
-    p.log.message(`Private key: ${pc.dim(status.ssh.state.clientPrivateKeyPath)}`);
-    p.log.message(`Known hosts: ${pc.dim(status.ssh.state.knownHostsPath)}`);
-  } else if (status.ssh.state) {
-    p.log.warn("SSH env-lab fixture state exists, but the process is not running.");
-    p.log.message(`State: ${pc.dim(status.statePath)}`);
-  } else {
-    p.log.info("SSH env-lab fixture is not running.");
-    p.log.message(`State: ${pc.dim(status.statePath)}`);
-  }
-
-  p.log.message(`Cleanup: ${pc.dim("pnpm paperclipai env-lab down")}`);
-}
-
-export function registerEnvLabCommands(program: Command) {
-  const envLab = program.command("env-lab").description("Deterministic local environment fixtures");
-
-  envLab
-    .command("up")
-    .description("Start the default SSH env-lab fixture")
-    .option("-i, --instance <id>", "Paperclip instance id (default: current/default)")
-    .option("--json", "Print machine-readable fixture details")
-    .action(envLabUpCommand);
-
-  envLab
-    .command("status")
-    .description("Show the current SSH env-lab fixture state")
-    .option("-i, --instance <id>", "Paperclip instance id (default: current/default)")
-    .option("--json", "Print machine-readable fixture details")
-    .action(envLabStatusCommand);
-
-  envLab
-    .command("down")
-    .description("Stop the default SSH env-lab fixture")
-    .option("-i, --instance <id>", "Paperclip instance id (default: current/default)")
-    .option("--json", "Print machine-readable stop details")
-    .action(envLabDownCommand);
-
-  envLab
-    .command("doctor")
-    .description("Check SSH fixture prerequisites and current status")
-    .option("-i, --instance <id>", "Paperclip instance id (default: current/default)")
-    .option("--json", "Print machine-readable diagnostic details")
-    .action(envLabDoctorCommand);
-}

cli/src/commands/onboard.ts

@@ -3,14 +3,10 @@ import path from "node:path";
 import pc from "picocolors";
 import {
   AUTH_BASE_URL_MODES,
-  BIND_MODES,
   DEPLOYMENT_EXPOSURES,
   DEPLOYMENT_MODES,
   SECRET_PROVIDERS,
   STORAGE_PROVIDERS,
-  inferBindModeFromHost,
-  resolveRuntimeBind,
-  type BindMode,
   type AuthBaseUrlMode,
   type DeploymentExposure,
   type DeploymentMode,
@@ -27,7 +23,6 @@ import { promptLogging } from "../prompts/logging.js";
 import { defaultSecretsConfig } from "../prompts/secrets.js";
 import { defaultStorageConfig, promptStorage } from "../prompts/storage.js";
 import { promptServer } from "../prompts/server.js";
-import { buildPresetServerConfig } from "../config/server-bind.js";
 import {
   describeLocalInstancePaths,
   expandHomePrefix,
@@ -51,14 +46,10 @@ type OnboardOptions = {
   run?: boolean;
   yes?: boolean;
   invokedByRun?: boolean;
-  bind?: BindMode;
 };
 
 type OnboardDefaults = Pick<PaperclipConfig, "database" | "logging" | "server" | "auth" | "storage" | "secrets">;
 
-const TAILNET_BIND_WARNING =
-  "No Tailscale address was detected during setup. The saved config will stay on loopback until Tailscale is available or PAPERCLIP_TAILNET_BIND_HOST is set.";
-
 const ONBOARD_ENV_KEYS = [
   "PAPERCLIP_PUBLIC_URL",
   "DATABASE_URL",
@@ -68,9 +59,6 @@ const ONBOARD_ENV_KEYS = [
   "PAPERCLIP_DB_BACKUP_DIR",
   "PAPERCLIP_DEPLOYMENT_MODE",
   "PAPERCLIP_DEPLOYMENT_EXPOSURE",
-  "PAPERCLIP_BIND",
-  "PAPERCLIP_BIND_HOST",
-  "PAPERCLIP_TAILNET_BIND_HOST",
   "HOST",
   "PORT",
   "SERVE_UI",
@@ -116,62 +104,29 @@ function resolvePathFromEnv(rawValue: string | undefined): string | null {
   return path.resolve(expandHomePrefix(rawValue.trim()));
 }
 
-function describeServerBinding(server: Pick<PaperclipConfig["server"], "bind" | "customBindHost" | "host" | "port">): string {
-  const bind = server.bind ?? inferBindModeFromHost(server.host);
-  const detail =
-    bind === "custom"
-      ? server.customBindHost ?? server.host
-      : bind === "tailnet"
-        ? "detected tailscale address"
-        : server.host;
-  return `${bind}${detail ? ` (${detail})` : ""}:${server.port}`;
-}
-
-function quickstartDefaultsFromEnv(opts?: { preferTrustedLocal?: boolean }): {
+function quickstartDefaultsFromEnv(): {
   defaults: OnboardDefaults;
   usedEnvKeys: string[];
   ignoredEnvKeys: Array<{ key: string; reason: string }>;
 } {
-  const preferTrustedLocal = opts?.preferTrustedLocal ?? false;
   const instanceId = resolvePaperclipInstanceId();
   const defaultStorage = defaultStorageConfig();
   const defaultSecrets = defaultSecretsConfig();
   const databaseUrl = process.env.DATABASE_URL?.trim() || undefined;
-  const publicUrl = preferTrustedLocal
-    ? undefined
-    : (
-      process.env.PAPERCLIP_PUBLIC_URL?.trim() ||
-      process.env.PAPERCLIP_AUTH_PUBLIC_BASE_URL?.trim() ||
-      process.env.BETTER_AUTH_URL?.trim() ||
-      process.env.BETTER_AUTH_BASE_URL?.trim() ||
-      undefined
-    );
-  const deploymentMode = preferTrustedLocal
-    ? "local_trusted"
-    : (parseEnumFromEnv<DeploymentMode>(process.env.PAPERCLIP_DEPLOYMENT_MODE, DEPLOYMENT_MODES) ?? "local_trusted");
+  const publicUrl =
+    process.env.PAPERCLIP_PUBLIC_URL?.trim() ||
+    process.env.PAPERCLIP_AUTH_PUBLIC_BASE_URL?.trim() ||
+    process.env.BETTER_AUTH_URL?.trim() ||
+    process.env.BETTER_AUTH_BASE_URL?.trim() ||
+    undefined;
+  const deploymentMode =
+    parseEnumFromEnv<DeploymentMode>(process.env.PAPERCLIP_DEPLOYMENT_MODE, DEPLOYMENT_MODES) ?? "local_trusted";
   const deploymentExposureFromEnv = parseEnumFromEnv<DeploymentExposure>(
     process.env.PAPERCLIP_DEPLOYMENT_EXPOSURE,
     DEPLOYMENT_EXPOSURES,
   );
   const deploymentExposure =
     deploymentMode === "local_trusted" ? "private" : (deploymentExposureFromEnv ?? "private");
-  const bindFromEnv = parseEnumFromEnv<BindMode>(process.env.PAPERCLIP_BIND, BIND_MODES);
-  const customBindHostFromEnv = process.env.PAPERCLIP_BIND_HOST?.trim() || undefined;
-  const hostFromEnv = process.env.HOST?.trim() || undefined;
-  const configuredBindHost = customBindHostFromEnv ?? hostFromEnv;
-  const bind = preferTrustedLocal
-    ? "loopback"
-    : (
-      deploymentMode === "local_trusted"
-        ? "loopback"
-        : (bindFromEnv ?? (configuredBindHost ? inferBindModeFromHost(configuredBindHost) : "lan"))
-    );
-  const resolvedBind = resolveRuntimeBind({
-    bind,
-    host: hostFromEnv ?? (bind === "loopback" ? "127.0.0.1" : "0.0.0.0"),
-    customBindHost: customBindHostFromEnv,
-    tailnetBindHost: process.env.PAPERCLIP_TAILNET_BIND_HOST?.trim(),
-  });
   const authPublicBaseUrl = publicUrl;
   const authBaseUrlModeFromEnv = parseEnumFromEnv<AuthBaseUrlMode>(
     process.env.PAPERCLIP_AUTH_BASE_URL_MODE,
@@ -228,9 +183,7 @@ function quickstartDefaultsFromEnv(opts?: { preferTrustedLocal?: boolean }): {
     server: {
       deploymentMode,
       exposure: deploymentExposure,
-      bind: resolvedBind.bind,
-      ...(resolvedBind.customBindHost ? { customBindHost: resolvedBind.customBindHost } : {}),
-      host: resolvedBind.host,
+      host: process.env.HOST ?? "127.0.0.1",
       port: Number(process.env.PORT) || 3100,
       allowedHostnames: Array.from(new Set([...allowedHostnamesFromEnv, ...(hostnameFromPublicUrl ? [hostnameFromPublicUrl] : [])])),
       serveUi: parseBooleanFromEnv(process.env.SERVE_UI) ?? true,
@@ -267,49 +220,12 @@ function quickstartDefaultsFromEnv(opts?: { preferTrustedLocal?: boolean }): {
     },
   };
   const ignoredEnvKeys: Array<{ key: string; reason: string }> = [];
-  if (preferTrustedLocal) {
-    const forcedLocalReason = "Ignored because --yes quickstart forces trusted local loopback defaults";
-    for (const key of [
-      "PAPERCLIP_DEPLOYMENT_MODE",
-      "PAPERCLIP_DEPLOYMENT_EXPOSURE",
-      "PAPERCLIP_BIND",
-      "PAPERCLIP_BIND_HOST",
-      "HOST",
-      "PAPERCLIP_AUTH_BASE_URL_MODE",
-      "PAPERCLIP_AUTH_PUBLIC_BASE_URL",
-      "PAPERCLIP_PUBLIC_URL",
-      "BETTER_AUTH_URL",
-      "BETTER_AUTH_BASE_URL",
-    ] as const) {
-      if (process.env[key] !== undefined) {
-        ignoredEnvKeys.push({ key, reason: forcedLocalReason });
-      }
-    }
-  }
   if (deploymentMode === "local_trusted" && process.env.PAPERCLIP_DEPLOYMENT_EXPOSURE !== undefined) {
     ignoredEnvKeys.push({
       key: "PAPERCLIP_DEPLOYMENT_EXPOSURE",
       reason: "Ignored because deployment mode local_trusted always forces private exposure",
     });
   }
-  if (deploymentMode === "local_trusted" && process.env.PAPERCLIP_BIND !== undefined) {
-    ignoredEnvKeys.push({
-      key: "PAPERCLIP_BIND",
-      reason: "Ignored because deployment mode local_trusted always uses loopback reachability",
-    });
-  }
-  if (deploymentMode === "local_trusted" && process.env.PAPERCLIP_BIND_HOST !== undefined) {
-    ignoredEnvKeys.push({
-      key: "PAPERCLIP_BIND_HOST",
-      reason: "Ignored because deployment mode local_trusted always uses loopback reachability",
-    });
-  }
-  if (deploymentMode === "local_trusted" && process.env.HOST !== undefined) {
-    ignoredEnvKeys.push({
-      key: "HOST",
-      reason: "Ignored because deployment mode local_trusted always uses loopback reachability",
-    });
-  }
 
   const ignoredKeySet = new Set(ignoredEnvKeys.map((entry) => entry.key));
   const usedEnvKeys = ONBOARD_ENV_KEYS.filter(
@@ -323,10 +239,6 @@ function canCreateBootstrapInviteImmediately(config: Pick<PaperclipConfig, "data
 }
 
 export async function onboard(opts: OnboardOptions): Promise<void> {
-  if (opts.bind && !["loopback", "lan", "tailnet"].includes(opts.bind)) {
-    throw new Error(`Unsupported bind preset for onboard: ${opts.bind}. Use loopback, lan, or tailnet.`);
-  }
-
   printPaperclipCliBanner();
   p.intro(pc.bgCyan(pc.black(" paperclipai onboard ")));
   const configPath = resolveConfigPath(opts.config);
@@ -381,7 +293,7 @@ export async function onboard(opts: OnboardOptions): Promise<void> {
         `Database: ${existingConfig.database.mode}`,
         existingConfig.llm ? `LLM: ${existingConfig.llm.provider}` : "LLM: not configured",
         `Logging: ${existingConfig.logging.mode} -> ${existingConfig.logging.logDir}`,
-        `Server: ${existingConfig.server.deploymentMode}/${existingConfig.server.exposure} @ ${describeServerBinding(existingConfig.server)}`,
+        `Server: ${existingConfig.server.deploymentMode}/${existingConfig.server.exposure} @ ${existingConfig.server.host}:${existingConfig.server.port}`,
         `Allowed hosts: ${existingConfig.server.allowedHostnames.length > 0 ? existingConfig.server.allowedHostnames.join(", ") : "(loopback only)"}`,
         `Auth URL mode: ${existingConfig.auth.baseUrlMode}${existingConfig.auth.publicBaseUrl ? ` (${existingConfig.auth.publicBaseUrl})` : ""}`,
         `Storage: ${existingConfig.storage.provider}`,
@@ -424,13 +336,7 @@ export async function onboard(opts: OnboardOptions): Promise<void> {
 
   let setupMode: SetupMode = "quickstart";
   if (opts.yes) {
-    p.log.message(
-      pc.dim(
-        opts.bind
-          ? `\`--yes\` enabled: using Quickstart defaults with bind=${opts.bind}.`
-          : "`--yes` enabled: using Quickstart defaults.",
-      ),
-    );
+    p.log.message(pc.dim("`--yes` enabled: using Quickstart defaults."));
   } else {
     const setupModeChoice = await p.select({
       message: "Choose setup path",
@@ -459,9 +365,7 @@ export async function onboard(opts: OnboardOptions): Promise<void> {
   if (tc) trackInstallStarted(tc);
 
   let llm: PaperclipConfig["llm"] | undefined;
-  const { defaults: derivedDefaults, usedEnvKeys, ignoredEnvKeys } = quickstartDefaultsFromEnv({
-    preferTrustedLocal: opts.yes === true && !opts.bind,
-  });
+  const { defaults: derivedDefaults, usedEnvKeys, ignoredEnvKeys } = quickstartDefaultsFromEnv();
   let {
     database,
     logging,
@@ -471,19 +375,6 @@ export async function onboard(opts: OnboardOptions): Promise<void> {
     secrets,
   } = derivedDefaults;
 
-  if (opts.bind === "loopback" || opts.bind === "lan" || opts.bind === "tailnet") {
-    const preset = buildPresetServerConfig(opts.bind, {
-      port: server.port,
-      allowedHostnames: server.allowedHostnames,
-      serveUi: server.serveUi,
-    });
-    server = preset.server;
-    auth = preset.auth;
-    if (opts.bind === "tailnet" && server.host === "127.0.0.1") {
-      p.log.warn(TAILNET_BIND_WARNING);
-    }
-  }
-
   if (setupMode === "advanced") {
     p.log.step(pc.bold("Database"));
     database = await promptDatabase(database);
@@ -571,13 +462,7 @@ export async function onboard(opts: OnboardOptions): Promise<void> {
     );
   } else {
     p.log.step(pc.bold("Quickstart"));
-    p.log.message(
-      pc.dim(
-        opts.bind
-          ? `Using quickstart defaults with bind=${opts.bind}.`
-          : `Using quickstart defaults: ${server.deploymentMode}/${server.exposure} @ ${describeServerBinding(server)}.`,
-      ),
-    );
+    p.log.message(pc.dim("Using quickstart defaults."));
     if (usedEnvKeys.length > 0) {
       p.log.message(pc.dim(`Environment-aware defaults active (${usedEnvKeys.length} env var(s) detected).`));
     } else {
@@ -636,7 +521,7 @@ export async function onboard(opts: OnboardOptions): Promise<void> {
       `Database: ${database.mode}`,
       llm ? `LLM: ${llm.provider}` : "LLM: not configured",
       `Logging: ${logging.mode} -> ${logging.logDir}`,
-      `Server: ${server.deploymentMode}/${server.exposure} @ ${describeServerBinding(server)}`,
+      `Server: ${server.deploymentMode}/${server.exposure} @ ${server.host}:${server.port}`,
       `Allowed hosts: ${server.allowedHostnames.length > 0 ? server.allowedHostnames.join(", ") : "(loopback only)"}`,
       `Auth URL mode: ${auth.baseUrlMode}${auth.publicBaseUrl ? ` (${auth.publicBaseUrl})` : ""}`,
       `Storage: ${storage.provider}`,

cli/src/commands/routines.ts

@@ -9,7 +9,6 @@ import {
   createEmbeddedPostgresLogBuffer,
   ensurePostgresDatabase,
   formatEmbeddedPostgresError,
-  prepareEmbeddedPostgresNativeRuntime,
   routines,
 } from "@paperclipai/db";
 import { eq, inArray } from "drizzle-orm";
@@ -117,7 +116,6 @@ async function ensureEmbeddedPostgres(dataDir: string, preferredPort: number): P
       "Embedded PostgreSQL support requires dependency `embedded-postgres`. Reinstall dependencies and try again.",
     );
   }
-  await prepareEmbeddedPostgresNativeRuntime();
 
   const postmasterPidFile = path.resolve(dataDir, "postmaster.pid");
   const runningPid = readRunningPostmasterPid(postmasterPidFile);

cli/src/commands/run.ts

@@ -1,6 +1,5 @@
 import fs from "node:fs";
 import path from "node:path";
-import { spawnSync } from "node:child_process";
 import { fileURLToPath, pathToFileURL } from "node:url";
 import * as p from "@clack/prompts";
 import pc from "picocolors";
@@ -22,7 +21,6 @@ interface RunOptions {
   instance?: string;
   repair?: boolean;
   yes?: boolean;
-  bind?: "loopback" | "lan" | "tailnet";
 }
 
 interface StartedServer {
@@ -59,7 +57,7 @@ export async function runCommand(opts: RunOptions): Promise<void> {
     }
 
     p.log.step("No config found. Starting onboarding...");
-    await onboard({ config: configPath, invokedByRun: true, bind: opts.bind });
+    await onboard({ config: configPath, invokedByRun: true });
   }
 
   p.log.step("Running doctor checks...");
@@ -148,35 +146,11 @@ function maybeEnableUiDevMiddleware(entrypoint: string): void {
   }
 }
 
-function ensureDevWorkspaceBuildDeps(projectRoot: string): void {
-  const buildScript = path.resolve(projectRoot, "scripts/ensure-plugin-build-deps.mjs");
-  if (!fs.existsSync(buildScript)) return;
-
-  const result = spawnSync(process.execPath, [buildScript], {
-    cwd: projectRoot,
-    stdio: "inherit",
-    timeout: 120_000,
-  });
-
-  if (result.error) {
-    throw new Error(
-      `Failed to prepare workspace build artifacts before starting the Paperclip dev server.\n${formatError(result.error)}`,
-    );
-  }
-
-  if ((result.status ?? 1) !== 0) {
-    throw new Error(
-      "Failed to prepare workspace build artifacts before starting the Paperclip dev server.",
-    );
-  }
-}
-
 async function importServerEntry(): Promise<StartedServer> {
   // Dev mode: try local workspace path (monorepo with tsx)
   const projectRoot = path.resolve(path.dirname(fileURLToPath(import.meta.url)), "../../..");
   const devEntry = path.resolve(projectRoot, "server/src/index.ts");
   if (fs.existsSync(devEntry)) {
-    ensureDevWorkspaceBuildDeps(projectRoot);
     maybeEnableUiDevMiddleware(devEntry);
     const mod = await import(pathToFileURL(devEntry).href);
     return await startServerFromModule(mod, devEntry);

cli/src/commands/worktree-lib.ts

@@ -75,6 +75,11 @@ function nonEmpty(value: string | null | undefined): string | null {
   return typeof value === "string" && value.trim().length > 0 ? value.trim() : null;
 }
 
+function isLoopbackHost(hostname: string): boolean {
+  const value = hostname.trim().toLowerCase();
+  return value === "127.0.0.1" || value === "localhost" || value === "::1";
+}
+
 export function sanitizeWorktreeInstanceId(rawValue: string): string {
   const trimmed = rawValue.trim().toLowerCase();
   const normalized = trimmed
@@ -163,8 +168,7 @@ export function rewriteLocalUrlPort(rawUrl: string | undefined, port: number): s
   if (!rawUrl) return undefined;
   try {
     const parsed = new URL(rawUrl);
-    // The URL API normalizes default ports like :80/:443 to "", so treat them as stable URLs.
-    if (!parsed.port) return rawUrl;
+    if (!isLoopbackHost(parsed.hostname)) return rawUrl;
     parsed.port = String(port);
     return parsed.toString();
   } catch {
@@ -210,8 +214,6 @@ export function buildWorktreeConfig(input: {
     server: {
       deploymentMode: source?.server.deploymentMode ?? "local_trusted",
       exposure: source?.server.exposure ?? "private",
-      ...(source?.server.bind ? { bind: source.server.bind } : {}),
-      ...(source?.server.customBindHost ? { customBindHost: source.server.customBindHost } : {}),
       host: source?.server.host ?? "127.0.0.1",
       port: serverPort,
       allowedHostnames: source?.server.allowedHostnames ?? [],

cli/src/commands/worktree.ts

@@ -39,13 +39,10 @@ import {
   issues,
   projectWorkspaces,
   projects,
-  routines,
-  routineTriggers,
   runDatabaseBackup,
   runDatabaseRestore,
   createEmbeddedPostgresLogBuffer,
   formatEmbeddedPostgresError,
-  prepareEmbeddedPostgresNativeRuntime,
 } from "@paperclipai/db";
 import type { Command } from "commander";
 import { ensureAgentJwtSecret, loadPaperclipEnvFile, mergePaperclipEnvEntries, readPaperclipEnvEntries, resolvePaperclipEnvFile } from "../config/env.js";
@@ -94,7 +91,6 @@ type WorktreeInitOptions = {
   dbPort?: number;
   seed?: boolean;
   seedMode?: string;
-  preserveLiveWork?: boolean;
   force?: boolean;
 };
 
@@ -128,23 +124,10 @@ type WorktreeReseedOptions = {
   fromDataDir?: string;
   fromInstance?: string;
   seedMode?: string;
-  preserveLiveWork?: boolean;
   yes?: boolean;
   allowLiveTarget?: boolean;
 };
 
-type WorktreeRepairOptions = {
-  branch?: string;
-  home?: string;
-  fromConfig?: string;
-  fromDataDir?: string;
-  fromInstance?: string;
-  seedMode?: string;
-  preserveLiveWork?: boolean;
-  noSeed?: boolean;
-  allowLiveTarget?: boolean;
-};
-
 type EmbeddedPostgresInstance = {
   initialise(): Promise<void>;
   start(): Promise<void>;
@@ -183,8 +166,6 @@ type CopiedGitHooksResult = {
 
 type SeedWorktreeDatabaseResult = {
   backupSummary: string;
-  pausedScheduledRoutines: number;
-  executionQuarantine: SeededWorktreeExecutionQuarantineSummary;
   reboundWorkspaces: Array<{
     name: string;
     fromCwd: string;
@@ -192,14 +173,6 @@ type SeedWorktreeDatabaseResult = {
   }>;
 };
 
-export type SeededWorktreeExecutionQuarantineSummary = {
-  disabledTimerHeartbeats: number;
-  resetRunningAgents: number;
-  quarantinedInProgressIssues: number;
-  unassignedTodoIssues: number;
-  unassignedReviewIssues: number;
-};
-
 function nonEmpty(value: string | null | undefined): string | null {
   return typeof value === "string" && value.trim().length > 0 ? value.trim() : null;
 }
@@ -212,18 +185,6 @@ function isCurrentSourceConfigPath(sourceConfigPath: string): boolean {
   return path.resolve(currentConfigPath) === path.resolve(sourceConfigPath);
 }
 
-function formatSeededWorktreeExecutionQuarantineSummary(
-  summary: SeededWorktreeExecutionQuarantineSummary,
-): string {
-  return [
-    `disabled timer heartbeats: ${summary.disabledTimerHeartbeats}`,
-    `reset running agents: ${summary.resetRunningAgents}`,
-    `quarantined in-progress issues: ${summary.quarantinedInProgressIssues}`,
-    `unassigned todo issues: ${summary.unassignedTodoIssues}`,
-    `unassigned review issues: ${summary.unassignedReviewIssues}`,
-  ].join(", ");
-}
-
 const WORKTREE_NAME_PREFIX = "paperclip-";
 
 function resolveWorktreeMakeName(name: string): string {
@@ -587,46 +548,6 @@ function detectGitBranchName(cwd: string): string | null {
   }
 }
 
-function validateGitBranchName(cwd: string, branchName: string): string {
-  const value = nonEmpty(branchName);
-  if (!value) {
-    throw new Error("Branch name is required.");
-  }
-  try {
-    execFileSync("git", ["check-ref-format", "--branch", value], {
-      cwd,
-      stdio: ["ignore", "pipe", "pipe"],
-    });
-  } catch (error) {
-    throw new Error(`Invalid branch name "${branchName}": ${extractExecSyncErrorMessage(error) ?? String(error)}`);
-  }
-  return value;
-}
-
-function isPrimaryGitWorktree(cwd: string): boolean {
-  const workspace = detectGitWorkspaceInfo(cwd);
-  return Boolean(workspace && workspace.gitDir === workspace.commonDir);
-}
-
-function resolvePrimaryGitRepoRoot(cwd: string): string {
-  const workspace = detectGitWorkspaceInfo(cwd);
-  if (!workspace) {
-    throw new Error("Current directory is not inside a git repository.");
-  }
-  if (workspace.gitDir === workspace.commonDir) {
-    return workspace.root;
-  }
-  return path.resolve(workspace.commonDir, "..");
-}
-
-function resolveRepairWorktreeDirName(branchName: string): string {
-  const normalized = branchName.trim()
-    .replace(/[^A-Za-z0-9._-]+/g, "-")
-    .replace(/-+/g, "-")
-    .replace(/^[-._]+|[-._]+$/g, "");
-  return normalized || "worktree";
-}
-
 function detectGitWorkspaceInfo(cwd: string): GitWorkspaceInfo | null {
   try {
     const root = execFileSync("git", ["rev-parse", "--show-toplevel"], {
@@ -850,21 +771,6 @@ export function resolveWorktreeReseedSource(input: WorktreeReseedOptions): Resol
   );
 }
 
-function resolveWorktreeRepairSource(input: WorktreeRepairOptions): ResolvedWorktreeReseedSource {
-  const fromConfig = nonEmpty(input.fromConfig);
-  const fromDataDir = nonEmpty(input.fromDataDir);
-  const fromInstance = nonEmpty(input.fromInstance) ?? "default";
-  const configPath = resolveSourceConfigPath({
-    fromConfig: fromConfig ?? undefined,
-    fromDataDir: fromDataDir ?? undefined,
-    fromInstance,
-  });
-  return {
-    configPath,
-    label: configPath,
-  };
-}
-
 export function resolveWorktreeReseedTargetPaths(input: {
   configPath: string;
   rootPath: string;
@@ -886,105 +792,6 @@ export function resolveWorktreeReseedTargetPaths(input: {
   });
 }
 
-function resolveExistingGitWorktree(selector: string, cwd: string): MergeSourceChoice | null {
-  const trimmed = selector.trim();
-  if (trimmed.length === 0) return null;
-
-  const directPath = path.resolve(trimmed);
-  if (existsSync(directPath)) {
-    return {
-      worktree: directPath,
-      branch: null,
-      branchLabel: path.basename(directPath),
-      hasPaperclipConfig: existsSync(path.resolve(directPath, ".paperclip", "config.json")),
-      isCurrent: directPath === path.resolve(cwd),
-    };
-  }
-
-  return toMergeSourceChoices(cwd).find((choice) =>
-    choice.worktree === directPath
-    || path.basename(choice.worktree) === trimmed
-    || choice.branchLabel === trimmed
-    || choice.branch === trimmed,
-  ) ?? null;
-}
-
-async function ensureRepairTargetWorktree(input: {
-  selector?: string;
-  seedMode: WorktreeSeedMode;
-  opts: WorktreeRepairOptions;
-}): Promise<ResolvedWorktreeRepairTarget | null> {
-  const cwd = process.cwd();
-  const currentRoot = path.resolve(cwd);
-  const currentConfigPath = path.resolve(currentRoot, ".paperclip", "config.json");
-
-  if (!input.selector) {
-    if (isPrimaryGitWorktree(cwd)) {
-      return null;
-    }
-    return {
-      rootPath: currentRoot,
-      configPath: currentConfigPath,
-      label: path.basename(currentRoot),
-      branchName: detectGitBranchName(cwd),
-      created: false,
-    };
-  }
-
-  const existing = resolveExistingGitWorktree(input.selector, cwd);
-  if (existing) {
-    return {
-      rootPath: existing.worktree,
-      configPath: path.resolve(existing.worktree, ".paperclip", "config.json"),
-      label: existing.branchLabel,
-      branchName: existing.branchLabel === "(detached)" ? null : existing.branchLabel,
-      created: false,
-    };
-  }
-
-  const repoRoot = resolvePrimaryGitRepoRoot(cwd);
-  const branchName = validateGitBranchName(repoRoot, input.selector);
-  const targetPath = path.resolve(
-    repoRoot,
-    ".paperclip",
-    "worktrees",
-    resolveRepairWorktreeDirName(branchName),
-  );
-
-  if (existsSync(targetPath)) {
-    throw new Error(`Target path already exists but is not a registered git worktree: ${targetPath}`);
-  }
-
-  mkdirSync(path.dirname(targetPath), { recursive: true });
-
-  const spinner = p.spinner();
-  spinner.start(`Creating git worktree for ${branchName}...`);
-  try {
-    execFileSync("git", resolveGitWorktreeAddArgs({
-      branchName,
-      targetPath,
-      branchExists: localBranchExists(repoRoot, branchName),
-    }), {
-      cwd: repoRoot,
-      stdio: ["ignore", "pipe", "pipe"],
-    });
-    spinner.stop(`Created git worktree at ${targetPath}.`);
-  } catch (error) {
-    spinner.stop(pc.red("Failed to create git worktree."));
-    throw new Error(extractExecSyncErrorMessage(error) ?? String(error));
-  }
-
-  installDependenciesBestEffort(targetPath);
-
-  return {
-    rootPath: targetPath,
-    configPath: path.resolve(targetPath, ".paperclip", "config.json"),
-    label: branchName,
-    branchName,
-    created: true,
-  };
-}
-
 function resolveSourceConnectionString(config: PaperclipConfig, envEntries: Record<string, string>, portOverride?: number): string {
   if (config.database.mode === "postgres") {
     const connectionString = nonEmpty(envEntries.DATABASE_URL) ?? nonEmpty(config.database.connectionString);
@@ -1060,7 +867,6 @@ async function ensureEmbeddedPostgres(dataDir: string, preferredPort: number): P
       "Embedded PostgreSQL support requires dependency `embedded-postgres`. Reinstall dependencies and try again.",
     );
   }
-  await prepareEmbeddedPostgresNativeRuntime();
 
   const postmasterPidFile = path.resolve(dataDir, "postmaster.pid");
   const runningPid = readRunningPostmasterPid(postmasterPidFile);
@@ -1116,163 +922,6 @@ async function ensureEmbeddedPostgres(dataDir: string, preferredPort: number): P
   };
 }
 
-export async function pauseSeededScheduledRoutines(connectionString: string): Promise<number> {
-  const db = createDb(connectionString);
-  try {
-    const scheduledRoutineIds = await db
-      .selectDistinct({ routineId: routineTriggers.routineId })
-      .from(routineTriggers)
-      .where(and(eq(routineTriggers.kind, "schedule"), eq(routineTriggers.enabled, true)));
-    const idsToPause = scheduledRoutineIds
-      .map((row) => row.routineId)
-      .filter((value): value is string => Boolean(value));
-
-    if (idsToPause.length === 0) {
-      return 0;
-    }
-
-    const paused = await db
-      .update(routines)
-      .set({
-        status: "paused",
-        updatedAt: new Date(),
-      })
-      .where(and(inArray(routines.id, idsToPause), sql`${routines.status} <> 'paused'`, sql`${routines.status} <> 'archived'`))
-      .returning({ id: routines.id });
-
-    return paused.length;
-  } finally {
-    await db.$client?.end?.({ timeout: 5 }).catch(() => undefined);
-  }
-}
-
-const EMPTY_SEEDED_WORKTREE_EXECUTION_QUARANTINE_SUMMARY: SeededWorktreeExecutionQuarantineSummary = {
-  disabledTimerHeartbeats: 0,
-  resetRunningAgents: 0,
-  quarantinedInProgressIssues: 0,
-  unassignedTodoIssues: 0,
-  unassignedReviewIssues: 0,
-};
-
-function isRecord(value: unknown): value is Record<string, unknown> {
-  return Boolean(value) && typeof value === "object" && !Array.isArray(value);
-}
-
-function isEnabledValue(value: unknown): boolean {
-  return value === true || value === "true" || value === 1 || value === "1";
-}
-
-function normalizeWorktreeRuntimeConfig(runtimeConfig: unknown): {
-  runtimeConfig: Record<string, unknown>;
-  disabledTimerHeartbeat: boolean;
-  changed: boolean;
-} {
-  const nextRuntimeConfig = isRecord(runtimeConfig) ? { ...runtimeConfig } : {};
-  const heartbeat = isRecord(nextRuntimeConfig.heartbeat) ? { ...nextRuntimeConfig.heartbeat } : null;
-  if (!heartbeat) {
-    return { runtimeConfig: nextRuntimeConfig, disabledTimerHeartbeat: false, changed: false };
-  }
-
-  const disabledTimerHeartbeat = isEnabledValue(heartbeat.enabled);
-  if (heartbeat.enabled !== false) {
-    heartbeat.enabled = false;
-    nextRuntimeConfig.heartbeat = heartbeat;
-    return { runtimeConfig: nextRuntimeConfig, disabledTimerHeartbeat, changed: true };
-  }
-
-  return { runtimeConfig: nextRuntimeConfig, disabledTimerHeartbeat: false, changed: false };
-}
-
-export async function quarantineSeededWorktreeExecutionState(
-  connectionString: string,
-): Promise<SeededWorktreeExecutionQuarantineSummary> {
-  const db = createDb(connectionString);
-  const summary = { ...EMPTY_SEEDED_WORKTREE_EXECUTION_QUARANTINE_SUMMARY };
-  try {
-    await db.transaction(async (tx) => {
-      const seededAgents = await tx
-        .select({
-          id: agents.id,
-          status: agents.status,
-          runtimeConfig: agents.runtimeConfig,
-        })
-        .from(agents);
-
-      for (const agent of seededAgents) {
-        const normalized = normalizeWorktreeRuntimeConfig(agent.runtimeConfig);
-        const nextStatus = agent.status === "running" ? "idle" : agent.status;
-        if (normalized.disabledTimerHeartbeat) {
-          summary.disabledTimerHeartbeats += 1;
-        }
-        if (agent.status === "running") {
-          summary.resetRunningAgents += 1;
-        }
-        if (normalized.changed || nextStatus !== agent.status) {
-          await tx
-            .update(agents)
-            .set({
-              runtimeConfig: normalized.runtimeConfig,
-              status: nextStatus,
-              updatedAt: new Date(),
-            })
-            .where(eq(agents.id, agent.id));
-        }
-      }
-
-      const affectedIssues = await tx
-        .select({
-          id: issues.id,
-          companyId: issues.companyId,
-          status: issues.status,
-        })
-        .from(issues)
-        .where(
-          and(
-            sql`${issues.assigneeAgentId} is not null`,
-            sql`${issues.assigneeUserId} is null`,
-            inArray(issues.status, ["todo", "in_progress", "in_review"]),
-          ),
-        );
-
-      for (const issue of affectedIssues) {
-        const nextStatus = issue.status === "in_progress" ? "blocked" : issue.status;
-        await tx
-          .update(issues)
-          .set({
-            status: nextStatus,
-            assigneeAgentId: null,
-            checkoutRunId: null,
-            executionRunId: null,
-            executionAgentNameKey: null,
-            executionLockedAt: null,
-            executionWorkspaceId: null,
-            updatedAt: new Date(),
-          })
-          .where(eq(issues.id, issue.id));
-
-        if (issue.status === "in_progress") {
-          summary.quarantinedInProgressIssues += 1;
-          await tx.insert(issueComments).values({
-            companyId: issue.companyId,
-            issueId: issue.id,
-            body:
-              "Quarantined during worktree seed so copied in-flight work does not auto-run in this isolated instance. " +
-              "Reassign or unblock here only if you intentionally want the worktree instance to own this task.",
-          });
-        } else if (issue.status === "todo") {
-          summary.unassignedTodoIssues += 1;
-        } else if (issue.status === "in_review") {
-          summary.unassignedReviewIssues += 1;
-        }
-      }
-    });
-
-    return summary;
-  } finally {
-    await db.$client?.end?.({ timeout: 5 }).catch(() => undefined);
-  }
-}
-
 async function seedWorktreeDatabase(input: {
   sourceConfigPath: string;
   sourceConfig: PaperclipConfig;
@@ -1280,7 +929,6 @@ async function seedWorktreeDatabase(input: {
   targetPaths: WorktreeLocalPaths;
   instanceId: string;
   seedMode: WorktreeSeedMode;
-  preserveLiveWork?: boolean;
 }): Promise<SeedWorktreeDatabaseResult> {
   const seedPlan = resolveWorktreeSeedPlan(input.seedMode);
   const sourceEnvFile = resolvePaperclipEnvFile(input.sourceConfigPath);
@@ -1311,9 +959,8 @@ async function seedWorktreeDatabase(input: {
     const backup = await runDatabaseBackup({
       connectionString: sourceConnectionString,
       backupDir: path.resolve(input.targetPaths.backupDir, "seed"),
-      retention: { dailyDays: 7, weeklyWeeks: 4, monthlyMonths: 1 },
+      retentionDays: 7,
       filenamePrefix: `${input.instanceId}-seed`,
-      backupEngine: "javascript",
       includeMigrationJournal: true,
       excludeTables: seedPlan.excludedTables,
       nullifyColumns: seedPlan.nullifyColumns,
@@ -1332,10 +979,6 @@ async function seedWorktreeDatabase(input: {
       backupFile: backup.backupFile,
     });
     await applyPendingMigrations(targetConnectionString);
-    const executionQuarantine = input.preserveLiveWork
-      ? { ...EMPTY_SEEDED_WORKTREE_EXECUTION_QUARANTINE_SUMMARY }
-      : await quarantineSeededWorktreeExecutionState(targetConnectionString);
-    const pausedScheduledRoutines = await pauseSeededScheduledRoutines(targetConnectionString);
     const reboundWorkspaces = await rebindSeededProjectWorkspaces({
       targetConnectionString,
       currentCwd: input.targetPaths.cwd,
@@ -1343,8 +986,6 @@ async function seedWorktreeDatabase(input: {
 
     return {
       backupSummary: formatDatabaseBackupResult(backup),
-      pausedScheduledRoutines,
-      executionQuarantine,
       reboundWorkspaces,
     };
   } finally {
@@ -1387,12 +1028,7 @@ async function runWorktreeInit(opts: WorktreeInitOptions): Promise<void> {
   }
 
   if (opts.force) {
-    // Only remove the specific files we're about to rewrite, not the whole
-    // repoConfigDir — that directory can contain sibling state such as
-    // <repo>/.paperclip/worktrees/ holding every repo-managed worktree
-    // checkout, and a recursive rmSync here would nuke them all.
-    rmSync(paths.configPath, { force: true });
-    rmSync(paths.envPath, { force: true });
+    rmSync(paths.repoConfigDir, { recursive: true, force: true });
     rmSync(paths.instanceRoot, { recursive: true, force: true });
   }
 
@@ -1428,8 +1064,6 @@ async function runWorktreeInit(opts: WorktreeInitOptions): Promise<void> {
   const copiedGitHooks = copyGitHooksToWorktreeGitDir(cwd);
 
   let seedSummary: string | null = null;
-  let seedExecutionQuarantineSummary: SeededWorktreeExecutionQuarantineSummary | null = null;
-  let pausedScheduledRoutineCount: number | null = null;
   let reboundWorkspaceSummary: SeedWorktreeDatabaseResult["reboundWorkspaces"] = [];
   if (opts.seed !== false) {
     if (!sourceConfig) {
@@ -1447,11 +1081,8 @@ async function runWorktreeInit(opts: WorktreeInitOptions): Promise<void> {
         targetPaths: paths,
         instanceId,
         seedMode,
-        preserveLiveWork: opts.preserveLiveWork,
       });
       seedSummary = seeded.backupSummary;
-      seedExecutionQuarantineSummary = seeded.executionQuarantine;
-      pausedScheduledRoutineCount = seeded.pausedScheduledRoutines;
       reboundWorkspaceSummary = seeded.reboundWorkspaces;
       spinner.stop(`Seeded isolated worktree database (${seedMode}).`);
     } catch (error) {
@@ -1474,16 +1105,6 @@ async function runWorktreeInit(opts: WorktreeInitOptions): Promise<void> {
   if (seedSummary) {
     p.log.message(pc.dim(`Seed mode: ${seedMode}`));
     p.log.message(pc.dim(`Seed snapshot: ${seedSummary}`));
-    if (opts.preserveLiveWork) {
-      p.log.warning("Preserved copied live work; this worktree instance may auto-run source-instance assignments.");
-    } else if (seedExecutionQuarantineSummary) {
-      p.log.message(
-        pc.dim(`Seed execution quarantine: ${formatSeededWorktreeExecutionQuarantineSummary(seedExecutionQuarantineSummary)}`),
-      );
-    }
-    if (pausedScheduledRoutineCount != null) {
-      p.log.message(pc.dim(`Paused scheduled routines: ${pausedScheduledRoutineCount}`));
-    }
     for (const rebound of reboundWorkspaceSummary) {
       p.log.message(
         pc.dim(`Rebound workspace ${rebound.name}: ${rebound.fromCwd} -> ${rebound.toCwd}`),
@@ -1551,7 +1172,18 @@ export async function worktreeMakeCommand(nameArg: string, opts: WorktreeMakeOpt
     throw new Error(extractExecSyncErrorMessage(error) ?? String(error));
   }
 
-  installDependenciesBestEffort(targetPath);
+  const installSpinner = p.spinner();
+  installSpinner.start("Installing dependencies...");
+  try {
+    execFileSync("pnpm", ["install"], {
+      cwd: targetPath,
+      stdio: ["ignore", "pipe", "pipe"],
+    });
+    installSpinner.stop("Installed dependencies.");
+  } catch (error) {
+    installSpinner.stop(pc.yellow("Failed to install dependencies (continuing anyway)."));
+    p.log.warning(extractExecSyncErrorMessage(error) ?? String(error));
+  }
 
   const originalCwd = process.cwd();
   try {
@@ -1568,21 +1200,6 @@ export async function worktreeMakeCommand(nameArg: string, opts: WorktreeMakeOpt
   }
 }
 
-function installDependenciesBestEffort(targetPath: string): void {
-  const installSpinner = p.spinner();
-  installSpinner.start("Installing dependencies...");
-  try {
-    execFileSync("pnpm", ["install"], {
-      cwd: targetPath,
-      stdio: ["ignore", "pipe", "pipe"],
-    });
-    installSpinner.stop("Installed dependencies.");
-  } catch (error) {
-    installSpinner.stop(pc.yellow("Failed to install dependencies (continuing anyway)."));
-    p.log.warning(extractExecSyncErrorMessage(error) ?? String(error));
-  }
-}
-
 type WorktreeCleanupOptions = {
   instance?: string;
   home?: string;
@@ -1616,14 +1233,6 @@ type ResolvedWorktreeReseedSource = {
   label: string;
 };
 
-type ResolvedWorktreeRepairTarget = {
-  rootPath: string;
-  configPath: string;
-  label: string;
-  branchName: string | null;
-  created: boolean;
-};
-
 function parseGitWorktreeList(cwd: string): GitWorktreeListEntry[] {
   const raw = execFileSync("git", ["worktree", "list", "--porcelain"], {
     cwd,
@@ -3065,7 +2674,10 @@ export async function worktreeMergeHistoryCommand(sourceArg: string | undefined,
   }
 }
 
-async function runWorktreeReseed(opts: WorktreeReseedOptions): Promise<void> {
+export async function worktreeReseedCommand(opts: WorktreeReseedOptions): Promise<void> {
+  printPaperclipCliBanner();
+  p.intro(pc.bgCyan(pc.black(" paperclipai worktree reseed ")));
+
   const seedMode = opts.seedMode ?? "full";
   if (!isWorktreeSeedMode(seedMode)) {
     throw new Error(`Unsupported seed mode "${seedMode}". Expected one of: minimal, full.`);
@@ -3128,20 +2740,11 @@ async function runWorktreeReseed(opts: WorktreeReseedOptions): Promise<void> {
       targetPaths,
       instanceId: targetPaths.instanceId,
       seedMode,
-      preserveLiveWork: opts.preserveLiveWork,
     });
     spinner.stop(`Reseeded ${targetEndpoint.label} (${seedMode}).`);
     p.log.message(pc.dim(`Source: ${source.configPath}`));
     p.log.message(pc.dim(`Target: ${targetEndpoint.configPath}`));
     p.log.message(pc.dim(`Seed snapshot: ${seeded.backupSummary}`));
-    if (opts.preserveLiveWork) {
-      p.log.warning("Preserved copied live work; this worktree instance may auto-run source-instance assignments.");
-    } else {
-      p.log.message(
-        pc.dim(`Seed execution quarantine: ${formatSeededWorktreeExecutionQuarantineSummary(seeded.executionQuarantine)}`),
-      );
-    }
-    p.log.message(pc.dim(`Paused scheduled routines: ${seeded.pausedScheduledRoutines}`));
     for (const rebound of seeded.reboundWorkspaces) {
       p.log.message(
         pc.dim(`Rebound workspace ${rebound.name}: ${rebound.fromCwd} -> ${rebound.toCwd}`),
@@ -3154,98 +2757,6 @@ async function runWorktreeReseed(opts: WorktreeReseedOptions): Promise<void> {
   }
 }
 
-export async function worktreeReseedCommand(opts: WorktreeReseedOptions): Promise<void> {
-  printPaperclipCliBanner();
-  p.intro(pc.bgCyan(pc.black(" paperclipai worktree reseed ")));
-  await runWorktreeReseed(opts);
-}
-
-export async function worktreeRepairCommand(opts: WorktreeRepairOptions): Promise<void> {
-  printPaperclipCliBanner();
-  p.intro(pc.bgCyan(pc.black(" paperclipai worktree repair ")));
-
-  const seedMode = opts.seedMode ?? "minimal";
-  if (!isWorktreeSeedMode(seedMode)) {
-    throw new Error(`Unsupported seed mode "${seedMode}". Expected one of: minimal, full.`);
-  }
-
-  const target = await ensureRepairTargetWorktree({
-    selector: nonEmpty(opts.branch) ?? undefined,
-    seedMode,
-    opts,
-  });
-  if (!target) {
-    p.log.warn("Current checkout is the primary repo worktree. Pass --branch to create or repair a linked worktree.");
-    p.outro(pc.yellow("No worktree repaired."));
-    return;
-  }
-
-  const source = resolveWorktreeRepairSource(opts);
-  if (!existsSync(source.configPath)) {
-    throw new Error(`Source config not found at ${source.configPath}.`);
-  }
-  if (path.resolve(source.configPath) === path.resolve(target.configPath)) {
-    throw new Error("Source and target Paperclip configs are the same. Use --from-config/--from-instance to point repair at a different source.");
-  }
-
-  const targetConfig = existsSync(target.configPath) ? readConfig(target.configPath) : null;
-  const targetEnvEntries = readPaperclipEnvEntries(resolvePaperclipEnvFile(target.configPath));
-  const targetHasWorktreeEnv = Boolean(
-    nonEmpty(targetEnvEntries.PAPERCLIP_HOME) && nonEmpty(targetEnvEntries.PAPERCLIP_INSTANCE_ID),
-  );
-
-  if (targetConfig && targetHasWorktreeEnv && opts.noSeed) {
-    p.log.message(pc.dim(`Target ${target.label} already has worktree-local config/env. Skipping reseed because --no-seed was passed.`));
-    p.outro(pc.green(`Worktree metadata already looks healthy for ${target.label}.`));
-    return;
-  }
-
-  if (targetConfig && targetHasWorktreeEnv) {
-    await runWorktreeReseed({
-      fromConfig: source.configPath,
-      to: target.rootPath,
-      seedMode,
-      preserveLiveWork: opts.preserveLiveWork,
-      yes: true,
-      allowLiveTarget: opts.allowLiveTarget,
-    });
-    return;
-  }
-
-  const repairInstanceId = sanitizeWorktreeInstanceId(path.basename(target.rootPath));
-  const repairPaths = resolveWorktreeLocalPaths({
-    cwd: target.rootPath,
-    homeDir: resolveWorktreeHome(opts.home),
-    instanceId: repairInstanceId,
-  });
-  const runningTargetPid = readRunningPostmasterPid(path.resolve(repairPaths.embeddedPostgresDataDir, "postmaster.pid"));
-  if (runningTargetPid && !opts.allowLiveTarget) {
-    throw new Error(
-      `Target worktree database appears to be running (pid ${runningTargetPid}). Stop Paperclip in ${target.rootPath} before repairing, or re-run with --allow-live-target if you want to override this guard.`,
-    );
-  }
-  if (runningTargetPid && opts.allowLiveTarget) {
-    p.log.warning(`Proceeding even though the target embedded PostgreSQL appears to be running (pid ${runningTargetPid}).`);
-  }
-
-  const originalCwd = process.cwd();
-  try {
-    process.chdir(target.rootPath);
-    await runWorktreeInit({
-      home: opts.home,
-      fromConfig: source.configPath,
-      fromDataDir: opts.fromDataDir,
-      fromInstance: opts.fromInstance,
-      seed: opts.noSeed ? false : true,
-      seedMode,
-      preserveLiveWork: opts.preserveLiveWork,
-      force: true,
-    });
-  } finally {
-    process.chdir(originalCwd);
-  }
-}
-
 export function registerWorktreeCommands(program: Command): void {
   const worktree = program.command("worktree").description("Worktree-local Paperclip instance helpers");
 
@@ -3262,7 +2773,6 @@ export function registerWorktreeCommands(program: Command): void {
     .option("--server-port <port>", "Preferred server port", (value) => Number(value))
     .option("--db-port <port>", "Preferred embedded Postgres port", (value) => Number(value))
     .option("--seed-mode <mode>", "Seed profile: minimal or full (default: minimal)", "minimal")
-    .option("--preserve-live-work", "Do not quarantine copied agent timers or assigned open issues in the seeded worktree", false)
     .option("--no-seed", "Skip database seeding from the source instance")
     .option("--force", "Replace existing repo-local config and isolated instance data", false)
     .action(worktreeMakeCommand);
@@ -3279,7 +2789,6 @@ export function registerWorktreeCommands(program: Command): void {
     .option("--server-port <port>", "Preferred server port", (value) => Number(value))
     .option("--db-port <port>", "Preferred embedded Postgres port", (value) => Number(value))
     .option("--seed-mode <mode>", "Seed profile: minimal or full (default: minimal)", "minimal")
-    .option("--preserve-live-work", "Do not quarantine copied agent timers or assigned open issues in the seeded worktree", false)
     .option("--no-seed", "Skip database seeding from the source instance")
     .option("--force", "Replace existing repo-local config and isolated instance data", false)
     .action(worktreeInitCommand);
@@ -3319,25 +2828,10 @@ export function registerWorktreeCommands(program: Command): void {
     .option("--from-data-dir <path>", "Source PAPERCLIP_HOME used when deriving the source config")
     .option("--from-instance <id>", "Source instance id when deriving the source config")
     .option("--seed-mode <mode>", "Seed profile: minimal or full (default: full)", "full")
-    .option("--preserve-live-work", "Do not quarantine copied agent timers or assigned open issues in the seeded worktree", false)
     .option("--yes", "Skip the destructive confirmation prompt", false)
     .option("--allow-live-target", "Override the guard that requires the target worktree DB to be stopped first", false)
     .action(worktreeReseedCommand);
 
-  worktree
-    .command("repair")
-    .description("Create or repair a linked worktree-local Paperclip instance without touching the primary checkout")
-    .option("--branch <name>", "Existing branch/worktree selector to repair, or a branch name to create under .paperclip/worktrees")
-    .option("--home <path>", `Home root for worktree instances (env: PAPERCLIP_WORKTREES_DIR, default: ${DEFAULT_WORKTREE_HOME})`)
-    .option("--from-config <path>", "Source config.json to seed from")
-    .option("--from-data-dir <path>", "Source PAPERCLIP_HOME used when deriving the source config")
-    .option("--from-instance <id>", "Source instance id when deriving the source config (default: default)")
-    .option("--seed-mode <mode>", "Seed profile: minimal or full (default: minimal)", "minimal")
-    .option("--preserve-live-work", "Do not quarantine copied agent timers or assigned open issues in the seeded worktree", false)
-    .option("--no-seed", "Repair metadata only and skip reseeding when bootstrapping a missing worktree config", false)
-    .option("--allow-live-target", "Override the guard that requires the target worktree DB to be stopped first", false)
-    .action(worktreeRepairCommand);
-
   program
     .command("worktree:cleanup")
     .description("Safely remove a worktree, its branch, and its isolated instance data")

cli/src/config/home.ts

@@ -1,31 +1,32 @@
+import os from "node:os";
 import path from "node:path";
-import {
-  expandHomePrefix,
-  resolveDefaultBackupDir as resolveSharedDefaultBackupDir,
-  resolveDefaultEmbeddedPostgresDir as resolveSharedDefaultEmbeddedPostgresDir,
-  resolveDefaultLogsDir as resolveSharedDefaultLogsDir,
-  resolveDefaultSecretsKeyFilePath as resolveSharedDefaultSecretsKeyFilePath,
-  resolveDefaultStorageDir as resolveSharedDefaultStorageDir,
-  resolveHomeAwarePath,
-  resolvePaperclipConfigPathForInstance,
-  resolvePaperclipHomeDir,
-  resolvePaperclipInstanceId,
-  resolvePaperclipInstanceRoot as resolveSharedPaperclipInstanceRoot,
-} from "@paperclipai/shared/home-paths";
 
-export {
-  expandHomePrefix,
-  resolveHomeAwarePath,
-  resolvePaperclipHomeDir,
-  resolvePaperclipInstanceId,
-};
+const DEFAULT_INSTANCE_ID = "default";
+const INSTANCE_ID_RE = /^[a-zA-Z0-9_-]+$/;
+
+export function resolvePaperclipHomeDir(): string {
+  const envHome = process.env.PAPERCLIP_HOME?.trim();
+  if (envHome) return path.resolve(expandHomePrefix(envHome));
+  return path.resolve(os.homedir(), ".paperclip");
+}
+
+export function resolvePaperclipInstanceId(override?: string): string {
+  const raw = override?.trim() || process.env.PAPERCLIP_INSTANCE_ID?.trim() || DEFAULT_INSTANCE_ID;
+  if (!INSTANCE_ID_RE.test(raw)) {
+    throw new Error(
+      `Invalid instance id '${raw}'. Allowed characters: letters, numbers, '_' and '-'.`,
+    );
+  }
+  return raw;
+}
 
 export function resolvePaperclipInstanceRoot(instanceId?: string): string {
-  return resolveSharedPaperclipInstanceRoot({ instanceId });
+  const id = resolvePaperclipInstanceId(instanceId);
+  return path.resolve(resolvePaperclipHomeDir(), "instances", id);
 }
 
 export function resolveDefaultConfigPath(instanceId?: string): string {
-  return resolvePaperclipConfigPathForInstance({ instanceId });
+  return path.resolve(resolvePaperclipInstanceRoot(instanceId), "config.json");
 }
 
 export function resolveDefaultContextPath(): string {
@@ -37,23 +38,29 @@ export function resolveDefaultCliAuthPath(): string {
 }
 
 export function resolveDefaultEmbeddedPostgresDir(instanceId?: string): string {
-  return resolveSharedDefaultEmbeddedPostgresDir({ instanceId });
+  return path.resolve(resolvePaperclipInstanceRoot(instanceId), "db");
 }
 
 export function resolveDefaultLogsDir(instanceId?: string): string {
-  return resolveSharedDefaultLogsDir({ instanceId });
+  return path.resolve(resolvePaperclipInstanceRoot(instanceId), "logs");
 }
 
 export function resolveDefaultSecretsKeyFilePath(instanceId?: string): string {
-  return resolveSharedDefaultSecretsKeyFilePath({ instanceId });
+  return path.resolve(resolvePaperclipInstanceRoot(instanceId), "secrets", "master.key");
 }
 
 export function resolveDefaultStorageDir(instanceId?: string): string {
-  return resolveSharedDefaultStorageDir({ instanceId });
+  return path.resolve(resolvePaperclipInstanceRoot(instanceId), "data", "storage");
 }
 
 export function resolveDefaultBackupDir(instanceId?: string): string {
-  return resolveSharedDefaultBackupDir({ instanceId });
+  return path.resolve(resolvePaperclipInstanceRoot(instanceId), "data", "backups");
+}
+
+export function expandHomePrefix(value: string): string {
+  if (value === "~") return os.homedir();
+  if (value.startsWith("~/")) return path.resolve(os.homedir(), value.slice(2));
+  return value;
 }
 
 export function describeLocalInstancePaths(instanceId?: string) {

cli/src/config/server-bind.ts

@@ -1,183 +0,0 @@
-import { execFileSync } from "node:child_process";
-import {
-  ALL_INTERFACES_BIND_HOST,
-  LOOPBACK_BIND_HOST,
-  inferBindModeFromHost,
-  isAllInterfacesHost,
-  isLoopbackHost,
-  type BindMode,
-  type DeploymentExposure,
-  type DeploymentMode,
-} from "@paperclipai/shared";
-import type { AuthConfig, ServerConfig } from "./schema.js";
-
-const TAILSCALE_DETECT_TIMEOUT_MS = 3000;
-
-type BaseServerInput = {
-  port: number;
-  allowedHostnames: string[];
-  serveUi: boolean;
-};
-
-export function inferConfiguredBind(server?: Partial<ServerConfig>): BindMode {
-  if (server?.bind) return server.bind;
-  return inferBindModeFromHost(server?.customBindHost ?? server?.host);
-}
-
-export function detectTailnetBindHost(): string | undefined {
-  const explicit = process.env.PAPERCLIP_TAILNET_BIND_HOST?.trim();
-  if (explicit) return explicit;
-
-  try {
-    const stdout = execFileSync("tailscale", ["ip", "-4"], {
-      encoding: "utf8",
-      stdio: ["ignore", "pipe", "ignore"],
-      timeout: TAILSCALE_DETECT_TIMEOUT_MS,
-    });
-    return stdout
-      .split(/\r?\n/)
-      .map((line) => line.trim())
-      .find(Boolean);
-  } catch {
-    return undefined;
-  }
-}
-
-export function buildPresetServerConfig(
-  bind: Exclude<BindMode, "custom">,
-  input: BaseServerInput,
-): { server: ServerConfig; auth: AuthConfig } {
-  const host =
-    bind === "loopback"
-      ? LOOPBACK_BIND_HOST
-      : bind === "tailnet"
-        ? (detectTailnetBindHost() ?? LOOPBACK_BIND_HOST)
-        : ALL_INTERFACES_BIND_HOST;
-
-  return {
-    server: {
-      deploymentMode: bind === "loopback" ? "local_trusted" : "authenticated",
-      exposure: "private",
-      bind,
-      customBindHost: undefined,
-      host,
-      port: input.port,
-      allowedHostnames: input.allowedHostnames,
-      serveUi: input.serveUi,
-    },
-    auth: {
-      baseUrlMode: "auto",
-      disableSignUp: false,
-    },
-  };
-}
-
-export function buildCustomServerConfig(input: BaseServerInput & {
-  deploymentMode: DeploymentMode;
-  exposure: DeploymentExposure;
-  host: string;
-  publicBaseUrl?: string;
-}): { server: ServerConfig; auth: AuthConfig } {
-  const normalizedHost = input.host.trim();
-  const bind = isLoopbackHost(normalizedHost)
-    ? "loopback"
-    : isAllInterfacesHost(normalizedHost)
-      ? "lan"
-      : "custom";
-
-  return {
-    server: {
-      deploymentMode: input.deploymentMode,
-      exposure: input.deploymentMode === "local_trusted" ? "private" : input.exposure,
-      bind,
-      customBindHost: bind === "custom" ? normalizedHost : undefined,
-      host: normalizedHost,
-      port: input.port,
-      allowedHostnames: input.allowedHostnames,
-      serveUi: input.serveUi,
-    },
-    auth:
-      input.deploymentMode === "authenticated" && input.exposure === "public"
-        ? {
-          baseUrlMode: "explicit",
-          disableSignUp: false,
-          publicBaseUrl: input.publicBaseUrl,
-        }
-        : {
-          baseUrlMode: "auto",
-          disableSignUp: false,
-        },
-  };
-}
-
-export function resolveQuickstartServerConfig(input: {
-  bind?: BindMode | null;
-  deploymentMode?: DeploymentMode | null;
-  exposure?: DeploymentExposure | null;
-  host?: string | null;
-  port: number;
-  allowedHostnames: string[];
-  serveUi: boolean;
-  publicBaseUrl?: string;
-}): { server: ServerConfig; auth: AuthConfig } {
-  const trimmedHost = input.host?.trim();
-  const explicitBind = input.bind ?? null;
-
-  if (explicitBind === "loopback" || explicitBind === "lan" || explicitBind === "tailnet") {
-    return buildPresetServerConfig(explicitBind, {
-      port: input.port,
-      allowedHostnames: input.allowedHostnames,
-      serveUi: input.serveUi,
-    });
-  }
-
-  if (explicitBind === "custom") {
-    return buildCustomServerConfig({
-      deploymentMode: input.deploymentMode ?? "authenticated",
-      exposure: input.exposure ?? "private",
-      host: trimmedHost || LOOPBACK_BIND_HOST,
-      port: input.port,
-      allowedHostnames: input.allowedHostnames,
-      serveUi: input.serveUi,
-      publicBaseUrl: input.publicBaseUrl,
-    });
-  }
-
-  if (trimmedHost) {
-    return buildCustomServerConfig({
-      deploymentMode: input.deploymentMode ?? (isLoopbackHost(trimmedHost) ? "local_trusted" : "authenticated"),
-      exposure: input.exposure ?? "private",
-      host: trimmedHost,
-      port: input.port,
-      allowedHostnames: input.allowedHostnames,
-      serveUi: input.serveUi,
-      publicBaseUrl: input.publicBaseUrl,
-    });
-  }
-
-  if (input.deploymentMode === "authenticated") {
-    if (input.exposure === "public") {
-      return buildCustomServerConfig({
-        deploymentMode: "authenticated",
-        exposure: "public",
-        host: ALL_INTERFACES_BIND_HOST,
-        port: input.port,
-        allowedHostnames: input.allowedHostnames,
-        serveUi: input.serveUi,
-        publicBaseUrl: input.publicBaseUrl,
-      });
-    }
-
-    return buildPresetServerConfig("lan", {
-      port: input.port,
-      allowedHostnames: input.allowedHostnames,
-      serveUi: input.serveUi,
-    });
-  }
-
-  return buildPresetServerConfig("loopback", {
-    port: input.port,
-    allowedHostnames: input.allowedHostnames,
-    serveUi: input.serveUi,
-  });
-}

cli/src/index.ts

@@ -8,7 +8,6 @@ import { heartbeatRun } from "./commands/heartbeat-run.js";
 import { runCommand } from "./commands/run.js";
 import { bootstrapCeoInvite } from "./commands/auth-bootstrap-ceo.js";
 import { dbBackupCommand } from "./commands/db-backup.js";
-import { registerEnvLabCommands } from "./commands/env-lab.js";
 import { registerContextCommands } from "./commands/client/context.js";
 import { registerCompanyCommands } from "./commands/client/company.js";
 import { registerIssueCommands } from "./commands/client/issue.js";
@@ -18,9 +17,6 @@ import { registerActivityCommands } from "./commands/client/activity.js";
 import { registerDashboardCommands } from "./commands/client/dashboard.js";
 import { registerRoutineCommands } from "./commands/routines.js";
 import { registerFeedbackCommands } from "./commands/client/feedback.js";
-import { registerSecretCommands } from "./commands/client/secrets.js";
-import { registerCloudCommands } from "./commands/client/cloud.js";
-import { registerSkillsCommands } from "./commands/client/skills.js";
 import { applyDataDirOverride, type DataDirOptionLike } from "./config/data-dir.js";
 import { loadPaperclipEnvFile } from "./config/env.js";
 import { initTelemetryFromConfigFile, flushTelemetry } from "./telemetry.js";
@@ -54,8 +50,7 @@ program
   .description("Interactive first-run setup wizard")
   .option("-c, --config <path>", "Path to config file")
   .option("-d, --data-dir <path>", DATA_DIR_OPTION_HELP)
-  .option("--bind <mode>", "Quickstart reachability preset (loopback, lan, tailnet)")
-  .option("-y, --yes", "Accept quickstart defaults (trusted local loopback unless --bind is set) and start immediately", false)
+  .option("-y, --yes", "Accept defaults (quickstart + start immediately)", false)
   .option("--run", "Start Paperclip immediately after saving config", false)
   .action(onboard);
 
@@ -113,7 +108,6 @@ program
   .option("-c, --config <path>", "Path to config file")
   .option("-d, --data-dir <path>", DATA_DIR_OPTION_HELP)
   .option("-i, --instance <id>", "Local instance id (default: default)")
-  .option("--bind <mode>", "On first run, use onboarding reachability preset (loopback, lan, tailnet)")
   .option("--repair", "Attempt automatic repairs during doctor", true)
   .option("--no-repair", "Disable automatic repairs during doctor")
   .action(runCommand);
@@ -150,11 +144,7 @@ registerActivityCommands(program);
 registerDashboardCommands(program);
 registerRoutineCommands(program);
 registerFeedbackCommands(program);
-registerSecretCommands(program);
-registerCloudCommands(program);
-registerSkillsCommands(program);
 registerWorktreeCommands(program);
-registerEnvLabCommands(program);
 registerPluginCommands(program);
 
 const auth = program.command("auth").description("Authentication and bootstrap utilities");

cli/src/prompts/secrets.ts

@@ -32,7 +32,7 @@ export async function promptSecrets(current?: SecretsConfig): Promise<SecretsCon
       {
         value: "aws_secrets_manager" as const,
         label: "AWS Secrets Manager",
-        hint: "requires runtime AWS credentials and provider env config",
+        hint: "requires external adapter integration",
       },
       {
         value: "gcp_secret_manager" as const,
@@ -84,9 +84,7 @@ export async function promptSecrets(current?: SecretsConfig): Promise<SecretsCon
 
   if (provider !== "local_encrypted") {
     p.note(
-      provider === "aws_secrets_manager"
-        ? "AWS credentials must come from the Paperclip server runtime (IAM role/workload identity, AWS_PROFILE/SSO/shared credentials, or short-lived shell env), not from Paperclip company secrets."
-        : `${provider} is not fully wired in this build yet. Keep local_encrypted unless you are actively implementing that adapter.`,
+      `${provider} is not fully wired in this build yet. Keep local_encrypted unless you are actively implementing that adapter.`,
       "Heads up",
     );
   }

cli/src/prompts/server.ts

@@ -1,16 +1,6 @@
 import * as p from "@clack/prompts";
-import { isLoopbackHost, type BindMode } from "@paperclipai/shared";
 import type { AuthConfig, ServerConfig } from "../config/schema.js";
 import { parseHostnameCsv } from "../config/hostnames.js";
-import { buildCustomServerConfig, buildPresetServerConfig, inferConfiguredBind } from "../config/server-bind.js";
-
-const TAILNET_BIND_WARNING =
-  "No Tailscale address was detected during setup. The saved config will stay on loopback until Tailscale is available or PAPERCLIP_TAILNET_BIND_HOST is set.";
-
-function cancelled(): never {
-  p.cancel("Setup cancelled.");
-  process.exit(0);
-}
 
 export async function promptServer(opts?: {
   currentServer?: Partial<ServerConfig>;
@@ -18,37 +8,69 @@ export async function promptServer(opts?: {
 }): Promise<{ server: ServerConfig; auth: AuthConfig }> {
   const currentServer = opts?.currentServer;
   const currentAuth = opts?.currentAuth;
-  const currentBind = inferConfiguredBind(currentServer);
 
-  const bindSelection = await p.select({
-    message: "Reachability",
+  const deploymentModeSelection = await p.select({
+    message: "Deployment mode",
     options: [
       {
-        value: "loopback" as const,
-        label: "Trusted local",
-        hint: "Recommended for first run: localhost only, no login friction",
+        value: "local_trusted",
+        label: "Local trusted",
+        hint: "Easiest for local setup (no login, localhost-only)",
       },
       {
-        value: "lan" as const,
-        label: "Private network",
-        hint: "Broad private bind for LAN, VPN, or legacy --tailscale-auth style access",
-      },
-      {
-        value: "tailnet" as const,
-        label: "Tailnet",
-        hint: "Private authenticated access using the machine's detected Tailscale address",
-      },
-      {
-        value: "custom" as const,
-        label: "Custom",
-        hint: "Choose exact auth mode, exposure, and host manually",
+        value: "authenticated",
+        label: "Authenticated",
+        hint: "Login required; use for private network or public hosting",
       },
     ],
-    initialValue: currentBind,
+    initialValue: currentServer?.deploymentMode ?? "local_trusted",
   });
 
-  if (p.isCancel(bindSelection)) cancelled();
-  const bind = bindSelection as BindMode;
+  if (p.isCancel(deploymentModeSelection)) {
+    p.cancel("Setup cancelled.");
+    process.exit(0);
+  }
+  const deploymentMode = deploymentModeSelection as ServerConfig["deploymentMode"];
+
+  let exposure: ServerConfig["exposure"] = "private";
+  if (deploymentMode === "authenticated") {
+    const exposureSelection = await p.select({
+      message: "Exposure profile",
+      options: [
+        {
+          value: "private",
+          label: "Private network",
+          hint: "Private access (for example Tailscale), lower setup friction",
+        },
+        {
+          value: "public",
+          label: "Public internet",
+          hint: "Internet-facing deployment with stricter requirements",
+        },
+      ],
+      initialValue: currentServer?.exposure ?? "private",
+    });
+    if (p.isCancel(exposureSelection)) {
+      p.cancel("Setup cancelled.");
+      process.exit(0);
+    }
+    exposure = exposureSelection as ServerConfig["exposure"];
+  }
+
+  const hostDefault = deploymentMode === "local_trusted" ? "127.0.0.1" : "0.0.0.0";
+  const hostStr = await p.text({
+    message: "Bind host",
+    defaultValue: currentServer?.host ?? hostDefault,
+    placeholder: hostDefault,
+    validate: (val) => {
+      if (!val.trim()) return "Host is required";
+    },
+  });
+
+  if (p.isCancel(hostStr)) {
+    p.cancel("Setup cancelled.");
+    process.exit(0);
+  }
 
   const portStr = await p.text({
     message: "Server port",
@@ -62,113 +84,15 @@ export async function promptServer(opts?: {
     },
   });
 
-  if (p.isCancel(portStr)) cancelled();
-  const port = Number(portStr) || 3100;
-  const serveUi = currentServer?.serveUi ?? true;
-
-  if (bind === "loopback") {
-    return buildPresetServerConfig("loopback", {
-      port,
-      allowedHostnames: [],
-      serveUi,
-    });
+  if (p.isCancel(portStr)) {
+    p.cancel("Setup cancelled.");
+    process.exit(0);
   }
 
-  if (bind === "lan" || bind === "tailnet") {
-    const allowedHostnamesInput = await p.text({
-      message: "Allowed private hostnames (comma-separated, optional)",
-      defaultValue: (currentServer?.allowedHostnames ?? []).join(", "),
-      placeholder:
-        bind === "tailnet"
-          ? "your-machine.tailnet.ts.net"
-          : "dotta-macbook-pro, host.docker.internal",
-      validate: (val) => {
-        try {
-          parseHostnameCsv(val);
-          return;
-        } catch (err) {
-          return err instanceof Error ? err.message : "Invalid hostname list";
-        }
-      },
-    });
-
-    if (p.isCancel(allowedHostnamesInput)) cancelled();
-
-    const preset = buildPresetServerConfig(bind, {
-      port,
-      allowedHostnames: parseHostnameCsv(allowedHostnamesInput),
-      serveUi,
-    });
-    if (bind === "tailnet" && isLoopbackHost(preset.server.host)) {
-      p.log.warn(TAILNET_BIND_WARNING);
-    }
-    return preset;
-  }
-
-  const deploymentModeSelection = await p.select({
-    message: "Auth mode",
-    options: [
-      {
-        value: "local_trusted",
-        label: "Local trusted",
-        hint: "No login required; only safe with loopback-only or similarly trusted access",
-      },
-      {
-        value: "authenticated",
-        label: "Authenticated",
-        hint: "Login required; supports both private-network and public deployments",
-      },
-    ],
-    initialValue: currentServer?.deploymentMode ?? "authenticated",
-  });
-
-  if (p.isCancel(deploymentModeSelection)) cancelled();
-  const deploymentMode = deploymentModeSelection as ServerConfig["deploymentMode"];
-
-  let exposure: ServerConfig["exposure"] = "private";
-  if (deploymentMode === "authenticated") {
-    const exposureSelection = await p.select({
-      message: "Exposure profile",
-      options: [
-        {
-          value: "private",
-          label: "Private network",
-          hint: "Private access only, with automatic URL handling",
-        },
-        {
-          value: "public",
-          label: "Public internet",
-          hint: "Internet-facing deployment with explicit public URL requirements",
-        },
-      ],
-      initialValue: currentServer?.exposure ?? "private",
-    });
-    if (p.isCancel(exposureSelection)) cancelled();
-    exposure = exposureSelection as ServerConfig["exposure"];
-  }
-
-  const defaultHost =
-    currentServer?.customBindHost ??
-    currentServer?.host ??
-    (deploymentMode === "local_trusted" ? "127.0.0.1" : "0.0.0.0");
-  const host = await p.text({
-    message: "Bind host",
-    defaultValue: defaultHost,
-    placeholder: defaultHost,
-    validate: (val) => {
-      if (!val.trim()) return "Host is required";
-      if (deploymentMode === "local_trusted" && !isLoopbackHost(val.trim())) {
-        return "Local trusted mode requires a loopback host such as 127.0.0.1";
-      }
-    },
-  });
-
-  if (p.isCancel(host)) cancelled();
-
   let allowedHostnames: string[] = [];
   if (deploymentMode === "authenticated" && exposure === "private") {
     const allowedHostnamesInput = await p.text({
-      message: "Allowed private hostnames (comma-separated, optional)",
+      message: "Allowed hostnames (comma-separated, optional)",
       defaultValue: (currentServer?.allowedHostnames ?? []).join(", "),
       placeholder: "dotta-macbook-pro, your-host.tailnet.ts.net",
       validate: (val) => {
@@ -181,11 +105,15 @@ export async function promptServer(opts?: {
       },
     });
 
-    if (p.isCancel(allowedHostnamesInput)) cancelled();
+    if (p.isCancel(allowedHostnamesInput)) {
+      p.cancel("Setup cancelled.");
+      process.exit(0);
+    }
     allowedHostnames = parseHostnameCsv(allowedHostnamesInput);
   }
 
-  let publicBaseUrl: string | undefined;
+  const port = Number(portStr) || 3100;
+  let auth: AuthConfig = { baseUrlMode: "auto", disableSignUp: false };
   if (deploymentMode === "authenticated" && exposure === "public") {
     const urlInput = await p.text({
       message: "Public base URL",
@@ -205,17 +133,32 @@ export async function promptServer(opts?: {
         }
       },
     });
-    if (p.isCancel(urlInput)) cancelled();
-    publicBaseUrl = urlInput.trim().replace(/\/+$/, "");
+    if (p.isCancel(urlInput)) {
+      p.cancel("Setup cancelled.");
+      process.exit(0);
+    }
+    auth = {
+      baseUrlMode: "explicit",
+      disableSignUp: false,
+      publicBaseUrl: urlInput.trim().replace(/\/+$/, ""),
+    };
+  } else if (currentAuth?.baseUrlMode === "explicit" && currentAuth.publicBaseUrl) {
+    auth = {
+      baseUrlMode: "explicit",
+      disableSignUp: false,
+      publicBaseUrl: currentAuth.publicBaseUrl,
+    };
   }
 
-  return buildCustomServerConfig({
-    deploymentMode,
-    exposure,
-    host: host.trim(),
-    port,
-    allowedHostnames,
-    serveUi,
-    publicBaseUrl,
-  });
+  return {
+    server: {
+      deploymentMode,
+      exposure,
+      host: hostStr.trim(),
+      port,
+      allowedHostnames,
+      serveUi: currentServer?.serveUi ?? true,
+    },
+    auth,
+  };
 }

cli/tsconfig.json

@@ -4,5 +4,5 @@
     "outDir": "dist",
     "rootDir": ".."
   },
-  "include": ["src", "../packages/shared/src", "../packages/plugins/create-paperclip-plugin/src"]
+  "include": ["src", "../packages/shared/src"]
 }

doc/CLI.md

@@ -2,7 +2,7 @@
 
 Paperclip CLI now supports both:
 
-- instance setup/diagnostics (`onboard`, `doctor`, `configure`, `env`, `allowed-hostname`, `env-lab`)
+- instance setup/diagnostics (`onboard`, `doctor`, `configure`, `env`, `allowed-hostname`)
 - control-plane client operations (issues, approvals, agents, activity, dashboard)
 
 ## Base Usage
@@ -32,12 +32,10 @@ Mode taxonomy and design intent are documented in `doc/DEPLOYMENT-MODES.md`.
 Current CLI behavior:
 
 - `paperclipai onboard` and `paperclipai configure --section server` set deployment mode in config
-- server onboarding/configure ask for reachability intent and write `server.bind`
-- `paperclipai run --bind <loopback|lan|tailnet>` passes a quickstart bind preset into first-run onboarding when config is missing
 - runtime can override mode with `PAPERCLIP_DEPLOYMENT_MODE`
-- `paperclipai run` and `paperclipai doctor` still do not expose a direct low-level `--mode` flag
+- `paperclipai run` and `paperclipai doctor` do not yet expose a direct `--mode` flag
 
-Canonical behavior is documented in `doc/DEPLOYMENT-MODES.md`.
+Target behavior (planned) is documented in `doc/DEPLOYMENT-MODES.md` section 5.
 
 Allow an authenticated/private hostname (for example custom Tailscale DNS):
 
@@ -45,15 +43,6 @@ Allow an authenticated/private hostname (for example custom Tailscale DNS):
 pnpm paperclipai allowed-hostname dotta-macbook-pro
 ```
 
-Bring up the default local SSH fixture for environment testing:
-
-```sh
-pnpm paperclipai env-lab up
-pnpm paperclipai env-lab doctor
-pnpm paperclipai env-lab status --json
-pnpm paperclipai env-lab down
-```
-
 All client commands support:
 
 - `--data-dir <path>`
@@ -143,150 +132,6 @@ pnpm paperclipai agent local-cli codexcoder --company-id <company-id>
 pnpm paperclipai agent local-cli claudecoder --company-id <company-id>
 ```
 
-## Skills Commands
-
-`paperclipai skills` covers three distinct operations:
-
-1. **Company install** — adds or updates a row in `company_skills` for the
-   whole company. This is what `skills install`, `skills import`, `skills create`,
-   and `skills scan-projects` do.
-2. **Agent attach** — replaces an agent's *desired* company skill set
-   (`skills agent sync`/`clear`). This is a desired-state operation on the
-   agent's adapter config; it does not change the company library.
-3. **Adapter runtime sync** — the adapter reconciles the desired skill set
-   with files on disk and reports an `AgentSkillSnapshot` (`skills agent list`).
-   `skills agent sync` triggers this automatically after updating desired state.
-
-Required Paperclip runtime skills (heartbeat, etc.) remain server-enforced and
-are added on top of whatever the desired set names.
-
-### Catalog (app-shipped skills)
-
-The Paperclip app ships a curated catalog under `@paperclipai/skills-catalog`.
-Browse and inspect commands never mutate company state; `install` adds a catalog
-skill to the company library.
-
-```sh
-pnpm paperclipai skills browse [--kind bundled|optional] [--category <slug>] [--query <text>]
-pnpm paperclipai skills search "<text>" [--kind bundled|optional] [--category <slug>]
-pnpm paperclipai skills inspect <catalog-id-or-key-or-slug>
-pnpm paperclipai skills install <catalog-id-or-key-or-slug> [--as <slug>] [--force] --company-id <company-id>
-```
-
-Catalog semantics:
-
-- **Bundled** skills live in `packages/skills-catalog/catalog/bundled/<category>/<slug>`
-  and are recommended defaults for most companies. They use canonical key
-  `paperclipai/bundled/<category>/<slug>`.
-- **Optional** skills live in `packages/skills-catalog/catalog/optional/<category>/<slug>`
-  and are role-specific or domain-specific (browser, AWS ops, etc.). Same key
-  shape with `optional` in place of `bundled`.
-- `skills install` materializes the catalog files into a company-managed skill
-  directory and records provenance (`catalogId`, `catalogKey`, `packageVersion`,
-  `originHash`, …) so future updates and audit decisions stay consistent.
-- `--as <slug>` overrides the company skill slug. `--force` may replace a
-  same-key catalog-managed skill but never bypasses hard validation or hard-stop
-  audit findings.
-
-Examples:
-
-```sh
-pnpm paperclipai skills browse --kind bundled --company-id <company-id>
-pnpm paperclipai skills search "pull request" --kind bundled
-pnpm paperclipai skills inspect github-pr-workflow
-pnpm paperclipai skills install github-pr-workflow --company-id <company-id>
-pnpm paperclipai skills install paperclipai:optional:browser:agent-browser --company-id <company-id>
-```
-
-External GitHub, skills.sh, local-path, and URL sources still go through
-`skills import`; catalog commands are for the app-shipped catalog only.
-
-### Company library
-
-```sh
-pnpm paperclipai skills list --company-id <company-id>
-pnpm paperclipai skills show <skill-id-or-key-or-slug> --company-id <company-id>
-pnpm paperclipai skills file <skill-id-or-key-or-slug> [--path SKILL.md] --company-id <company-id>
-pnpm paperclipai skills import <source> --company-id <company-id>
-pnpm paperclipai skills create --name "Review PRs" [--slug review-prs] [--description "..."] [--body-file SKILL.md] --company-id <company-id>
-pnpm paperclipai skills scan-projects [--project-id <id>...] [--workspace-id <id>...] --company-id <company-id>
-pnpm paperclipai skills check [skill-id-or-key-or-slug] --company-id <company-id>
-pnpm paperclipai skills update <skill-id-or-key-or-slug> [--force] --company-id <company-id>
-pnpm paperclipai skills update --all [--force] --company-id <company-id>
-pnpm paperclipai skills audit [skill-id-or-key-or-slug] --company-id <company-id>
-pnpm paperclipai skills reset <skill-id-or-key-or-slug> [--yes] [--force] --company-id <company-id>
-pnpm paperclipai skills remove <skill-id-or-key-or-slug> --yes --company-id <company-id>
-```
-
-`skills import <source>` accepts a skills.sh URL, the equivalent
-`<owner>/<repo>/<skill>` shorthand, a GitHub URL, a local path, or an
-`npx skills add …` command. See `references/company-skills.md` in the agent
-skill bundle for the source-type table.
-
-`skills check`, `skills update`, `skills audit`, and `skills reset` are the
-maintenance loop for catalog-installed skills:
-
-- `check` reports whether each skill's installed bytes match its pinned origin
-  (`hasUpdate`, `installedHash`, `originHash`, `updateHoldReason`,
-  `auditVerdict`).
-- `update` installs the pinned update through the existing install-update API.
-  `--all` checks every company skill and updates only those with
-  `hasUpdate=true`. `--force` discards local-modification or soft-audit holds;
-  hard-stop audit findings still block the update.
-- `audit` re-scans installed bytes and reports findings without executing
-  anything.
-- `reset` reinstalls a catalog-managed skill from its pinned origin, discarding
-  local edits. Prompts in a TTY; requires `--yes` for non-interactive use.
-
-### Agent attach
-
-```sh
-pnpm paperclipai skills agent list <agent-id-or-shortname> --company-id <company-id>
-pnpm paperclipai skills agent sync <agent-id-or-shortname> --skill <skill-id-or-key-or-slug> [--skill <skill-id-or-key-or-slug>...] --company-id <company-id>
-pnpm paperclipai skills agent clear <agent-id-or-shortname> --yes --company-id <company-id>
-```
-
-`skills agent sync` replaces the agent's non-required desired skill set (it is
-not additive) and returns the resulting adapter `AgentSkillSnapshot`.
-`skills agent clear` sends an empty desired list. Required Paperclip skills are
-still enforced by the server in both cases.
-
-### Notes
-
-- Skill references accept company skill `id`, canonical `key`, or unique
-  `slug`; catalog references accept catalog `id`, `key`, or unique `slug`.
-- `skills file` prints raw file content in human mode so it can be piped.
-- `skills create --body-file -` reads the skill markdown body from stdin.
-- `skills remove`, `skills reset`, and `skills agent clear` prompt in a TTY and
-  require `--yes` in non-interactive use.
-- `--json` prints the raw API result for each command.
-
-## Secrets Commands
-
-```sh
-pnpm paperclipai secrets list --company-id <company-id>
-pnpm paperclipai secrets declarations --company-id <company-id> [--include agents,projects] [--kind secret]
-pnpm paperclipai secrets create --company-id <company-id> --name anthropic-api-key --value-env ANTHROPIC_API_KEY
-pnpm paperclipai secrets link --company-id <company-id> --name prod-stripe-key --provider aws_secrets_manager --external-ref <provider-ref>
-pnpm paperclipai secrets doctor --company-id <company-id>
-pnpm paperclipai secrets migrate-inline-env --company-id <company-id> [--apply]
-```
-
-Secret listing and declarations never print secret values. `create` accepts
-`--value-env` so shell history does not capture the value. `link` records
-provider-owned references without copying the secret value into Paperclip.
-For AWS-backed secrets, `secrets doctor` reports missing non-secret provider
-env and the expected AWS SDK runtime credential source; do not store AWS
-bootstrap credentials in Paperclip secrets.
-
-Per-company provider vaults (multiple vault instances per provider, default
-vault selection, coming-soon GCP/Vault) are configured from the board UI under
-`Company Settings → Secrets → Provider vaults` or through
-`/api/companies/{companyId}/secret-provider-configs`. There is no CLI surface
-for vault management today. See the
-[secrets deploy guide](../docs/deploy/secrets.md#provider-vaults) and
-[API reference](../docs/api/secrets.md#provider-vaults) for the contract.
-
 ## Approval Commands
 
 ```sh
@@ -322,28 +167,7 @@ pnpm paperclipai heartbeat run --agent-id <agent-id> [--api-base http://localhos
 
 ## Local Storage Defaults
 
-Local Paperclip data lives under the selected instance root. `PAPERCLIP_HOME` chooses the home directory and `PAPERCLIP_INSTANCE_ID` chooses the instance.
-
-```text
-~/.paperclip/                                     # PAPERCLIP_HOME
-└── instances/
-    └── default/                                  # instance root (PAPERCLIP_INSTANCE_ID)
-        ├── config.json                           # runtime config
-        ├── .env                                  # instance env file
-        ├── db/                                   # embedded PostgreSQL data
-        ├── data/
-        │   ├── storage/                          # local_disk uploads
-        │   └── backups/                          # automatic DB backups
-        ├── logs/
-        ├── secrets/
-        │   └── master.key                        # local_encrypted master key
-        ├── workspaces/                           # default agent workspaces
-        ├── projects/                             # project execution workspaces
-        ├── companies/                            # per-company adapter homes (e.g. codex-home)
-        └── codex-home/                           # per-instance codex home (when not company-scoped)
-```
-
-Default paths for the canonical install:
+Default local instance root is `~/.paperclip/instances/default`:
 
 - config: `~/.paperclip/instances/default/config.json`
 - embedded db: `~/.paperclip/instances/default/db`

doc/DATABASE.md

@@ -27,18 +27,6 @@ pnpm db:migrate
 
 When `DATABASE_URL` is unset, this command targets the current embedded PostgreSQL instance for your active Paperclip config/instance.
 
-Issue reference mentions follow the normal migration path: the schema migration creates the tracking table, but it does not backfill historical issue titles, descriptions, comments, or documents automatically.
-
-To backfill existing content manually after migrating, run:
-
-```sh
-pnpm issue-references:backfill
-# optional: limit to one company
-pnpm issue-references:backfill -- --company <company-id>
-```
-
-Future issue, comment, and document writes sync references automatically without running the backfill command.
-
 This mode is ideal for local development and one-command installs.
 
 Docker note: the Docker quickstart image also uses embedded PostgreSQL by default. Persist `/paperclip` to keep DB state across container restarts (see `doc/DOCKER.md`).
@@ -59,11 +47,11 @@ cp .env.example .env
 # DATABASE_URL=postgres://paperclip:paperclip@localhost:5432/paperclip
 ```
 
-Run migrations:
+Run migrations (once the migration generation issue is fixed) or use `drizzle-kit push`:
 
 ```sh
 DATABASE_URL=postgres://paperclip:paperclip@localhost:5432/paperclip \
-  pnpm db:migrate
+  npx drizzle-kit push
 ```
 
 Start the server:
@@ -100,27 +88,27 @@ postgres://postgres.[PROJECT-REF]:[PASSWORD]@aws-0-[REGION].pooler.supabase.com:
 
 ### Configure
 
-For the application runtime, use a direct PostgreSQL connection unless the database client has explicit prepared-statement configuration for your pooling mode:
-
-```sh
-DATABASE_URL=postgres://postgres.[PROJECT-REF]:[PASSWORD]@aws-0-[REGION].pooler.supabase.com:5432/postgres
-```
-
-If you later run the app with a pooled runtime URL, set `DATABASE_MIGRATION_URL` to the direct connection URL. Paperclip uses it for startup schema checks/migrations and plugin namespace migrations, while the app continues to use `DATABASE_URL` for runtime queries:
+Set `DATABASE_URL` in your `.env`:
 
 ```sh
 DATABASE_URL=postgres://postgres.[PROJECT-REF]:[PASSWORD]@aws-0-[REGION].pooler.supabase.com:6543/postgres
-DATABASE_MIGRATION_URL=postgres://postgres.[PROJECT-REF]:[PASSWORD]@aws-0-[REGION].pooler.supabase.com:5432/postgres
 ```
 
-If your hosted database requires transaction-pooling-only connections, use a direct or session-pooled connection for Paperclip until runtime pooling support is documented in this guide. Do not edit database client source files as part of deployment setup.
+If using connection pooling (port 6543), the `postgres` client must disable prepared statements. Update `packages/db/src/client.ts`:
+
+```ts
+export function createDb(url: string) {
+  const sql = postgres(url, { prepare: false });
+  return drizzlePg(sql, { schema });
+}
+```
 
 ### Push the schema
 
 ```sh
 # Use the direct connection (port 5432) for schema changes
 DATABASE_URL=postgres://postgres.[PROJECT-REF]:[PASSWORD]@...5432/postgres \
-  pnpm db:migrate
+  npx drizzle-kit push
 ```
 
 ### Free tier limits
@@ -143,51 +131,18 @@ The database mode is controlled by `DATABASE_URL`:
 
 Your Drizzle schema (`packages/db/src/schema/`) stays the same regardless of mode.
 
-## Resource membership tables
-
-Paperclip stores current-user sidebar membership state in:
-
-- `project_memberships`
-- `agent_memberships`
-
-These rows are company-scoped and user-scoped. A missing row means the user is joined, so existing users keep seeing projects and agents in the sidebar until they explicitly leave them. Rows only control sidebar visibility; they do not affect project/agent detail access, all-pages, selectors, assignment flows, or existing company permissions.
-
-Both tables use a unique key on `(company_id, user_id, resource_id)` and keep `state` as `joined` or `left`. Join/leave mutations are idempotent board-user `/me` operations and write activity entries when the effective state changes.
-
-## Plugin database namespaces
-
-The plugin runtime tracks plugin-owned database namespaces and migrations in `plugin_database_namespaces` and `plugin_migrations`. Hosted deployments that separate runtime and migration connections should set `DATABASE_MIGRATION_URL`; plugin namespace migration work uses the migration connection when present.
-
-## Backups
-
-Paperclip supports automatic and manual logical database backups. These dumps include
-non-system database schemas such as `public`, the Drizzle migration journal, and
-plugin-owned database schemas. See `doc/DEVELOPING.md` for the current
-`paperclipai db:backup` / `pnpm db:backup` commands and backup retention
-configuration.
-
-Database backups do not include non-database instance files such as local-disk
-uploads, workspace files, or the local encrypted secrets master key. Back those paths
-up separately when you need full instance disaster recovery.
-
 ## Secret storage
 
 Paperclip stores secret metadata and versions in:
 
 - `company_secrets`
 - `company_secret_versions`
-- `company_secret_bindings`
-- `secret_access_events`
-
-Secret-aware env bindings are supported by agents, projects, and routines. Routine env lives in `routines.env`, is captured in `routine_revisions.snapshot`, and routine dispatches store `routine_runs.routine_revision_id` so runtime secret resolution uses the env snapshot that existed when the run was created. Routine secret refs bind with `target_type = 'routine'`, `target_id = routines.id`, and `config_path` values under `env.*`.
 
 For local/default installs, the active provider is `local_encrypted`:
 
 - Secret material is encrypted at rest with a local master key.
 - Default key file: `~/.paperclip/instances/default/secrets/master.key` (auto-created if missing).
 - CLI config location: `~/.paperclip/instances/default/config.json` under `secrets.localEncrypted.keyFilePath`.
-- Backup/restore requires both the database metadata and the local master key file; either artifact alone is insufficient.
-- The server best-effort enforces `0600` key file permissions and provider health reports permission warnings.
 
 Optional overrides:
 
@@ -209,10 +164,5 @@ pnpm paperclipai configure --section secrets
 Inline secret migration command:
 
 ```sh
-pnpm paperclipai secrets migrate-inline-env --company-id <company-id> --apply
-
-# direct database maintenance fallback
 pnpm secrets:migrate-inline-env --apply
 ```
-
-Hosted AWS provider notes live in [SECRETS-AWS-PROVIDER.md](./SECRETS-AWS-PROVIDER.md).

doc/DEPLOYMENT-MODES.md

@@ -17,11 +17,6 @@ Paperclip supports two runtime modes:
 
 This keeps one authenticated auth stack while still separating low-friction private-network defaults from internet-facing hardening requirements.
 
-Paperclip now treats **bind** as a separate concern from auth:
-
-- auth model: `local_trusted` vs `authenticated`, plus `private/public`
-- reachability model: `server.bind = loopback | lan | tailnet | custom`
-
 ## 2. Canonical Model
 
 | Runtime Mode | Exposure | Human auth | Primary use |
@@ -30,15 +25,6 @@ Paperclip now treats **bind** as a separate concern from auth:
 | `authenticated` | `private` | Login required | Private-network access (for example Tailscale/VPN/LAN) |
 | `authenticated` | `public` | Login required | Internet-facing/cloud deployment |
 
-## Reachability Model
-
-| Bind | Meaning | Typical use |
-|---|---|---|
-| `loopback` | Listen on localhost only | default local usage, reverse-proxy deployments |
-| `lan` | Listen on all interfaces (`0.0.0.0`) | LAN/VPN/private-network access |
-| `tailnet` | Listen on a detected Tailscale IP | Tailscale-only access |
-| `custom` | Listen on an explicit host/IP | advanced interface-specific setups |
-
 ## 3. Security Policy
 
 ## `local_trusted`
@@ -52,14 +38,12 @@ Paperclip now treats **bind** as a separate concern from auth:
 - login required
 - low-friction URL handling (`auto` base URL mode)
 - private-host trust policy required
-- bind can be `loopback`, `lan`, `tailnet`, or `custom`
 
 ## `authenticated + public`
 
 - login required
 - explicit public URL required
 - stricter deployment checks and failures in doctor
-- recommended bind is `loopback` behind a reverse proxy; direct `lan/custom` is advanced
 
 ## 4. Onboarding UX Contract
 
@@ -71,22 +55,14 @@ pnpm paperclipai onboard
 
 Server prompt behavior:
 
-1. quickstart `--yes` defaults to `server.bind=loopback` and therefore `local_trusted/private`
-2. advanced server setup asks reachability first:
-- `Trusted local` → `bind=loopback`, `local_trusted/private`
-- `Private network` → `bind=lan`, `authenticated/private`
-- `Tailnet` → `bind=tailnet`, `authenticated/private`
-- `Custom` → manual mode/exposure/host entry
-3. raw host entry is only required for the `Custom` path
-4. explicit public URL is only required for `authenticated + public`
-
-Examples:
-
-```sh
-pnpm paperclipai onboard --yes
-pnpm paperclipai onboard --yes --bind lan
-pnpm paperclipai run --bind tailnet
-```
+1. ask mode, default `local_trusted`
+2. option copy:
+- `local_trusted`: "Easiest for local setup (no login, localhost-only)"
+- `authenticated`: "Login required; use for private network or public hosting"
+3. if `authenticated`, ask exposure:
+- `private`: "Private network access (for example Tailscale), lower setup friction"
+- `public`: "Internet-facing deployment, stricter security requirements"
+4. ask explicit public URL only for `authenticated + public`
 
 `configure --section server` follows the same interactive behavior.
 
@@ -125,52 +101,20 @@ When running `authenticated` mode, if the only instance admin is `local-board`,
 
 This prevents lockout when a user migrates from long-running local trusted usage to authenticated mode.
 
-## 8. First Admin Setup For Fresh Authenticated Installs
-
-Fresh authenticated installs start in `bootstrap_pending` until the first
-`instance_admin` exists.
-
-For `authenticated/private`, Paperclip supports a browser-first setup path:
-
-1. open the Paperclip URL from the private network or appliance UI
-2. sign in or create a Paperclip account
-3. choose `Claim this instance` on the setup screen
-
-That browser claim promotes the signed-in session user to the first instance
-admin and then falls through to normal onboarding. The endpoint is available
-only to real browser session actors in `authenticated/private`; unauthenticated
-requests, agent keys, board API keys, and local implicit board actors are
-rejected.
-
-The CLI fallback remains supported in all authenticated setup states:
-
-```sh
-pnpm paperclipai auth bootstrap-ceo
-```
-
-That command prints a one-time first-admin invite URL. Browser claim and
-bootstrap invite acceptance share the same first-admin transaction, so whichever
-path wins first makes later attempts return a conflict.
-
-For `authenticated/public`, browser first-admin claim is intentionally disabled.
-Public deployments must use the high-entropy bootstrap invite path unless a
-future public-hosted setup design explicitly changes this policy.
-
-## 9. Current Code Reality (As Of 2026-02-23)
+## 8. Current Code Reality (As Of 2026-02-23)
 
 - runtime values are `local_trusted | authenticated`
 - `authenticated` uses Better Auth sessions and bootstrap invite flow
 - `local_trusted` ensures a real local Board user principal in `authUsers` with `instance_user_roles` admin access
 - company creation ensures creator membership in `company_memberships` so user assignment/access flows remain consistent
 
-## 10. Naming and Compatibility Policy
+## 9. Naming and Compatibility Policy
 
 - canonical naming is `local_trusted` and `authenticated` with `private/public` exposure
 - no long-term compatibility alias layer for discarded naming variants
 
-## 11. Relationship to Other Docs
+## 10. Relationship to Other Docs
 
 - implementation plan: `doc/plans/deployment-auth-mode-consolidation.md`
 - V1 contract: `doc/SPEC-implementation.md`
 - operator workflows: `doc/DEVELOPING.md` and `doc/CLI.md`
-- invite/join state map: `doc/spec/invite-flow.md`

doc/DEVELOPING.md

@@ -43,19 +43,6 @@ This starts:
 
 `pnpm dev` and `pnpm dev:once` are now idempotent for the current repo and instance: if the matching Paperclip dev runner is already alive, Paperclip reports the existing process instead of starting a duplicate.
 
-Issue execution may also use project execution workspace policies and workspace runtime services for per-project worktrees, preview servers, and managed dev commands. Configure those through the project workspace/runtime surfaces rather than starting long-running unmanaged processes when a task needs a reusable service.
-
-## Storybook
-
-The board UI Storybook keeps stories and Storybook config under `ui/storybook/` so component review files stay out of the app source routes.
-
-```sh
-pnpm storybook
-pnpm build-storybook
-```
-
-These run the `@paperclipai/ui` Storybook on port `6006` and build the static output to `ui/storybook-static/`.
-
 Inspect or stop the current repo's managed dev runner:
 
 ```sh
@@ -67,63 +54,18 @@ pnpm dev:stop
 
 Tailscale/private-auth dev mode:
 
-```sh
-pnpm dev --bind lan
-```
-
-This runs dev as `authenticated/private` with a private-network bind preset.
-On a fresh authenticated/private instance, open the app, sign in or create an
-account, and use the setup screen to claim the first instance admin from the
-browser. The CLI fallback remains:
-
-```sh
-pnpm paperclipai auth bootstrap-ceo
-```
-
-For Tailscale-only reachability on a detected tailnet address:
-
-```sh
-pnpm dev --bind tailnet
-```
-
-Legacy aliases still map to the old broad private-network behavior:
-
 ```sh
 pnpm dev --tailscale-auth
-pnpm dev --authenticated-private
 ```
 
+This runs dev as `authenticated/private` and binds the server to `0.0.0.0` for private-network access.
+
 Allow additional private hostnames (for example custom Tailscale hostnames):
 
 ```sh
 pnpm paperclipai allowed-hostname dotta-macbook-pro
 ```
 
-## Test Commands
-
-Use the cheap local default unless you are specifically working on browser flows:
-
-```sh
-pnpm test
-```
-
-`pnpm test` runs the Vitest suite only. For interactive Vitest watch mode use:
-
-```sh
-pnpm test:watch
-```
-
-Browser suites stay separate:
-
-```sh
-pnpm test:e2e
-pnpm test:release-smoke
-```
-
-These browser suites are intended for targeted local verification and CI, not the default agent/human test command.
-
-For normal issue work, start with the smallest targeted check that proves the change. Reserve repo-wide typecheck/build/test runs for PR-ready handoff or changes broad enough that narrow checks do not cover the risk.
-
 ## One-Command Local Run
 
 For a first-time local install, you can bootstrap and run in one command:
@@ -164,27 +106,6 @@ See `doc/DOCKER.md` for API key wiring (`OPENAI_API_KEY` / `ANTHROPIC_API_KEY`)
 
 For a separate review-oriented container that keeps `codex`/`claude` login state in Docker volumes and checks out PRs into an isolated scratch workspace, see `doc/UNTRUSTED-PR-REVIEW.md`.
 
-## Local Instance Layout
-
-Every local install keeps runtime state directly under the selected instance root:
-
-```text
-~/.paperclip/instances/default/                  # instance root
-  config.json                                    # runtime config
-  .env                                           # instance env file
-  db/                                            # embedded PostgreSQL data
-  data/
-    storage/                                     # local_disk uploads
-    backups/                                     # automatic DB backups
-  logs/
-  secrets/master.key                             # local_encrypted master key
-  workspaces/<agent-id>/                         # default agent workspaces
-  projects/                                      # project execution workspaces
-  companies/<company-id>/codex-home/             # per-company codex_local home
-```
-
-`PAPERCLIP_HOME` and `PAPERCLIP_INSTANCE_ID` override the home root and instance id respectively. `paperclipai onboard` echoes the resolved values in its banner (`Local home: <home> | instance: <id> | config: <path>`) so you can confirm where state will land before continuing.
-
 ## Database in Dev (Auto-Handled)
 
 For local development, leave `DATABASE_URL` unset.
@@ -192,7 +113,7 @@ The server will automatically use embedded PostgreSQL and persist data at:
 
 - `~/.paperclip/instances/default/db`
 
-Override home or instance:
+Override home and instance:
 
 ```sh
 PAPERCLIP_HOME=/custom/path PAPERCLIP_INSTANCE_ID=dev pnpm paperclipai run
@@ -226,8 +147,6 @@ For `codex_local`, Paperclip also manages a per-company Codex home under the ins
 
 If the `codex` CLI is not installed or not on `PATH`, `codex_local` agent runs fail at execution time with a clear adapter error. Quota polling uses a short-lived `codex app-server` subprocess: when `codex` cannot be spawned, that provider reports `ok: false` in aggregated quota results and the API server keeps running (it must not exit on a missing binary).
 
-Local adapters require their corresponding CLI/session setup on the machine running Paperclip. External adapters are installed through the adapter/plugin flow and should not require hardcoded imports in `server/` or `ui/`.
-
 ## Worktree-local Instances
 
 When developing from multiple git worktrees, do not point two Paperclip servers at the same embedded PostgreSQL data directory.
@@ -254,13 +173,9 @@ Seed modes:
 - `full` makes a full logical clone of the source instance
 - `--no-seed` creates an empty isolated instance
 
-Seeded worktree instances quarantine copied live execution by default for both `minimal` and `full` seeds. During restore, Paperclip disables copied agent timer heartbeats, resets copied `running` agents to `idle`, blocks and unassigns copied agent-owned `in_progress` issues, and unassigns copied agent-owned `todo`/`in_review` issues. This keeps a freshly booted worktree from starting agents for work already owned by the source instance. Pass `--preserve-live-work` only when you intentionally want the isolated worktree to resume copied assignments.
-
 After `worktree init`, both the server and the CLI auto-load the repo-local `.paperclip/.env` when run inside that worktree, so normal commands like `pnpm dev`, `paperclipai doctor`, and `paperclipai db:backup` stay scoped to the worktree instance.
 
-`pnpm dev` now fails fast in a linked git worktree when `.paperclip/.env` is missing, instead of silently booting against the default instance/port. If that happens, run `paperclipai worktree init` in the worktree first.
-
-Provisioned git worktrees also pause seeded routines that still have enabled schedule triggers in the isolated worktree database by default. This prevents copied daily/cron routines from firing unexpectedly inside the new workspace instance during development without disabling webhook/API-only routines.
+Provisioned git worktrees also pause all seeded routines in the isolated worktree database by default. This prevents copied daily/cron routines from firing unexpectedly inside the new workspace instance during development.
 
 That repo-local env also sets:
 
@@ -269,8 +184,6 @@ That repo-local env also sets:
 - `PAPERCLIP_WORKTREE_COLOR=<hex-color>`
 
 The server/UI use those values for worktree-specific branding such as the top banner and dynamically colored favicon.
-Authenticated worktree servers also use the `PAPERCLIP_INSTANCE_ID` value to scope Better Auth cookie names.
-Browser cookies are shared by host rather than port, so this prevents logging into one `127.0.0.1:<port>` worktree from replacing another worktree server's session cookie.
 
 Print shell exports explicitly when needed:
 
@@ -308,10 +221,10 @@ paperclipai worktree init --from-data-dir ~/.paperclip
 paperclipai worktree init --force
 ```
 
-Repair an already-created repo-managed worktree and reseed its isolated instance from the main default install. Point `--from-config` at the instance config:
+Repair an already-created repo-managed worktree and reseed its isolated instance from the main default install:
 
 ```sh
-cd /path/to/paperclip/.paperclip/worktrees/PAP-884-ai-commits-component
+cd ~/.paperclip/worktrees/PAP-884-ai-commits-component
 pnpm paperclipai worktree init --force --seed-mode minimal \
   --name PAP-884-ai-commits-component \
   --from-config ~/.paperclip/instances/default/config.json
@@ -319,33 +232,6 @@ pnpm paperclipai worktree init --force --seed-mode minimal \
 
 That rewrites the worktree-local `.paperclip/config.json` + `.paperclip/.env`, recreates the isolated instance under `~/.paperclip-worktrees/instances/<worktree-id>/`, and preserves the git worktree contents themselves.
 
-For an already-created worktree where you want the CLI to decide whether to rebuild missing worktree metadata or just reseed the isolated DB, use `worktree repair`.
-
-**`pnpm paperclipai worktree repair [options]`** — Repair the current linked worktree by default, or create/repair a named linked worktree under `.paperclip/worktrees/` when `--branch` is provided. The command never targets the primary checkout unless you explicitly pass `--branch`.
-
-| Option | Description |
-|---|---|
-| `--branch <name>` | Existing branch/worktree selector to repair, or a branch name to create under `.paperclip/worktrees` |
-| `--home <path>` | Home root for worktree instances (default: `~/.paperclip-worktrees`) |
-| `--from-config <path>` | Source config.json to seed from |
-| `--from-data-dir <path>` | Source `PAPERCLIP_HOME` used when deriving the source config |
-| `--from-instance <id>` | Source instance id when deriving the source config (default: `default`) |
-| `--seed-mode <mode>` | Seed profile: `minimal` or `full` (default: `minimal`) |
-| `--no-seed` | Repair metadata only when bootstrapping a missing worktree config |
-| `--allow-live-target` | Override the guard that requires the target worktree DB to be stopped first |
-
-Examples:
-
-```sh
-# From inside a linked worktree, rebuild missing .paperclip metadata and reseed it from the default instance.
-cd /path/to/paperclip/.paperclip/worktrees/PAP-1132-assistant-ui-pap-1131-make-issues-comments-be-like-a-chat
-pnpm paperclipai worktree repair
-
-# From the primary checkout, create or repair a linked worktree for a branch under .paperclip/worktrees/.
-cd /path/to/paperclip
-pnpm paperclipai worktree repair --branch PAP-1132-assistant-ui-pap-1131-make-issues-comments-be-like-a-chat
-```
-
 For an already-created worktree where you want to keep the existing repo-local config/env and only overwrite the isolated database, use `worktree reseed` instead. Stop the target worktree's Paperclip server first so the command can replace the DB safely.
 
 **`pnpm paperclipai worktree reseed [options]`** — Re-seed an existing worktree-local instance from another Paperclip instance or worktree while preserving the target worktree's current config, ports, and instance identity.
@@ -420,62 +306,6 @@ eval "$(pnpm paperclipai worktree env)"
 
 For project execution worktrees, Paperclip can also run a project-defined provision command after it creates or reuses an isolated git worktree. Configure this on the project's execution workspace policy (`workspaceStrategy.provisionCommand`). The command runs inside the derived worktree and receives `PAPERCLIP_WORKSPACE_*`, `PAPERCLIP_PROJECT_ID`, `PAPERCLIP_AGENT_ID`, and `PAPERCLIP_ISSUE_*` environment variables so each repo can bootstrap itself however it wants.
 
-## App-Shipped Skills Catalog
-
-The Paperclip app ships a curated catalog of company skills out of the box. The
-catalog is a workspace package at `packages/skills-catalog`:
-
-```text
-packages/skills-catalog/
-  catalog/
-    bundled/<category>/<slug>/SKILL.md   # recommended defaults
-    optional/<category>/<slug>/SKILL.md  # role/domain-specific
-  generated/catalog.json                  # checked-in manifest
-  scripts/
-    build-catalog-manifest.ts             # regenerate generated/catalog.json
-    validate-catalog.ts                   # validation only
-  src/                                    # builder + types consumed by server/CLI
-```
-
-Server and CLI import the generated manifest; they do not crawl repository
-paths at request time. Root `skills/` remains reserved for Paperclip runtime
-skills and is not part of the catalog.
-
-Validate the catalog without writing the manifest:
-
-```sh
-pnpm --filter @paperclipai/skills-catalog validate
-```
-
-Regenerate `generated/catalog.json` after editing any catalog `SKILL.md`,
-frontmatter, file inventory, category, or slug:
-
-```sh
-pnpm --filter @paperclipai/skills-catalog build:manifest
-```
-
-The package's `build` script runs `build:manifest` and then `tsc`; tests live
-under `pnpm --filter @paperclipai/skills-catalog test`. Validation fails when:
-
-- a catalog entry is not under `catalog/bundled/<category>/<slug>` or
-  `catalog/optional/<category>/<slug>`
-- `SKILL.md` is missing or the frontmatter `name`/`description` is empty
-- the frontmatter `key` disagrees with the generated canonical key
-- two catalog entries share an `id`, `key`, or `slug`
-- file inventory contains absolute paths, `..`, broken symlinks, or files
-  outside the skill directory
-- the regenerated manifest differs from the checked-in
-  `generated/catalog.json`
-
-Trust level is derived from inventory: `markdown_only` (markdown + references
-only), `assets` (other non-script files), or `scripts_executables` (any
-executable script). The build contract is documented in
-`doc/plans/2026-05-26-skills-cli-catalog-contract.md`.
-
-CI runs `pnpm --filter @paperclipai/skills-catalog validate` and the package's
-vitest suite, so always regenerate the manifest in the same commit as the
-catalog change.
-
 ## Quick Health Checks
 
 In another terminal:
@@ -505,9 +335,7 @@ If you set `DATABASE_URL`, the server will use that instead of embedded PostgreS
 
 ## Automatic DB Backups
 
-Paperclip can run automatic logical database backups on a timer. These backups cover
-non-system database schemas, including migration history and plugin-owned database
-schemas. Defaults:
+Paperclip can run automatic DB backups on a timer. Defaults:
 
 - enabled
 - every 60 minutes
@@ -535,10 +363,6 @@ Environment overrides:
 - `PAPERCLIP_DB_BACKUP_RETENTION_DAYS=<days>`
 - `PAPERCLIP_DB_BACKUP_DIR=/absolute/or/~/path`
 
-DB backups are not full instance filesystem backups. For full local disaster
-recovery, also back up local storage files and the local encrypted secrets key if
-those providers are enabled.
-
 ## Secrets in Dev
 
 Agent env vars now support secret references. By default, secret values are stored with local encryption and only secret refs are persisted in agent config.
@@ -546,7 +370,6 @@ Agent env vars now support secret references. By default, secret values are stor
 - Default local key path: `~/.paperclip/instances/default/secrets/master.key`
 - Override key material directly: `PAPERCLIP_SECRETS_MASTER_KEY`
 - Override key file path: `PAPERCLIP_SECRETS_MASTER_KEY_FILE`
-- Back up the key file and database together; either one alone is not enough to restore local encrypted secrets.
 
 Strict mode (recommended outside local trusted machines):
 
@@ -555,20 +378,12 @@ PAPERCLIP_SECRETS_STRICT_MODE=true
 ```
 
 When strict mode is enabled, sensitive env keys (for example `*_API_KEY`, `*_TOKEN`, `*_SECRET`) must use secret references instead of inline plain values.
-Authenticated deployments default strict mode on unless explicitly overridden.
 
 CLI configuration support:
 
 - `pnpm paperclipai onboard` writes a default `secrets` config section (`local_encrypted`, strict mode off, key file path set) and creates a local key file when needed.
 - `pnpm paperclipai configure --section secrets` lets you update provider/strict mode/key path and creates the local key file when needed.
-- `pnpm paperclipai doctor` validates secrets adapter configuration, can create a missing local key file with `--repair`, and reports missing AWS Secrets Manager bootstrap env when that provider is selected.
-- Provider health is available at `GET /api/companies/:companyId/secret-providers/health` and reports local key permission warnings plus backup guidance.
-
-Per-company provider vaults are configured in the board UI under
-`Company Settings → Secrets → Provider vaults`, backed by
-`/api/companies/{companyId}/secret-provider-configs`. The CLI does not own
-vault lifecycle today. See `docs/deploy/secrets.md` (`Provider Vaults` section)
-for the operator model.
+- `pnpm paperclipai doctor` validates secrets adapter configuration and can create a missing local key file with `--repair`.
 
 Migration helper for existing inline env secrets:
 
@@ -617,12 +432,10 @@ pnpm paperclipai dashboard get
 
 See full command reference in `doc/CLI.md`.
 
-## Agent Invite Onboarding Endpoints
+## OpenClaw Invite Onboarding Endpoints
 
 Agent-oriented invite onboarding now exposes machine-readable API docs:
 
-The board UI generates agent onboarding prompts from the add-agent modal (`+` in the agent sidebar), so agent onboarding sits with the rest of agent creation rather than company member invite settings.
-
 - `GET /api/invites/:token` returns invite summary plus onboarding and skills index links.
 - `GET /api/invites/:token/onboarding` returns onboarding manifest details (registration endpoint, claim endpoint template, skill install hints).
 - `GET /api/invites/:token/onboarding.txt` returns a plain-text onboarding doc intended for both human operators and agents (llm.txt-style handoff), including optional inviter message and suggested network host candidates.
@@ -640,7 +453,7 @@ pnpm smoke:openclaw-join
 What it validates:
 
 - invite creation for agent-only join
-- agent join request using `adapterType=openclaw_gateway`
+- agent join request using `adapterType=openclaw`
 - board approval + one-time API key claim semantics
 - callback delivery on wakeup to a dockerized OpenClaw-style webhook receiver
 

doc/DOCKER.md

@@ -117,16 +117,6 @@ services:
 - bootstrap invite URL defaults
 - hostname allowlist defaults (hostname extracted from URL)
 
-For fresh `authenticated/private` Docker or appliance-style installs, the first
-admin can now be claimed entirely from the browser after sign-in. Open the
-Paperclip URL, sign in or create an account, then choose `Claim this instance`
-on the setup screen. This browser claim is disabled for `authenticated/public`;
-public deployments should run the high-entropy CLI invite fallback instead:
-
-```sh
-pnpm paperclipai auth bootstrap-ceo
-```
-
 Granular overrides remain available if needed (`PAPERCLIP_AUTH_PUBLIC_BASE_URL`, `BETTER_AUTH_URL`, `BETTER_AUTH_TRUSTED_ORIGINS`, `PAPERCLIP_ALLOWED_HOSTNAMES`).
 
 Set `PAPERCLIP_ALLOWED_HOSTNAMES` explicitly only when you need additional hostnames beyond the public URL host (for example Tailscale/LAN aliases or multiple private hostnames).

doc/GOAL.md

@@ -23,7 +23,7 @@ Paperclip is the command, communication, and control plane for a company of AI a
 - **Track work in real time** — see at any moment what every agent is working on
 - **Control costs** — token salary budgets per agent, spend tracking, burn rate
 - **Align to goals** — agents see how their work serves the bigger mission
-- **Preserve work context** — comments, documents, work products, attachments, and company state stay attached to the work
+- **Store company knowledge** — a shared brain for the organization
 
 ## Architecture
 
@@ -36,20 +36,17 @@ The central nervous system. Manages:
 - Agent registry and org chart
 - Task assignment and status
 - Budget and token spend tracking
-- Issue comments, documents, work products, attachments, and company state
+- Company knowledge base
 - Goal hierarchy (company → team → agent → task)
 - Heartbeat monitoring — know when agents are alive, idle, or stuck
 
-It also enforces execution-control semantics such as single-assignee issues, atomic checkout and execution locks, blockers, recovery issues, and workspace/runtime controls.
-
 ### 2. Execution Services (adapters)
 
-Agents run externally and report into the control plane. Adapters connect different execution environments and define how a heartbeat is invoked, observed, and cancelled:
+Agents run externally and report into the control plane. An agent is just Python code that gets kicked off and does work. Adapters connect different execution environments:
 
-- **Local CLI/session adapters** — built-in adapters for tools such as Claude Code, Codex, Gemini, OpenCode, Pi, and Cursor
-- **HTTP/process-style adapters** — command or webhook/API integrations for custom runtimes
-- **OpenClaw gateway** — integration for OpenClaw-style remote agents
-- **External adapter plugins** — dynamically loaded adapters installed outside the core app
+- **OpenClaw** — initial adapter target
+- **Heartbeat loop** — simple custom Python that loops, checks in, does work
+- **Others** — any runtime that can call an API
 
 The control plane doesn't run agents. It orchestrates them. Agents run wherever they run and phone home.
 

doc/OPENCLAW_ONBOARDING.md

@@ -3,7 +3,7 @@ Use this exact checklist.
 1. Start Paperclip in auth mode.
 ```bash
 cd <paperclip-repo-root>
-pnpm dev --bind lan
+pnpm dev --tailscale-auth
 ```
 Then verify:
 ```bash

doc/PRODUCT.md

@@ -32,14 +32,12 @@ Then you define who reports to the CEO: a CTO managing programmers, a CMO managi
 
 ### Agent Execution
 
-Paperclip supports several ways to run an agent's heartbeat:
+There are two fundamental modes for running an agent's heartbeat:
 
-1. **Local CLI/session adapters** — Paperclip starts or resumes local coding-tool sessions such as Claude Code, Codex, Gemini, OpenCode, Pi, and Cursor, then tracks the run.
-2. **Run a command** — Paperclip kicks off a process (shell command, Python script, etc.) and tracks it. The heartbeat is "execute this and monitor it."
-3. **Fire and forget a request** — Paperclip sends a webhook/API call to an externally running agent. The heartbeat is "notify this agent to wake up." OpenClaw-style hooks work this way.
-4. **External adapter plugins** — Paperclip loads adapter packages through the plugin/adapter flow so self-hosted installs can add runtimes without hardcoding them in core.
+1. **Run a command** — Paperclip kicks off a process (shell command, Python script, etc.) and tracks it. The heartbeat is "execute this and monitor it."
+2. **Fire and forget a request** — Paperclip sends a webhook/API call to an externally running agent. The heartbeat is "notify this agent to wake up." (OpenClaw hooks work this way.)
 
-Agent runs can use project and execution workspaces, managed runtime services such as preview/dev servers, adapter-specific session state, and HTTP/webhook-style execution. We provide sensible defaults, but the adapter is still the boundary: if a runtime can be invoked, observed, and authorized, Paperclip can coordinate it.
+We provide sensible defaults — a default agent that shells out to Claude Code or Codex with your configuration, remembers session IDs, runs basic scripts. But you can plug in anything.
 
 ### Task Management
 
@@ -56,7 +54,7 @@ I am researching the Facebook ads Granola uses (current task)
 
 Tasks have parentage. Every task exists in service of a parent task, all the way up to the company goal. This is what keeps autonomous agents aligned — they can always answer "why am I doing this?"
 
-The current issue model includes stable issue identifiers, parent/sub-issues, blockers, a single assignee, comments, issue documents, attachments and work products, and review/approval handoffs. That structure keeps work inspectable by both the board and agents while still allowing agents to decompose work into smaller tasks.
+More detailed task structure TBD.
 
 ## Principles
 
@@ -117,8 +115,7 @@ Paperclip’s core identity is a **control plane for autonomous AI companies**,
 
 - Do not make the core product a general chat app. The current product definition is explicitly task/comment-centric and “not a chatbot,” and that boundary is valuable.
 - Do not build a complete Jira/GitHub replacement. The repo/docs already position Paperclip as organization orchestration, not focused on pull-request review.
-- Do not build enterprise-grade RBAC first. Paperclip now has authenticated mode, company memberships, instance roles, and permission grants, but fine-grained enterprise governance should remain secondary to the core company control plane.
-- Do not interpret agent-level privacy flags as a project/issue privacy feature in V1; work visibility stays company-scoped.
+- Do not build enterprise-grade RBAC first. The current V1 spec still treats multi-board governance and fine-grained human permissions as out of scope, so the first multi-user version should be coarse and company-scoped.
 - Do not lead with raw bash logs and transcripts. Default view should be human-readable intent/progress, with raw detail beneath.
 - Do not force users to understand provider/API-key plumbing unless absolutely necessary. There are active onboarding/auth issues already; friction here is clearly real.
 
@@ -139,14 +136,11 @@ Paperclip’s core identity is a **control plane for autonomous AI companies**,
 5. **Output-first**
    Work is not done until the user can see the result: file, document, preview link, screenshot, plan, or PR.
 
-6. **Execution visibility without log worship**
-   Active runs, recovery issues, productivity review states, blockers, and work products should be first-class surfaces. Raw transcripts are available when needed, but they are not the primary product surface.
-
-7. **Local-first, cloud-ready**
+6. **Local-first, cloud-ready**
    The mental model should not change between local solo use and shared/private or public/cloud deployment.
 
-8. **Safe autonomy**
+7. **Safe autonomy**
    Auto mode is allowed; hidden token burn is not.
 
-9. **Thin core, rich edges**
+8. **Thin core, rich edges**
    Put optional chat, knowledge, and special surfaces into plugins/extensions rather than bloating the control plane.

doc/PUBLISHING.md

@@ -115,6 +115,38 @@ If the first real publish returns npm `E404`, check npm-side prerequisites befor
 - The initial publish must include `--access public` for a public scoped package.
 - npm also requires either account 2FA for publishing or a granular token that is allowed to bypass 2FA.
 
+### Manual first publish for `@paperclipai/mcp-server`
+
+If you need to publish only the MCP server package once by hand, use:
+
+- `@paperclipai/mcp-server`
+
+Recommended flow from the repo root:
+
+```bash
+# optional sanity check: this 404s until the first publish exists
+npm view @paperclipai/mcp-server version
+
+# make sure the build output is fresh
+pnpm --filter @paperclipai/mcp-server build
+
+# confirm your local npm auth before the real publish
+npm whoami
+
+# safe preview of the exact publish payload
+cd packages/mcp-server
+pnpm publish --dry-run --no-git-checks --access public
+
+# real publish
+pnpm publish --no-git-checks --access public
+```
+
+Notes:
+
+- Publish from `packages/mcp-server/`, not the repo root.
+- If `npm view @paperclipai/mcp-server version` already returns the same version that is in [`packages/mcp-server/package.json`](../packages/mcp-server/package.json), do not republish. Bump the version or use the normal repo-wide release flow in [`scripts/release.sh`](../scripts/release.sh).
+- The same npm-side prerequisites apply as above: valid npm auth, permission to publish to the `@paperclipai` scope, `--access public`, and the required publish auth/2FA policy.
+
 ## Version formats
 
 Paperclip uses calendar versions:
@@ -143,13 +175,6 @@ This keeps the default install path unchanged while allowing explicit installs w
 npx paperclipai@canary onboard
 ```
 
-The release script now verifies two things after a canary publish:
-
-- the `canary` dist-tag resolves to the version that was just published
-- every published internal `@paperclipai/*` dependency referenced by that manifest exists on npm
-
-It also treats `latest -> canary` as a failure by default, because npm metadata can otherwise leave the default install path pointing at an unreleased canary dependency graph. Only pass `./scripts/release.sh canary --allow-canary-latest` when that `latest` behavior is explicitly intended.
-
 ### Stable
 
 Stable publishes use the npm dist-tag `latest`.
@@ -176,58 +201,6 @@ That means:
 
 See [doc/RELEASE-AUTOMATION-SETUP.md](RELEASE-AUTOMATION-SETUP.md) for the GitHub/npm setup steps.
 
-## Release enrollment for new public packages
-
-Paperclip does not auto-publish every non-private workspace package anymore.
-CI publishing is controlled by [`scripts/release-package-manifest.json`](../scripts/release-package-manifest.json).
-
-When you add a new public package:
-
-1. add it to the manifest and decide whether CI should publish it immediately
-2. if CI should publish it, bootstrap the package on npm before merge
-3. if CI should not publish it yet, keep `"publishFromCi": false`
-4. only enable `"publishFromCi": true` after npm trusted publishing is configured for that package
-
-PR CI now checks changed release-enabled package manifests against npm. That catches a missing first-publish bootstrap before the change reaches `master`.
-
-### One-time bootstrap sequence for a new package
-
-The first publish of a brand-new package still needs one human maintainer with npm write access.
-After that, trusted publishing can take over.
-
-Example for `@paperclipai/adapter-acpx-local` from the repo root:
-
-```bash
-# safe preview
-pnpm run release:bootstrap-package -- @paperclipai/adapter-acpx-local
-
-# one-time first publish from an authenticated maintainer machine
-pnpm run release:bootstrap-package -- @paperclipai/adapter-acpx-local --publish --otp 123456
-```
-
-The helper script:
-
-- checks that the package does not already exist on npm
-- builds the target package unless `--skip-build` is passed
-- runs `npm pack --dry-run` in the package directory
-- only runs the real `npm publish --access public` when `--publish --otp <code>` is provided
-
-For the real `--publish` step, the maintainer machine must already be authenticated to npm.
-If `npm whoami` returns `401`, first run `npm logout --registry=https://registry.npmjs.org/` to clear any stale local auth, then run `npm login` or `npm adduser` locally as an npm org member, and finally rerun the helper.
-That local human auth is fine for the one-time bootstrap publish; we just do not want the same auth model inside CI.
-The helper now requires `--otp <code>` up front for `--publish`, so it fails before the real publish attempt if the one-time password is missing.
-
-After that first publish succeeds:
-
-1. open `https://www.npmjs.com/package/@paperclipai/adapter-acpx-local`
-2. go to `Settings` → `Trusted publishing`
-3. add repository `paperclipai/paperclip`
-4. set workflow filename to `release.yml`
-5. optionally go to `Settings` → `Publishing access` and enable `Require two-factor authentication and disallow tokens`
-6. keep `publishFromCi: true` in [`scripts/release-package-manifest.json`](../scripts/release-package-manifest.json)
-
-Once those steps are done, future canary and stable publishes for that package are automated through GitHub OIDC. The manual step is only the first package creation on npm.
-
 ## Rollback model
 
 Rollback does not unpublish anything.

doc/RELEASE-AUTOMATION-SETUP.md

@@ -67,27 +67,6 @@ Why:
 - the single `release.yml` workflow handles both canary and stable publishing
 - GitHub environments `npm-canary` and `npm-stable` still enforce different approval rules on the GitHub side
 
-### 2.2.1. Newly added public packages need a bootstrap phase
-
-Trusted publishing is configured on the npm package itself, not at the repo scope.
-That means a brand-new public package must not be auto-enrolled into CI publishing until its npm package exists and its trusted publisher has been configured.
-
-Repo policy:
-
-1. add every non-private package to [`scripts/release-package-manifest.json`](../scripts/release-package-manifest.json)
-2. set `"publishFromCi": true` only when CI is expected to publish that package
-3. if the package is not ready for CI publishing yet, keep `"publishFromCi": false`
-4. complete the package bootstrap before merging any PR that changes a release-enabled new package
-
-Bootstrap sequence for a new package:
-
-1. publish the package once from a trusted maintainer machine using normal npm auth
-2. open that package on npm and add the `paperclipai/paperclip` trusted publisher for `.github/workflows/release.yml`
-3. rerun or dry-run the release flow as needed to confirm CI publishing now works
-4. only then enable `"publishFromCi": true`
-
-PR CI enforces this by checking changed release-enabled package manifests against npm. That keeps `master` canary publishing healthy while preserving the no-long-lived-token model for normal CI releases.
-
 ### 2.3. Verify trusted publishing before removing old auth
 
 After the workflows are live:

doc/RELEASING.md

@@ -63,8 +63,6 @@ It:
 - verifies the pushed commit
 - computes the canary version for the current UTC date
 - publishes under npm dist-tag `canary`
-- verifies that `canary` resolves to the just-published version and that published internal dependencies exist on npm
-- fails by default if npm leaves `latest` pointing at a canary; use `--allow-canary-latest` only when that state is intentional
 - creates a git tag `canary/vYYYY.MDD.P-canary.N`
 
 Users install canaries with:

doc/SECRETS-AWS-PROVIDER.md

@@ -1,368 +0,0 @@
-# AWS Secrets Manager Provider
-
-Operational contract for the hosted `aws_secrets_manager` secret provider used by Paperclip Cloud.
-
-## Scope
-
-- Hosted provider for Paperclip-managed secrets when Paperclip Cloud runs on AWS.
-- Source of truth for secret values is AWS Secrets Manager, not Postgres.
-- Paperclip stores only metadata needed for ownership, bindings, version selection, audit, and runtime resolution.
-- AWS provider bootstrap credentials are deployment/runtime credentials, not Paperclip-managed company secrets.
-- Remote import for existing AWS secrets is metadata-only. Preview/import uses
-  AWS inventory metadata and creates Paperclip external references; it does not
-  copy plaintext into Paperclip.
-- Per-company AWS provider vaults (named instances of `aws_secrets_manager`
-  with their own region, namespace, prefix, KMS key id, and tags) are managed
-  in the board UI under `Company Settings → Secrets → Provider vaults`. See
-  [Provider Vaults](../docs/deploy/secrets.md#provider-vaults) for the operator
-  model and [Provider Vaults API](../docs/api/secrets.md#provider-vaults) for
-  the routes. The bootstrap trust model in this document still applies — vault
-  config carries non-sensitive routing metadata only, never AWS credentials.
-
-## Bootstrap Trust Model
-
-The AWS provider has a chicken-and-egg boundary: Paperclip cannot use
-`company_secrets` to unlock the AWS provider that stores those secrets. The
-initial AWS trust must exist before the Paperclip server starts.
-
-Allowed bootstrap locations:
-
-- Infrastructure IAM or workload identity attached to the Paperclip server
-  runtime.
-- Process environment or orchestrator secret store used to start the Paperclip
-  server.
-- Local AWS SDK sources such as `AWS_PROFILE`, AWS SSO/shared config, web
-  identity, container metadata, or instance metadata.
-- Short-lived shell credentials for local development only.
-
-Do not ask operators to paste AWS root credentials or long-lived IAM user access
-keys into the Paperclip board UI. Do not store those bootstrap keys in
-`company_secrets`.
-
-## Paperclip Cloud Bootstrap
-
-Paperclip Cloud must provision the AWS backing resources before any board user
-can create AWS-backed company secrets:
-
-1. Create or select the deployment KMS key.
-2. Create the Paperclip server runtime role for the deployment.
-3. Attach a minimum IAM policy scoped to the deployment Secrets Manager prefix
-   and the configured KMS key.
-4. Configure the server runtime with the non-secret provider environment
-   variables below.
-5. Run `paperclipai doctor` or the provider health endpoint from the deployed
-   runtime and confirm that the provider reports the expected region, prefix,
-   deployment id, KMS setting, and AWS SDK credential source.
-
-Once this is in place, the board UI can create Paperclip-managed AWS secrets and
-Paperclip will write them under the deployment/company namespace.
-
-## Self-Hosted And Local Bootstrap
-
-Self-hosted AWS deployments should use the AWS SDK default credential provider
-chain. Preferred sources are role-based:
-
-- EC2 instance profile.
-- ECS task role.
-- EKS IRSA or another OIDC web identity role.
-- AWS SSO/shared config via `AWS_PROFILE`.
-
-Local development can use:
-
-```sh
-aws sso login --profile paperclip-dev
-AWS_PROFILE=paperclip-dev \
-PAPERCLIP_SECRETS_PROVIDER=aws_secrets_manager \
-PAPERCLIP_SECRETS_AWS_REGION=us-east-1 \
-PAPERCLIP_SECRETS_AWS_DEPLOYMENT_ID=dev-local \
-PAPERCLIP_SECRETS_AWS_KMS_KEY_ID=arn:aws:kms:us-east-1:123456789012:key/abcd-... \
-pnpm dev
-```
-
-Temporary `AWS_ACCESS_KEY_ID`/`AWS_SECRET_ACCESS_KEY` environment credentials
-are acceptable only as a local break-glass or short-lived test source. They
-should not be written to Paperclip config, committed to `.env` files, stored in
-`company_secrets`, or used as the default Paperclip Cloud bootstrap path.
-
-## Deployment Config
-
-Required environment variables:
-
-```sh
-PAPERCLIP_SECRETS_PROVIDER=aws_secrets_manager
-PAPERCLIP_SECRETS_AWS_REGION=us-east-1
-PAPERCLIP_SECRETS_AWS_DEPLOYMENT_ID=prod-us-1
-PAPERCLIP_SECRETS_AWS_KMS_KEY_ID=arn:aws:kms:us-east-1:123456789012:key/abcd-...
-```
-
-Optional environment variables:
-
-```sh
-PAPERCLIP_SECRETS_AWS_PREFIX=paperclip
-PAPERCLIP_SECRETS_AWS_ENVIRONMENT=production
-PAPERCLIP_SECRETS_AWS_PROVIDER_OWNER=paperclip
-PAPERCLIP_SECRETS_AWS_ENDPOINT=
-PAPERCLIP_SECRETS_AWS_DELETE_RECOVERY_DAYS=30
-```
-
-Naming convention for Paperclip-managed secrets:
-
-```text
-paperclip/{deploymentId}/{companyId}/{secretKey}
-```
-
-Tag set for Paperclip-managed secrets:
-
-- `paperclip:managed-by=paperclip`
-- `paperclip:provider-owner=<owner tag>`
-- `paperclip:deployment-id=<deployment id>`
-- `paperclip:company-id=<company id>`
-- `paperclip:secret-key=<secret key>`
-- `paperclip:environment=<environment tag>`
-
-## IAM And KMS Assumptions
-
-Launch posture:
-
-- One Paperclip app role per deployment.
-- One deployment-scoped KMS key per deployment at launch.
-- Future per-company KMS keys remain compatible because Paperclip stores provider refs and version metadata separately from values.
-
-Minimum IAM boundary:
-
-- Allow `secretsmanager:CreateSecret`, `PutSecretValue`, `GetSecretValue`, and `DeleteSecret`.
-- Scope resources to the deployment prefix:
-
-```text
-arn:aws:secretsmanager:<region>:<account-id>:secret:paperclip/<deployment-id>/*
-```
-
-- Allow `kms:Encrypt`, `kms:Decrypt`, `kms:GenerateDataKey`, and `kms:DescribeKey` for the configured deployment CMK.
-- Deny wildcard access outside the deployment prefix.
-- Prefer workload identity / role-based auth. Do not store AWS credentials inline in Paperclip config.
-
-Example minimum policy shape:
-
-```json
-{
-  "Version": "2012-10-17",
-  "Statement": [
-    {
-      "Sid": "PaperclipDeploymentSecrets",
-      "Effect": "Allow",
-      "Action": [
-        "secretsmanager:CreateSecret",
-        "secretsmanager:PutSecretValue",
-        "secretsmanager:GetSecretValue",
-        "secretsmanager:DeleteSecret"
-      ],
-      "Resource": "arn:aws:secretsmanager:<region>:<account-id>:secret:paperclip/<deployment-id>/*"
-    },
-    {
-      "Sid": "PaperclipDeploymentKms",
-      "Effect": "Allow",
-      "Action": [
-        "kms:Encrypt",
-        "kms:Decrypt",
-        "kms:GenerateDataKey",
-        "kms:DescribeKey"
-      ],
-      "Resource": "arn:aws:kms:<region>:<account-id>:key/<key-id>"
-    }
-  ]
-}
-```
-
-Operational expectation:
-
-- Paperclip-managed secrets may be deleted only by Paperclip or an operator with equivalent break-glass access.
-- External references may resolve through Paperclip runtime, but Paperclip should not delete the external secret resource.
-
-## Remote Import Inventory IAM
-
-Remote import preview needs one additional AWS permission:
-
-```json
-{
-  "Sid": "PaperclipRemoteSecretInventory",
-  "Effect": "Allow",
-  "Action": "secretsmanager:ListSecrets",
-  "Resource": "*"
-}
-```
-
-This is intentionally separate from the managed create/rotate/delete policy.
-AWS treats `ListSecrets` as an account/Region inventory action; do not document
-secret ARNs, names, tags, or AWS request filters as an IAM boundary for it. Use
-`Resource: "*"` and decide whether inventory exposure is acceptable for the AWS
-account and Region behind each provider vault.
-
-Remote import preview/import must not call:
-
-- `secretsmanager:GetSecretValue`
-- `secretsmanager:BatchGetSecretValue`
-- `kms:Decrypt`
-
-Those permissions are only needed later when a bound runtime resolves an
-imported external reference. For imported refs, scope read permissions to the
-operator-approved external prefixes that Paperclip is allowed to consume:
-
-```json
-{
-  "Sid": "PaperclipResolveImportedExternalReferences",
-  "Effect": "Allow",
-  "Action": "secretsmanager:GetSecretValue",
-  "Resource": [
-    "arn:aws:secretsmanager:<region>:<account-id>:secret:<approved-external-prefix>/*"
-  ]
-}
-```
-
-If selected external secrets use customer-managed KMS keys, also grant
-`kms:Decrypt` and `kms:DescribeKey` on those keys. Keep managed write/delete
-permissions scoped to `paperclip/<deployment-id>/*`; do not broaden them for
-remote import.
-
-Safe scoping guidance:
-
-- Prefer one Paperclip runtime role per environment/account.
-- Point provider vaults at the intended AWS account and Region instead of a
-  broad central admin role.
-- Enable `ListSecrets` only in accounts where inventory exposure is acceptable.
-- Keep preview/import board-only; agent API keys must not call these routes.
-- Treat AWS tag/name filters as search UX only, not permission enforcement.
-
-Paperclip also blocks importing refs under its own managed namespace as
-external references. Use the Paperclip-managed flow for
-`paperclip/{deploymentId}/{companyId}/{secretKey}` resources.
-
-## Existing AWS Secrets
-
-V1 keeps existing AWS Secrets Manager entries as **linked external references**, not adopted
-Paperclip-managed resources.
-
-Use the Paperclip-managed flow when Paperclip should create and rotate the value. The AWS
-secret name is derived from deployment and company scope:
-
-```text
-paperclip/{deploymentId}/{companyId}/{secretKey}
-```
-
-Use the external-reference flow when the secret already exists at an operator-owned path such
-as:
-
-```text
-/paperclip-bench/anthropic_api_key
-```
-
-In that mode Paperclip stores only the path or ARN, resolves it at runtime, and records
-redacted access events. Operators rotate the actual value in AWS. Update the Paperclip
-reference only when the AWS path, ARN, or pinned provider version changes.
-
-Paperclip does not currently offer an "adopt existing AWS secret" flow that takes over future
-`PutSecretValue` writes for an arbitrary existing secret. Adding that later requires explicit
-confirmation UX, scope validation, expected Paperclip tags, and security/cloud-ops review.
-
-## Data Custody
-
-- Paperclip stores `externalRef`, `providerVersionRef`, provider id, fingerprint hash, status, and binding metadata.
-- Paperclip does not store AWS secret plaintext in `company_secret_versions.material`.
-- Runtime resolution fetches the value from AWS only when a bound consumer needs it.
-
-## Rotation Runbook
-
-Manual Paperclip-managed rotation:
-
-1. Write the new value through the Paperclip secret rotate flow.
-2. Paperclip creates a new AWS secret version with `PutSecretValue`.
-3. Paperclip records the new `providerVersionRef` in `company_secret_versions`.
-4. Re-run or restart affected workloads that consume `latest`, or pin consumers to a specific Paperclip version before rollout when you need staged release safety.
-
-Guidance:
-
-- Prefer pinned Paperclip secret versions for risky rollouts.
-- Treat provider-native automatic rotation as a later enhancement; current V1 flow is explicit create-new-version plus controlled rollout.
-
-## Backup And Restore Runbook
-
-What must survive:
-
-- Paperclip database metadata for secret ownership, bindings, status, and provider version refs.
-- AWS Secrets Manager namespace under the configured deployment prefix.
-- The configured KMS key and its decrypt permissions.
-
-Restore checklist:
-
-1. Restore Paperclip database metadata.
-2. Confirm the same AWS Secrets Manager namespace still exists.
-3. Confirm the Paperclip runtime role can call `GetSecretValue` on the restored prefix.
-4. Confirm the role still has decrypt access to the CMK referenced by `PAPERCLIP_SECRETS_AWS_KMS_KEY_ID`.
-5. Run the live smoke below or a targeted runtime secret resolution test.
-
-## Provider Outage Runbook
-
-Symptoms:
-
-- Secret create/rotate/resolve operations fail with AWS provider errors.
-- Agent runs fail before adapter invocation on required secret resolution.
-- Remote import preview fails to list AWS inventory.
-
-Immediate actions:
-
-1. Confirm AWS regional health and Secrets Manager availability.
-2. Confirm the runtime role still has `GetSecretValue` and KMS decrypt permissions.
-3. Check for accidental prefix, region, deployment id, or KMS key config drift.
-4. Retry a single resolution after AWS service health is green.
-5. If outage persists, pause high-risk runs that require secret access rather than churning retries.
-
-Remote import-specific actions:
-
-- Missing list permission: add `secretsmanager:ListSecrets` with
-  `Resource: "*"` only when inventory import is approved for that vault's
-  AWS account and Region.
-- Throttling: narrow the search, wait briefly, and retry with backoff. Avoid
-  full-account enumeration.
-- Invalid or stale cursor: refresh the preview and discard the old
-  `NextToken`.
-- Large account: load pages intentionally, keep one in-flight preview request
-  per vault/search, and do not run background full-account crawls.
-- Runtime read failure after import: verify `GetSecretValue` and KMS decrypt
-  on the selected external secret. Visibility in `ListSecrets` does not prove
-  read permission.
-
-## Incident Response Runbook
-
-Potential incidents:
-
-- Cross-company access caused by IAM scoping drift.
-- KMS policy drift causing decrypt failures or over-broad access.
-- Suspected secret exposure in logs, transcripts, or downstream agent output.
-
-Response steps:
-
-1. Stop or pause affected Paperclip runs.
-2. Audit recent Paperclip secret access events for impacted secret ids and consumers.
-3. Audit AWS CloudTrail for `ListSecrets`, `GetSecretValue`,
-   `PutSecretValue`, and `DeleteSecret` calls on the relevant vault account,
-   Region, deployment prefix, and approved external prefixes.
-4. Rotate impacted secrets in AWS through Paperclip-managed versioning.
-5. Re-scope IAM and KMS policies before resuming normal traffic.
-6. If a value may have reached an agent transcript or external system, treat it as exposed and rotate immediately.
-
-## Optional Live Smoke
-
-This is safe to skip locally. Run it only against a dedicated AWS test namespace.
-
-Prerequisites:
-
-- AWS credentials or workload identity with the deployment-scoped IAM permissions above.
-- `PAPERCLIP_SECRETS_PROVIDER=aws_secrets_manager`
-- The required `PAPERCLIP_SECRETS_AWS_*` environment variables set.
-
-Suggested smoke:
-
-1. Create a test secret through the Paperclip board or API under a throwaway company.
-2. Confirm the resulting AWS secret name matches `paperclip/{deploymentId}/{companyId}/{secretKey}`.
-3. Rotate the secret once and confirm a new `providerVersionRef` appears in Paperclip metadata.
-4. Resolve the secret through a bound runtime path, not by adding a general-purpose reveal endpoint.
-5. Delete the throwaway secret and confirm AWS schedules deletion with the configured recovery window.

doc/SPEC-implementation.md

@@ -1,7 +1,7 @@
 # Paperclip V1 Implementation Spec
 
 Status: Implementation contract for first release (V1)
-Date: 2026-04-28
+Date: 2026-02-17
 Audience: Product, engineering, and agent-integration authors
 Source inputs: `GOAL.md`, `PRODUCT.md`, `SPEC.md`, `DATABASE.md`, current monorepo code
 
@@ -34,12 +34,11 @@ These decisions close open questions from `SPEC.md` for V1.
 | Company model | Company is first-order; all business entities are company-scoped |
 | Board | Single human board operator per deployment |
 | Org graph | Strict tree (`reports_to` nullable root); no multi-manager reporting |
-| Visibility | Company-scoped visibility: board + all in-company agents can see all work objects by default; public/private deployment flags affect external exposure only and do **not** imply project/issue privacy |
+| Visibility | Full visibility to board and all agents in same company |
 | Communication | Tasks + comments only (no separate chat system) |
 | Task ownership | Single assignee; atomic checkout required for `in_progress` transition |
-| Recovery | Liveness/watchdog recovery preserves explicit ownership: retry lost execution continuity where safe, otherwise open visible source-scoped recovery actions by default, use issue-backed recovery only for independent repair work, or require human escalation (see `doc/execution-semantics.md`) |
-| Agent adapters | Built-in `process`, `http`, local CLI/session adapters, and OpenClaw gateway support; external adapters can also be loaded through the adapter plugin flow |
-| Plugin framework | Local/self-hosted early plugin runtime is in scope; cloud marketplace and packaged public distribution remain out of scope |
+| Recovery | No automatic reassignment; work recovery stays manual/explicit |
+| Agent adapters | Built-in `process` and `http` adapters |
 | Auth | Mode-dependent human auth (`local_trusted` implicit board in current code; authenticated mode uses sessions), API keys for agents |
 | Budget period | Monthly UTC calendar window |
 | Budget enforcement | Soft alerts + hard limit auto-pause |
@@ -74,7 +73,7 @@ V1 implementation extends this baseline into a company-centric, governance-aware
 
 ## 5.2 Out of Scope (V1)
 
-- Cloud-grade plugin marketplace/distribution beyond the local/self-hosted plugin runtime
+- Plugin framework and third-party extension SDK
 - Revenue/expense accounting beyond model/token costs
 - Knowledge base subsystem
 - Public marketplace (ClipHub)
@@ -124,16 +123,6 @@ Human auth tables (`users`, `sessions`, and provider-specific auth artifacts) ar
 - `name` text not null
 - `description` text null
 - `status` enum: `active | paused | archived`
-- `pause_reason` text null
-- `paused_at` timestamptz null
-- `issue_prefix` text not null
-- `issue_counter` int not null
-- `budget_monthly_cents` int not null default 0
-- `spent_monthly_cents` int not null default 0
-- `attachment_max_bytes` int not null
-- `require_board_approval_for_new_agents` boolean not null default false
-- feedback sharing consent fields
-- branding fields such as `brand_color`
 
 Invariant: every business record belongs to exactly one company.
 
@@ -144,21 +133,15 @@ Invariant: every business record belongs to exactly one company.
 - `name` text not null
 - `role` text not null
 - `title` text null
-- `icon` text null
-- `status` enum: `active | paused | idle | running | error | pending_approval | terminated`
+- `status` enum: `active | paused | idle | running | error | terminated`
 - `reports_to` uuid fk `agents.id` null
 - `capabilities` text null
-- `adapter_type` text; built-ins include `process`, `http`, `claude_local`, `codex_local`, `gemini_local`, `opencode_local`, `pi_local`, `cursor`, and `openclaw_gateway`
+- `adapter_type` enum: `process | http`
 - `adapter_config` jsonb not null
-- `runtime_config` jsonb not null default `{}`; may include Paperclip runtime policy such as `modelProfiles.cheap.adapterConfig` for an optional low-cost model lane that does not change the primary adapter config
-- `default_environment_id` uuid fk `environments.id` null
 - `context_mode` enum: `thin | fat` default `thin`
 - `budget_monthly_cents` int not null default 0
 - `spent_monthly_cents` int not null default 0
-- pause fields: `pause_reason`, `paused_at`
-- `permissions` jsonb not null default `{}`
 - `last_heartbeat_at` timestamptz null
-- `metadata` jsonb null
 
 Invariants:
 
@@ -207,14 +190,11 @@ Invariant:
 
 - project env is merged into run environment for issues in that project and overrides conflicting agent env keys before Paperclip runtime-owned keys are injected
 
-Routine execution issues add a routine-scoped env overlay after project env and before Paperclip runtime-owned keys. Routine env uses the same secret-aware binding format, is stored on `routines.env`, is snapshotted in routine revisions, and resolves secret refs against the routine binding target so routine-owned secrets do not require direct bindings on the executing agent.
-
 ## 7.6 `issues` (core task entity)
 
 - `id` uuid pk
 - `company_id` uuid fk not null
 - `project_id` uuid fk `projects.id` null
-- `project_workspace_id` uuid fk `project_workspaces.id` null
 - `goal_id` uuid fk `goals.id` null
 - `parent_id` uuid fk `issues.id` null
 - `title` text not null
@@ -222,22 +202,13 @@ Routine execution issues add a routine-scoped env overlay after project env and
 - `status` enum: `backlog | todo | in_progress | in_review | done | blocked | cancelled`
 - `priority` enum: `critical | high | medium | low`
 - `assignee_agent_id` uuid fk `agents.id` null
-- `assignee_user_id` text null
-- checkout/execution locks: `checkout_run_id`, `execution_run_id`, `execution_agent_name_key`, `execution_locked_at`
 - `created_by_agent_id` uuid fk `agents.id` null
 - `created_by_user_id` uuid fk `users.id` null
-- identifier fields: `issue_number`, `identifier`
-- origin fields: `origin_kind`, `origin_id`, `origin_run_id`, `origin_fingerprint`
 - `request_depth` int not null default 0
 - `billing_code` text null
-- `assignee_adapter_overrides` jsonb null
-- `execution_policy` jsonb null
-- `execution_state` jsonb null
-- execution workspace fields: `execution_workspace_id`, `execution_workspace_preference`, `execution_workspace_settings`
 - `started_at` timestamptz null
 - `completed_at` timestamptz null
 - `cancelled_at` timestamptz null
-- `hidden_at` timestamptz null
 
 Invariants:
 
@@ -290,10 +261,10 @@ Invariant: each event must attach to agent and company; rollups are aggregation,
 
 - `id` uuid pk
 - `company_id` uuid fk not null
-- `type` enum: `hire_agent | approve_ceo_strategy | budget_override_required | request_board_approval`
+- `type` enum: `hire_agent | approve_ceo_strategy`
 - `requested_by_agent_id` uuid fk `agents.id` null
 - `requested_by_user_id` uuid fk `users.id` null
-- `status` enum: `pending | revision_requested | approved | rejected | cancelled`
+- `status` enum: `pending | approved | rejected | cancelled`
 - `payload` jsonb not null
 - `decision_note` text null
 - `decided_by_user_id` uuid fk `users.id` null
@@ -311,32 +282,7 @@ Invariant: each event must attach to agent and company; rollups are aggregation,
 - `details` jsonb null
 - `created_at` timestamptz not null default now()
 
-## 7.12 `project_memberships` + `agent_memberships`
-
-Per-user project/agent membership is personal visibility state for board users. It only controls whether a resource appears in the current user's sidebar; it must not grant or revoke access to all-pages, detail pages, selectors, assignment flows, search, or existing permissions.
-
-`project_memberships`:
-
-- `id` uuid pk
-- `company_id` uuid fk `companies.id` not null
-- `project_id` uuid fk `projects.id` not null
-- `user_id` text not null
-- `state` enum-like text: `joined | left`
-- `created_at` timestamptz not null default now()
-- `updated_at` timestamptz not null default now()
-- unique `(company_id, user_id, project_id)`
-
-`agent_memberships` mirrors the same shape with `agent_id` instead of `project_id` and unique `(company_id, user_id, agent_id)`.
-
-Invariants:
-
-- Missing membership rows mean `joined` for backward compatibility.
-- Mutations are board-user-only `/me` operations; agent API keys are rejected.
-- Viewer-role board users may update only their own membership rows through the narrow self-service helper.
-- Target project/agent ownership is checked against the path company before mutation.
-- Successful state changes write `resource_membership.joined` or `resource_membership.left` activity entries.
-
-## 7.13 `company_secrets` + `company_secret_versions`
+## 7.12 `company_secrets` + `company_secret_versions`
 
 - Secret values are not stored inline in `agents.adapter_config.env`.
 - Agent env entries should use secret refs for sensitive values.
@@ -350,7 +296,7 @@ Operational policy:
 - Activity and approval payloads must not persist raw sensitive values.
 - Config revisions may include redacted placeholders; such revisions are non-restorable for redacted fields.
 
-## 7.14 Required Indexes
+## 7.13 Required Indexes
 
 - `agents(company_id, status)`
 - `agents(company_id, reports_to)`
@@ -368,12 +314,8 @@ Operational policy:
 - `issue_attachments(company_id, issue_id)`
 - `company_secrets(company_id, name)` unique
 - `company_secret_versions(secret_id, version)` unique
-- `project_memberships(company_id, user_id)`
-- `project_memberships(company_id, user_id, project_id)` unique
-- `agent_memberships(company_id, user_id)`
-- `agent_memberships(company_id, user_id, agent_id)` unique
 
-## 7.15 `assets` + `issue_attachments`
+## 7.14 `assets` + `issue_attachments`
 
 - `assets` stores provider-backed object metadata (not inline bytes):
   - `id` uuid pk
@@ -407,10 +349,6 @@ Operational policy:
   - `created_by_user_id` uuid/text fk null
   - `updated_by_agent_id` uuid fk null
   - `updated_by_user_id` uuid/text fk null
-  - `locked_at` timestamptz null
-  - `locked_by_agent_id` uuid fk null
-  - `locked_by_user_id` uuid/text fk null
-  - Locked documents are immutable until unlocked. Board operators can lock/unlock; agent writes to a locked key create a new issue document with a derived key instead of overwriting the locked document.
 - `document_revisions` stores append-only history:
   - `id` uuid pk
   - `company_id` uuid fk not null
@@ -425,15 +363,6 @@ Operational policy:
   - `document_id` uuid fk not null
   - `key` text not null (`plan`, `design`, `notes`, etc.)
 
-## 7.16 Current Implementation Addenda
-
-The current implementation includes additional V1-control-plane tables beyond the original February snapshot:
-
-- Issue structure and review: `issue_relations` for blockers, `labels`/`issue_labels`, `issue_thread_interactions`, `issue_approvals`, `issue_execution_decisions`, `issue_work_products`, `issue_inbox_archives`, `issue_read_states`, and issue reference mention indexes.
-- Execution and workspace control: `execution_workspaces`, `project_workspaces`, `workspace_runtime_services`, `workspace_operations`, `environments`, `environment_leases`, `agent_task_sessions`, `agent_runtime_state`, `agent_wakeup_requests`, heartbeat events, and watchdog decision tables.
-- Plugins and routines: `plugins`, plugin config/state/entities/jobs/logs/webhooks, plugin database namespaces/migrations, plugin company settings, `routines`, `routine_revisions`, `routine_triggers`, and `routine_runs`.
-- Access and operations: company memberships, instance roles, principal permission grants, invites, join requests, board API keys, CLI auth challenges, budget policies/incidents, feedback exports/votes, company skills, sidebar preferences, and company logos.
-
 ## 8. State Machines
 
 ## 8.1 Agent Status
@@ -466,16 +395,6 @@ Side effects:
 - entering `done` sets `completed_at`
 - entering `cancelled` sets `cancelled_at`
 
-V1 non-terminal liveness rule:
-
-- agent-owned `todo`, `in_progress`, `in_review`, and `blocked` issues must have a live execution path, an explicit waiting path, or an explicit recovery path
-- `in_review` is healthy only when a typed execution participant, pending issue-thread interaction or approval, user owner, active run, queued wake, or explicit recovery action owns the next action
-- a blocked chain is covered only when each unresolved leaf issue is live or explicitly waiting
-- when Paperclip cannot safely infer the next action, it surfaces the problem through visible blocked/recovery work instead of silently completing or reassigning work
-- explicit recovery actions are the liveness primitive; source-scoped actions are the default form, issue-backed recovery is a fallback for independent repair work or safety boundaries, and comments alone are evidence rather than a healthy liveness path
-
-Detailed ownership, execution, blocker, active-run watchdog, crash-recovery, and non-terminal liveness semantics are documented in `doc/execution-semantics.md`.
-
 ## 8.3 Approval Status
 
 - `pending -> approved | rejected | cancelled`
@@ -516,59 +435,6 @@ Detailed ownership, execution, blocker, active-run watchdog, crash-recovery, and
 | Report cost | yes | yes |
 | Set company budget | yes | no |
 | Set subordinate budget | yes | yes (manager subtree only) |
-| Set work-object visibility (issue/project) | no | no (pro gate) |
-
-## 9.4 Permission Terminology and Default Visibility Rule
-
-Paperclip V1 keeps a company-scoped visibility model as the default because centralized authorization and scoped work-object controls are not yet a core V1 control surface.
-
-The approved term set is:
-
-- **Agent profile visibility**: identity-level facts needed for delegation and governance (name, role, capabilities, reporting lines).
-- **Agent config visibility**: adapter/runtime config metadata and secret-access policy.
-- **Assignment/invocation permission**: who may modify or execute a task.
-- **Work-object visibility**: who can read/write issues, comments, projects, and attachments.
-- **Tool/secret policy**: what tools and secret-backed credentials an agent can use and what appears in logs.
-- **Escalation authority**: where refusal/blocked decisions route (manager, then board).
-
-## 9.5 Core V1 Rule: what “private” means
-
-- A **private marker** on an agent profile (where represented) does **not** make company-visible work private.
-- Company-visible work objects (issues, comments, work products, costs, activity, project/task state) remain visible to the board and in-company agents by default.
-- Project/issue-level privacy, scoped assignment-only object visibility, and organization-wide custom ACLs are deferred to Pro/Enterprise controls.
-
-## 9.6 V1 vs Pro/Enterprise Controls (recommended target split)
-
-| Permission area | Free / V1 default | Pro / Enterprise |
-|---|---|---|
-| Company boundary | Hard boundary only (`company_id`) | Multi-company policy overlays (`membership`, `project`, and `task` scopes) |
-| Simple roles | Board + agent roles with existing approval/budget gates | Additional role aliases + scoped approver roles |
-| Profile visibility | Full profile visibility for coordination and audit | Optional profile redaction / selective sharing for external surfaces |
-| Config visibility | Board full read with redacted secret fields; agent config read/write constrained by own agent identity | Scoped config visibility controls and central policy enforcement |
-| Assignment/invocation | Assignment creates execution authority; board can reassign or force release | Delegation policies and scoped invokers with deny-listed tool classes |
-| Work-object visibility | All issues and projects in-company are visible to board and agents | Project/issue ACLs and reviewer-only channels |
-| Tool/secret policy | Secret refs, log redaction, and adapter-level command/webhook restrictions | Tool allowlists with centralized policy evaluation |
-| Escalation | Escalate from agent to manager to board; board approval/budget gates remain authoritative | Escalation routing and SLA windows |
-
-## 9.7 Recommended first-slice implementation order
-
-1. Lock route-level checks for existing company boundaries, actor extraction, and approval/budget gates.
-2. Treat profile privacy as external-facing signal only; do not use it to hide company-visible work objects.
-3. Enforce assignment/invocation coupling (`assignee`/`agent` checks, checkout semantics, invocation checks).
-4. Standardize read-path redaction for secrets and secret references, including logs and activity.
-5. Standardize escalation paths (`blocked` and refusal) so non-board agents hand off by manager/board with immutable audit.
-
-## 9.8 Scoped Task Assignment Grants
-
-`tasks:assign` remains the broad assignment permission. Existing unscoped grants preserve compatibility and allow the principal to assign any visible company task within normal company-boundary checks.
-
-`tasks:assign_scope` is the constrained assignment permission. Its `principal_permission_grants.scope` JSON must include at least one recognized constraint:
-
-- Project scope: `projectId`, `projectIds`, or `allow: ["project:<projectId>"]`.
-- Target-agent allowlist: `agentId`, `agentIds`, `assigneeAgentId`, `assigneeAgentIds`, `targetAgentId`, `targetAgentIds`, or `allow: ["agent:<agentId>"]`.
-- Managed-subtree scope: `managerAgentId`, `managerAgentIds`, `managedSubtreeAgentId`, `managedSubtreeAgentIds`, `subtreeAgentId`, `subtreeAgentIds`, `subtreeRootAgentId`, `subtreeRootAgentIds`, or `allow: ["subtree:<agentId>"]`.
-
-When multiple constraint families are present, assignment must satisfy all of them. Denials return `403` with a generic scope explanation and do not disclose details about hidden or unrelated resources.
 
 ## 10. API Contract (REST)
 
@@ -612,13 +478,10 @@ All endpoints are under `/api` and return JSON.
 - `GET /issues/:issueId/documents`
 - `GET /issues/:issueId/documents/:key`
 - `PUT /issues/:issueId/documents/:key`
-- `POST /issues/:issueId/documents/:key/lock`
-- `POST /issues/:issueId/documents/:key/unlock`
 - `GET /issues/:issueId/documents/:key/revisions`
 - `DELETE /issues/:issueId/documents/:key`
 - `POST /issues/:issueId/checkout`
 - `POST /issues/:issueId/release`
-- `POST /issues/:issueId/admin/force-release` (board-only lock recovery)
 - `POST /issues/:issueId/comments`
 - `GET /issues/:issueId/comments`
 - `POST /companies/:companyId/issues/:issueId/attachments` (multipart upload)
@@ -643,8 +506,6 @@ Server behavior:
 2. if updated row count is 0, return `409` with current owner/status
 3. successful checkout sets `assignee_agent_id`, `status = in_progress`, and `started_at`
 
-`POST /issues/:issueId/admin/force-release` is an operator recovery endpoint for stale harness locks. It requires board access to the issue company, clears checkout and execution run lock fields, and may clear the agent assignee when `clearAssignee=true` is passed. The route must write an `issue.admin_force_release` activity log entry containing the previous checkout and execution run IDs.
-
 ## 10.5 Projects
 
 - `GET /companies/:companyId/projects`
@@ -652,28 +513,14 @@ Server behavior:
 - `GET /projects/:projectId`
 - `PATCH /projects/:projectId`
 
-## 10.6 Current-user Resource Memberships
-
-- `GET /companies/:companyId/resource-memberships/me`
-- `PUT /companies/:companyId/resource-memberships/me/projects/:projectId`
-- `PUT /companies/:companyId/resource-memberships/me/agents/:agentId`
-
-Request payload:
-
-```json
-{ "state": "joined" }
-```
-
-Allowed states are `joined` and `left`. Endpoints require a concrete board user and active company membership, reject agent API keys, and only mutate the caller's own sidebar visibility state. Joining/leaving is idempotent; missing rows read as `joined`.
-
-## 10.7 Approvals
+## 10.6 Approvals
 
 - `GET /companies/:companyId/approvals?status=pending`
 - `POST /companies/:companyId/approvals`
 - `POST /approvals/:approvalId/approve`
 - `POST /approvals/:approvalId/reject`
 
-## 10.8 Cost and Budgets
+## 10.7 Cost and Budgets
 
 - `POST /companies/:companyId/cost-events`
 - `GET /companies/:companyId/costs/summary`
@@ -682,7 +529,7 @@ Allowed states are `joined` and `left`. Endpoints require a concrete board user
 - `PATCH /companies/:companyId/budgets`
 - `PATCH /agents/:agentId/budgets`
 
-## 10.9 Activity and Dashboard
+## 10.8 Activity and Dashboard
 
 - `GET /companies/:companyId/activity`
 - `GET /companies/:companyId/dashboard`
@@ -694,7 +541,7 @@ Dashboard payload must include:
 - month-to-date spend and budget utilization
 - pending approvals count
 
-## 10.10 Error Semantics
+## 10.9 Error Semantics
 
 - `400` validation error
 - `401` unauthenticated
@@ -704,17 +551,6 @@ Dashboard payload must include:
 - `422` semantic rule violation
 - `500` server error
 
-## 10.11 Current Implementation API Addenda
-
-The current app also exposes V1-supporting surfaces for:
-
-- issue thread interactions (`suggest_tasks`, `ask_user_questions`, `request_confirmation`)
-- issue approvals, issue references/search, labels, read state, inbox/archive state, and work products
-- execution workspaces, project workspaces, workspace runtime services, and workspace operations
-- routines and scheduled/API/webhook triggers
-- plugin installation, configuration, state, jobs, logs, webhooks, and plugin database namespace migration
-- company import/export preview/apply, feedback export/vote routes, instance backup/config routes, invites, join requests, memberships, and permission grants
-
 ## 11. Heartbeat and Adapter Contract
 
 ## 11.1 Adapter Interface
@@ -775,19 +611,13 @@ Behavior:
 - `thin`: send IDs and pointers only; agent fetches context via API
 - `fat`: include current assignments, goal summary, budget snapshot, and recent comments
 
-## 11.5 Recovery Model Profiles
-
-The optional `modelProfiles.cheap` lane is not a retry worker lane. Paperclip may request the cheap profile only for status-only recovery coordination, and those wakes must include guard context that prevents deliverable work and document/plan updates (`allowDeliverableWork: false`, `allowDocumentUpdates: false`, `resumeRequiresNormalModel: true`).
-
-Failed source-work retries, process-loss retries, transient/scheduled retries, max-turn continuations, source-assignee continuations, and downstream source-work child/requeue/resume contexts must use the normal/original model lane. If cheap recovery repairs liveness while actual work remains, the next live continuation path must be a separate normal-model worker run with cheap hints scrubbed.
-
-## 11.6 Scheduler Rules
+## 11.5 Scheduler Rules
 
 Per-agent schedule fields in `adapter_config`:
 
 - `enabled` boolean
 - `intervalSec` integer (minimum 30)
-- `maxConcurrentRuns` integer; new agents default to `20`; scheduler clamps configured values to `1..50`
+- `maxConcurrentRuns` fixed at `1` for V1
 
 Scheduler must skip invocation when:
 
@@ -896,14 +726,13 @@ Required UX behaviors:
 
 - Node 20+
 - `DATABASE_URL` optional
-- if unset, auto-use embedded PostgreSQL under `~/.paperclip/instances/default/db`
+- if unset, auto-use PGlite and push schema
 
 ## 15.2 Migrations
 
 - Drizzle migrations are source of truth
-- local/dev startup applies pending migrations automatically where supported
-- `pnpm db:migrate` applies pending migrations manually
 - no destructive migration in-place for V1 upgrade path
+- provide migration script from existing minimal tables to company-scoped schema
 
 ## 15.3 Logging and Audit
 
@@ -958,8 +787,6 @@ A release candidate is blocked unless these pass:
 
 ## 18. Delivery Plan
 
-Current implementation note: the milestones below describe the original V1 sequencing. Several systems originally framed as future work have since shipped or advanced materially, including issue documents/interactions, blockers, routines, execution workspaces, import/export portability, authenticated deployment modes, multi-user basics, and the local/self-hosted plugin runtime.
-
 ## Milestone 1: Company Core and Auth
 
 - add `companies` and company scoping to existing entities
@@ -1012,7 +839,7 @@ V1 is complete only when all criteria are true:
 
 ## 20. Post-V1 Backlog (Explicitly Deferred)
 
-- cloud-grade plugin marketplace/distribution
+- plugin architecture
 - richer workflow-state customization per team
 - milestones/labels/dependency graph depth beyond V1 minimum
 - realtime transport optimization (SSE/WebSockets)

doc/SPEC.md

@@ -141,8 +141,6 @@ Hierarchical reporting structure. CEO at top, reports cascade down.
 
 **Full visibility across the org.** Every agent can see the entire org chart, all tasks, all agents. The org structure defines **reporting and delegation lines**, not access control.
 
-Visibility settings on an agent profile (where supported) do not alter company-level visibility for tasks, projects, issues, comments, costs, or activity. Those work-object privacy controls are not a V1 feature until centralized scoped authorization is in place.
-
 Each agent publishes a short description of their responsibilities and capabilities — almost like skills ("when I'm relevant"). This lets other agents discover who can help with what.
 
 ### Cross-Team Work

doc/execution-semantics.md

@@ -1,541 +0,0 @@
-# Execution Semantics
-
-Status: Current implementation guide
-Date: 2026-05-23
-Audience: Product and engineering
-
-This document explains how Paperclip interprets issue assignment, issue status, execution runs, wakeups, parent/sub-issue structure, and blocker relationships.
-
-`doc/SPEC-implementation.md` remains the V1 contract. This document is the detailed execution model behind that contract.
-
-## 1. Core Model
-
-Paperclip separates four concepts that are easy to blur together:
-
-1. structure: parent/sub-issue relationships
-2. dependency: blocker relationships
-3. ownership: who is responsible for the issue now
-4. execution: whether the control plane currently has a live path to move the issue forward
-
-The system works best when those are kept separate.
-
-## 2. Assignee Semantics
-
-An issue has at most one assignee.
-
-- `assigneeAgentId` means the issue is owned by an agent
-- `assigneeUserId` means the issue is owned by a human board user
-- both cannot be set at the same time
-
-This is a hard invariant. Paperclip is single-assignee by design.
-
-## 3. Status Semantics
-
-Paperclip issue statuses are not just UI labels. They imply different expectations about ownership and execution.
-
-### `backlog`
-
-The issue is not ready for active work.
-
-- no execution expectation
-- no pickup expectation
-- safe resting state for future work
-
-### `todo`
-
-The issue is actionable but not actively claimed.
-
-- it may be assigned or unassigned
-- no checkout/execution lock is required yet
-- for agent-assigned work, Paperclip may still need a wake path to ensure the assignee actually sees it
-
-### `in_progress`
-
-The issue is actively owned work.
-
-- requires an assignee
-- for agent-owned issues, this is a strict execution-backed state
-- for user-owned issues, this is a human ownership state and is not backed by heartbeat execution
-
-For agent-owned issues, `in_progress` should not be allowed to become a silent dead state.
-
-### `blocked`
-
-The issue cannot proceed until something external changes.
-
-This is the right state for:
-
-- waiting on another issue
-- waiting on a human decision
-- waiting on an external dependency or system when Paperclip does not own a scheduled re-check
-- work that automatic recovery could not safely continue
-
-### `in_review`
-
-Execution work is paused because the next move belongs to a reviewer or approver, not the current executor.
-
-An external review service can also be a valid review path when the issue keeps an agent assignee and has an active one-shot monitor that will wake that assignee to check the service later.
-
-### `done`
-
-The work is complete and terminal.
-
-### `cancelled`
-
-The work will not continue and is terminal.
-
-## 4. Agent-Owned vs User-Owned Execution
-
-The execution model differs depending on assignee type.
-
-### Agent-owned issues
-
-Agent-owned issues are part of the control plane's execution loop.
-
-- Paperclip can wake the assignee
-- Paperclip can track runs linked to the issue
-- Paperclip can recover some lost execution state after crashes/restarts
-
-### User-owned issues
-
-User-owned issues are not executed by the heartbeat scheduler.
-
-- Paperclip can track the ownership and status
-- Paperclip cannot rely on heartbeat/run semantics to keep them moving
-- stranded-work reconciliation does not apply to them
-
-This is why `in_progress` can be strict for agents without forcing the same runtime rules onto human-held work.
-
-## 5. Checkout and Active Execution
-
-Checkout is the bridge from issue ownership to active agent execution.
-
-- checkout is required to move an issue into agent-owned `in_progress`
-- `checkoutRunId` represents issue-ownership lock for the current agent run
-- `executionRunId` represents the currently active execution path for the issue
-
-These are related but not identical:
-
-- `checkoutRunId` answers who currently owns execution rights for the issue
-- `executionRunId` answers which run is actually live right now
-
-Paperclip already clears stale execution locks and can adopt some stale checkout locks when the original run is gone.
-
-## 6. Parent/Sub-Issue vs Blockers
-
-Paperclip uses two different relationships for different jobs.
-
-### Parent/Sub-Issue (`parentId`)
-
-This is structural.
-
-Use it for:
-
-- work breakdown
-- rollup context
-- explaining why a child issue exists
-- waking the parent assignee when all direct children become terminal
-
-Do not treat `parentId` as execution dependency by itself.
-
-### Blockers (`blockedByIssueIds`)
-
-This is dependency semantics.
-
-Use it for:
-
-- \"this issue cannot continue until that issue changes state\"
-- explicit waiting relationships
-- automatic wakeups when all blockers resolve
-
-Blocked issues should stay idle while blockers remain unresolved. Paperclip should not create a queued heartbeat run for that issue until the final blocker is done and the `issue_blockers_resolved` wake can start real work.
-
-If a parent is truly waiting on a child, model that with blockers. Do not rely on the parent/child relationship alone.
-
-## 7. Accepted-Plan Decomposition
-
-An accepted plan confirmation is permission to decompose one specific accepted plan revision into child issues.
-
-This complements the existing accepted-plan continuation rule: once a plan is accepted, the source issue may create child implementation issues, but it must not start implementation work on the source issue itself during that continuation.
-
-Paperclip must treat accepted-plan decomposition as an exact-once control-plane primitive, not as a free-floating wake that any later run may interpret again.
-
-### Exact-once fingerprint
-
-The canonical decomposition fingerprint is:
-
-- `(sourceIssueId, acceptedPlanRevisionId)`
-
-Where:
-
-- `sourceIssueId` is the issue whose `plan` document revision was accepted
-- `acceptedPlanRevisionId` is the accepted `plan` document revision
-
-This is the product contract because the accepted revision is the thing being authorized for decomposition. Re-accepting, re-waking, or re-reading the same accepted revision must not authorize a second child tree. A later accepted revision on the same source issue is a new fingerprint and may produce a different decomposition result.
-
-An implementation may also store the accepted interaction id, acceptance run id, or other evidence, but those values must collapse onto the same uniqueness guarantee. They must not allow a second decomposition claim for the same `(sourceIssueId, acceptedPlanRevisionId)` pair.
-
-### Durable claim and durable result
-
-Before creating child issues, the first decomposition attempt must create or reuse a durable record for the fingerprint.
-
-That durable record must be able to answer, without reconstructing the thread from comments or transcripts:
-
-- whether decomposition for the fingerprint is `in_flight` or `completed`
-- which run or owner currently holds the in-flight claim
-- which child issues, if any, have already been created under that fingerprint
-- which final child issue ids belong to the completed result
-
-Paperclip does not need to mandate a specific storage shape in this document. The record may live in a dedicated table, source-issue execution state, interaction metadata, or another durable product surface. What matters is the contract:
-
-- the claim is durable before fan-out starts
-- partial progress is durable while fan-out is underway
-- the completed child result set is durable after fan-out finishes
-
-If a run creates some children and then dies, retries must continue from the same fingerprint and reuse the already-recorded partial result. They must not restart decomposition as if nothing happened.
-
-### Parent live path while decomposition is in flight
-
-While decomposition for an accepted fingerprint is incomplete, the source issue must expose an explicit live path for that same fingerprint.
-
-The accepted interaction by itself is only evidence that the plan was approved. It is not a sufficient live path once decomposition begins. The source issue must make it clear what moves the fingerprint forward next, such as:
-
-- the active decomposition run
-- a queued continuation wake for the same assignee
-- a monitor or explicit recovery action tied to the same decomposition claim
-- a blocked state that names the real blocker for finishing that claimed decomposition
-
-If the live run disappears, Paperclip must repair, resume, or visibly block the existing claim. It must not leave the source issue in a state where a second run can interpret the same acceptance as fresh permission to create sibling issues again.
-
-### Concurrent and repeat attempts
-
-Every later run that encounters the same accepted-plan fingerprint must consult the durable claim/result before creating children.
-
-- If no claim exists, the run may atomically create the claim and become the decomposition owner.
-- If a claim exists and is `in_flight`, the later run must reuse that claim. It may resume the same decomposition if it is the valid continuation owner, or it may exit after observing that another run already owns the work.
-- If a claim exists and is `completed`, the later run must reuse the recorded child result and must not create new sibling issues.
-- If the prior attempt ended after partial child creation, the retry must continue under the same fingerprint and preserve the already-created child ids.
-
-Concurrent accepted-plan runs are therefore idempotent relative to the fingerprint. Creating multiple child trees for the same `(sourceIssueId, acceptedPlanRevisionId)` pair is a product bug.
-
-## 8. Non-Terminal Issue Liveness Contract
-
-For agent-owned, non-terminal issues, Paperclip should never leave work in a state where nobody is responsible for the next move and nothing will wake or surface it.
-
-This is a visibility contract, not an auto-completion contract. If Paperclip cannot safely infer the next action, it should surface the ambiguity with a blocked state, a visible notice, or an explicit recovery action. It must not silently mark work done from prose comments or guess that a dependency is complete.
-
-An issue is healthy when the product can answer "what moves this forward next?" without requiring a human to reconstruct intent from the whole thread. An issue is stalled when it is non-terminal but has no live execution path, no explicit waiting path, and no recovery path.
-
-The valid action-path primitives are:
-
-- an active run linked to the issue
-- a queued wake or continuation that can be delivered to the responsible agent
-- a typed execution-policy participant, such as `executionState.currentParticipant`
-- a pending issue-thread interaction or linked approval that is waiting for a specific responder
-- a one-shot issue monitor (`executionPolicy.monitor.nextCheckAt`) that will wake the assignee for a future check
-- a human owner via `assigneeUserId`
-- a first-class blocker chain whose unresolved leaf issues are themselves healthy
-- an open explicit recovery action that names the owner and action needed to restore liveness
-
-### Explicit recovery actions
-
-An explicit recovery action is a typed liveness repair path for a source issue. It is the recovery primitive; the action can be rendered directly on the source issue or backed by a separate recovery issue when the repair needs its own work item.
-
-A valid recovery action must name:
-
-- the source issue and company
-- the recovery kind and idempotency fingerprint
-- the recovery owner, plus previous or return owner when ownership may temporarily shift
-- the cause, bounded evidence, and next action
-- the wake, monitor, timeout, retry, or escalation policy that will move the action forward
-- the resolution outcome when closed, such as restored, delegated, false positive, blocked, escalated, or cancelled
-
-A source-scoped recovery action is the default form. Use it when the next safe move is to repair the source issue's liveness directly: move the source issue back to `todo` so it can be retried, clarify disposition, re-establish a monitor, record a false positive, or delegate real follow-up work from the source issue.
-
-Use an issue-backed recovery action only when the recovery is genuinely independent work or when source-scoped handling would be unsafe or unclear. Examples include:
-
-- long or cross-agent repair work with its own assignee, subtasks, or blockers
-- real delegated follow-up that should block the source issue as a first-class dependency
-- active-run watchdog work that must observe a still-running source process without interfering with it
-- recovery that needs separate review, approval, security handling, or escalation ownership
-- cases where source issue ownership cannot be changed or restored safely
-
-A comment or system notice can be evidence for a recovery action, but it is not a recovery action by itself. Comment-only recovery is not a healthy liveness path because it does not define a typed owner, wake or monitor policy, retry bound, timeout, escalation path, or resolution outcome.
-
-#### Recovery action freshness
-
-Source-scoped recovery actions are snapshots of the source issue's liveness state at the time the action was opened. They must be revalidated after newer durable source activity, including source issue status changes, assignee changes, blocker changes, execution policy or monitor changes, document or work-product updates that define a valid waiting path, and structured resume or disposition updates.
-
-When newer source activity restores a valid live or waiting path, the recovery action is stale and should be folded through the explicit recovery lifecycle instead of being hidden or deleted. Folding means resolving or cancelling the recovery action with a resolution outcome and note that preserve the audit trail.
-
-Plain comments alone do not make a recovery action stale. A comment can provide evidence, but the recovery action should remain visible when the source issue is still stalled and the comment does not create a valid action-path primitive such as a wake, monitor, interaction, approval, blocker, human owner, execution participant, terminal disposition, or delegated follow-up.
-
-### Agent-assigned `todo`
-
-This is dispatch state: ready to start, not yet actively claimed.
-
-A healthy dispatch state means at least one of these is true:
-
-- the issue already has a queued wake path
-- the issue is intentionally resting in `todo` after a completed agent heartbeat, with no interrupted dispatch evidence
-- the issue has been explicitly surfaced as stranded through a visible blocked/recovery path
-
-An assigned `todo` issue is stalled when dispatch was interrupted, no wake remains queued or running, and no recovery path has been opened.
-
-### Agent-assigned `backlog`
-
-This is parked state, not dispatch state.
-
-Assigning an issue normally implies executable intent. When create APIs receive an assignee and no explicit status, Paperclip defaults the issue to `todo` so the assignee has a wake path instead of silently inheriting the unassigned `backlog` default.
-
-An explicit assigned `backlog` issue remains valid when the creator is deliberately parking the work. It must not wake the assignee just because it has an assignee. Paperclip should make that choice visible in activity and UI so operators can distinguish intentional parking from a missed handoff.
-
-An assigned `backlog` issue becomes a liveness problem when another issue is blocked on it and there is no explicit waiting path such as a human owner, active run, queued wake, pending interaction or approval, monitor, or open recovery action. In that case the blocked parent should surface "blocked by parked work" rather than treating the dependency chain as healthy.
-
-### Agent-assigned `in_progress`
-
-This is active-work state.
-
-A healthy active-work state means at least one of these is true:
-
-- there is an active run for the issue
-- there is already a queued continuation wake
-- there is an active one-shot monitor that will wake the assignee for a future check
-- there is an open explicit recovery action for the lost execution path
-
-An agent-owned `in_progress` issue is stalled when it has no active run, no queued continuation, and no explicit recovery surface. A still-running but silent process is not automatically stalled; it is handled by the active-run watchdog contract.
-
-### `in_review`
-
-This is review/approval state: execution is paused because the next move belongs to a reviewer, approver, board user, or recovery owner.
-
-A healthy `in_review` issue has at least one valid action path:
-
-- a typed execution-policy participant who can approve or request changes
-- a pending issue-thread interaction or linked approval waiting for a named responder
-- a human owner via `assigneeUserId`
-- an active run or queued wake that is expected to process the review state
-- an active one-shot monitor for an external service or async review loop that the assignee owns
-- an open explicit recovery action for an ambiguous review handoff
-
-Agent-assigned `in_review` with no typed participant is only healthy when one of the other paths exists. Assignment to the same agent that produced the handoff is not, by itself, a review path.
-
-An `in_review` issue is stalled when it has no typed participant, no pending interaction or approval, no user owner, no active monitor, no active run, no queued wake, and no explicit recovery action. Paperclip should surface that state as recovery work rather than silently completing the issue or leaving blocker chains parked indefinitely.
-
-### Issue monitors
-
-An issue monitor is a one-shot deferred action path for agent-owned issues in `in_progress` or `in_review`.
-
-Use a monitor when the current assignee owns a future check against an async system or external service. Examples include Greptile review loops, GitHub checks, Vercel deployments, or provider jobs where the agent should come back later and decide what happens next.
-
-Monitor policy lives under `executionPolicy.monitor` and includes:
-
-- `nextCheckAt`: when Paperclip should wake the assignee
-- `notes`: non-secret instructions for what the assignee should check
-- `serviceName`: optional non-secret external-service context
-- `externalRef`: optional external-service reference input; Paperclip treats it as secret-adjacent, redacts it before persistence/visibility, and omits it from activity and wake payloads
-- `timeoutAt`, `maxAttempts`, and `recoveryPolicy`: optional recovery hints for bounded waits
-
-Monitors are not recurring intervals. When a monitor fires, Paperclip clears the scheduled monitor and queues an `issue_monitor_due` wake for the assignee. If the external service is still pending, the assignee must explicitly re-arm the monitor with a new `nextCheckAt`. If the issue moves to `done`, `cancelled`, an invalid status, or a human/unassigned owner, the monitor is cleared.
-
-Because `serviceName` and `notes` remain visible in issue activity and wake context, operators should keep them short and non-secret. Put enough context for the assignee to know what to inspect, but do not include signed URLs, bearer tokens, customer secrets, tenant-private identifiers, or provider links with embedded credentials.
-
-Monitor bounds are enforced. Paperclip rejects attempts to re-arm a monitor whose `timeoutAt` or `maxAttempts` is already exhausted. When a scheduled monitor reaches an exhausted bound at trigger time, Paperclip clears it and follows `recoveryPolicy`: `wake_owner` queues a bounded recovery wake for the assignee, `create_recovery_issue` opens visible issue-backed recovery work, and `escalate_to_board` records a board-visible escalation comment/activity.
-
-Use `blocked` instead of a monitor when no Paperclip assignee owns a responsible polling path. In that case, name the external owner/action or create first-class recovery/blocker work.
-
-### `blocked`
-
-This is explicit waiting state.
-
-A healthy `blocked` issue has an explicit waiting path:
-
-- first-class blockers exist, and each unresolved leaf has a valid action path under this contract
-- the issue has an explicit recovery action that itself has a live or waiting path
-- the issue is waiting on a pending interaction, linked approval, human owner, or clearly named external owner/action
-
-A blocker chain is covered only when its unresolved leaf is live or explicitly waiting. An intermediate `blocked` issue does not make the chain healthy by itself.
-
-A `blocked` issue is stalled when the unresolved blocker leaf has no active run, queued wake, typed participant, pending interaction or approval, user owner, external owner/action, or recovery action. In that case the parent should show the first stalled leaf instead of presenting the dependency as calmly covered.
-
-## 9. Crash and Restart Recovery
-
-Paperclip now treats crash/restart recovery as a stranded-assigned-work problem, not just a stranded-run problem.
-
-There are two distinct failure modes.
-
-### 9.1 Stranded assigned `todo`
-
-Example:
-
-- issue is assigned to an agent
-- status is `todo`
-- the original wake/run died during or after dispatch
-- after restart there is no queued wake and nothing picks the issue back up
-
-Recovery rule:
-
-- if the latest issue-linked run failed/timed out/cancelled and no live execution path remains, Paperclip queues one automatic assignment recovery wake
-- if that recovery wake also finishes and the issue is still stranded, Paperclip moves the issue to `blocked` and opens or updates an explicit recovery action when a bounded owner/action is known; the visible comment is evidence, not the recovery path by itself
-
-This is a dispatch recovery, not a continuation recovery.
-
-### 9.2 Stranded assigned `in_progress`
-
-Example:
-
-- issue is assigned to an agent
-- status is `in_progress`
-- the live run disappeared
-- after restart there is no active run and no queued continuation
-
-Recovery rule:
-
-- Paperclip queues one automatic continuation wake
-- if that continuation wake also finishes and the issue is still stranded, Paperclip moves the issue to `blocked` and opens or updates an explicit recovery action when a bounded owner/action is known; the visible comment is evidence, not the recovery path by itself
-
-This is an active-work continuity recovery.
-
-### 9.3 Recovery model-profile lane
-
-Cheap model profiles are only for status-only operational recovery overhead. Paperclip may request `modelProfile: "cheap"` for bounded recovery-owner work that updates task liveness, clears bad status, records a disposition, or asks for human/manager intervention. Those wakes must carry guard context such as `allowDeliverableWork: false`, `allowDocumentUpdates: false`, and `resumeRequiresNormalModel: true`.
-
-Automatic retries that can continue source work must use the original/normal model lane. This includes failed source-work retries, process-loss retries, transient/scheduled retries, max-turn continuations, source-assignee continuations, assigned-todo dispatch recovery, and any run that can update repo files, issue documents, plans, work products, or attachments. When a cheap status-only recovery determines that actual work remains, it must hand back to a normal-model worker run before source work or persistent deliverable updates resume. Cheap recovery hints must be scrubbed from copied retry, resume, child, and downstream source-work contexts.
-
-## 10. Startup and Periodic Reconciliation
-
-Startup recovery and periodic recovery are different from normal wakeup delivery.
-
-On startup and on the periodic recovery loop, Paperclip now does five things in sequence:
-
-1. reap orphaned `running` runs
-2. resume persisted `queued` runs
-3. reconcile stranded assigned work
-4. scan silent active runs, revalidate their source issues, and either fold source-resolved watchdogs or create/update explicit watchdog recovery actions
-5. reconcile productivity reviews
-
-The stranded-work pass closes the gap where issue state survives a crash but the wake/run path does not. The silent-run scan covers the separate case where a live process exists but has stopped producing observable output. The productivity-review pass is later and separate; it reviews unusual progression patterns on assigned source issues, not stale run handles after a source issue already has a valid disposition.
-
-## 11. Silent Active-Run Watchdog
-
-An active run can still be unhealthy even when its process is `running`. Paperclip treats prolonged output silence as a watchdog signal, not as proof that the run is failed.
-
-The recovery service owns this contract:
-
-- classify active-run output silence as `ok`, `suspicious`, `critical`, `snoozed`, or `not_applicable`
-- collect bounded evidence from run logs, recent run events, child issues, and blockers
-- preserve redaction and truncation before evidence is written to issue descriptions
-- create at most one open watchdog recovery action per run; issue-backed implementations use `stale_active_run_evaluation` issues
-- honor active snooze decisions before creating more review work
-- build the `outputSilence` summary shown by live-run and active-run API responses
-
-Suspicious silence creates a medium-priority watchdog recovery action for the selected recovery owner. Critical silence raises that recovery action to high priority and, when issue-backed evaluation is needed for correctness, blocks the source issue on the explicit evaluation task without cancelling the active process.
-
-Watchdog decisions are explicit operator/recovery-owner decisions:
-
-- `snooze` records an operator-chosen future quiet-until time and suppresses scan-created review work during that window
-- `continue` records that the current evidence is acceptable, does not cancel or mutate the active run, and sets a 30-minute default re-arm window before the watchdog evaluates the still-silent run again
-- `dismissed_false_positive` records why the review was not actionable
-
-Operators should prefer `snooze` for known time-bounded quiet periods. `continue` is only a short acknowledgement of the current evidence; if the run remains silent after the re-arm window, the periodic watchdog scan can create or update review work again.
-
-The board can record watchdog decisions. The assigned owner of an issue-backed watchdog evaluation can also record them. Other agents cannot.
-
-### Source-aware watchdog folding
-
-Active-run watchdog work is source-aware. Before the watchdog creates, refreshes, escalates, or blocks on reviewer work, it must re-read the linked source issue and decide whether the watchdog signal is still about productive source work or only about stale run/process bookkeeping.
-
-Fold watchdog work when all of these are true:
-
-- the run is linked to a source issue in the same company
-- the source issue is terminal (`done` or `cancelled`)
-- durable source activity from the same run proves the source issue reached that terminal disposition after the stale-run or output-silence evidence point
-- there is no independent evidence that the still-running or detached process is doing harmful work, still owns external cleanup that needs an operator decision, or needs a separate security/ownership review
-
-Folding means resolving or cancelling the watchdog recovery action or issue-backed evaluation through the explicit recovery lifecycle. It must preserve the run id, source issue, detected silence or detached-process evidence, terminal source activity, decision reason, and best-effort process cleanup result. It must be idempotent for the `(companyId, runId, sourceIssueId)` signal and must not recursively recover the watchdog evaluation issue itself.
-
-Do not fold watchdog work only because the run is quiet. The watchdog must still create or continue reviewer work when:
-
-- the source issue is still `todo` or `in_progress`, because productive work may still be happening or stuck
-- the source issue remains `in_progress` after a successful run with no valid disposition, because the successful-run handoff path owns that bounded correction
-- the run terminated or disappeared while the source issue remains `in_progress` without a live path, because stranded assigned recovery owns that continuity repair
-- the source issue is terminal but there is no durable same-run terminal activity after the stale evidence point
-- there is independent evidence that the process may still be mutating external state, leaking resources, crossing company or ownership boundaries, or otherwise needs operator review
-
-In the normal non-terminal case, critical silence can still create issue-backed evaluation work and block the source issue when blocking is necessary for correctness. In the source-resolved case, a completed source issue should not acquire a new manager review or blocker merely because an old run handle stayed active; only real unresolved work should block work.
-
-This is distinct from productivity review. Productivity review asks whether an assigned source issue has unusual progression patterns, such as no-comment terminal-run streaks, long active duration, or high churn. Source-resolved watchdog folding asks whether a stale active-run signal outlived a source issue that already reached a valid terminal disposition. One does not substitute for the other.
-
-Detached process cleanup is operational hygiene, not source issue liveness. Cleanup should be best-effort and auditable. If cleanup fails but the source issue is already terminal with same-run durable evidence, Paperclip should preserve the cleanup failure on the run/watchdog audit trail and route only the cleanup concern to bounded recovery when a real owner/action remains.
-
-## 12. Auto-Recover vs Explicit Recovery vs Human Escalation
-
-Paperclip uses three different recovery outcomes, depending on how much it can safely infer.
-
-### Auto-Recover
-
-Auto-recovery is allowed when ownership is clear and the control plane only lost execution continuity.
-
-Examples:
-
-- requeue one dispatch wake for an assigned `todo` issue whose latest run failed, timed out, or was cancelled
-- requeue one continuation wake for an assigned `in_progress` issue whose live execution path disappeared
-- assign an orphan blocker back to its creator when that blocker is already preventing other work
-
-Auto-recovery preserves the existing owner. It does not choose a replacement agent.
-
-### Explicit Recovery Action
-
-Paperclip opens an explicit recovery action when the system can identify a problem but cannot safely complete the work itself.
-
-Examples:
-
-- automatic stranded-work retry was already exhausted
-- a dependency graph has an invalid/uninvokable owner, unassigned blocker, or invalid review participant
-- an active run is silent past the watchdog threshold
-
-The recovery action stays source-scoped by default. The source issue should show the recovery owner, cause, evidence, next action, and wake or monitor policy in its own thread/detail surface.
-
-Create an issue-backed recovery action only when a separate issue is the right execution object. In that fallback form, the source issue remains visible and is blocked on the recovery issue when blocking is necessary for correctness. The recovery owner must restore a live path, resolve the source issue manually, delegate real follow-up work, or record the reason the signal is a false positive.
-
-Instance-level issue-graph liveness auto-recovery is disabled by default. When enabled, its lookback window means "dependency paths updated within the last N hours"; older findings remain advisory and are counted as outside the configured lookback instead of creating recovery actions automatically. This is an operator noise control, not the older staleness delay for determining whether a chain is old enough to surface.
-
-### Human Escalation
-
-Human escalation is required when the next safe action depends on board judgment, budget/approval policy, or information unavailable to the control plane.
-
-Examples:
-
-- all candidate recovery owners are paused, terminated, pending approval, or budget-blocked
-- the issue is human-owned rather than agent-owned
-- the run is intentionally quiet but needs an operator decision before cancellation or continuation
-
-In these cases Paperclip should leave a visible issue/comment trail instead of silently retrying.
-
-## 13. What This Does Not Mean
-
-These semantics do not change V1 into an auto-reassignment system.
-
-Paperclip still does not:
-
-- automatically reassign work to a different agent
-- infer dependency semantics from `parentId` alone
-- treat human-held work as heartbeat-managed execution
-
-The recovery model is intentionally conservative:
-
-- preserve ownership
-- retry once when the control plane lost execution continuity
-- open an explicit recovery action when the system can identify a bounded recovery owner/action
-- escalate visibly when the system cannot safely keep going
-
-## 14. Practical Interpretation
-
-For a board operator, the intended meaning is:
-
-- agent-owned `in_progress` should mean \"this is live work or clearly surfaced as a problem\"
-- agent-owned `todo` should not stay assigned forever after a crash with no remaining wake path
-- parent/sub-issue explains structure
-- blockers explain waiting
-
-That is the execution contract Paperclip should present to operators.

doc/memory-landscape.md

@@ -22,7 +22,6 @@ The question is not "which memory project wins?" The question is "what is the sm
 ### Hosted memory APIs
 
 - `mem0`
-- `AWS Bedrock AgentCore Memory`
 - `supermemory`
 - `Memori`
 
@@ -50,7 +49,6 @@ These emphasize local persistence, inspectability, and low operational overhead.
 |---|---|---|---|---|
 | [nuggets](https://github.com/NeoVertex1/nuggets) | local memory engine + messaging gateway | topic-scoped HRR memory with `remember`, `recall`, `forget`, fact promotion into `MEMORY.md` | good example of lightweight local memory and automatic promotion | very specific architecture; not a general multi-tenant service |
 | [mem0](https://github.com/mem0ai/mem0) | hosted + OSS SDK | `add`, `search`, `getAll`, `get`, `update`, `delete`, `deleteAll`; entity partitioning via `user_id`, `agent_id`, `run_id`, `app_id` | closest to a clean provider API with identities and metadata filters | provider owns extraction heavily; Paperclip should not assume every backend behaves like mem0 |
-| [AWS Bedrock AgentCore Memory](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/memory.html) | AWS-managed memory service | explicit short-term and long-term memories, actor/session/event APIs, memory strategies, namespace templates, optional self-managed extraction pipeline | strong example of provider-managed memory with clear scoped ids, retention controls, and standalone API access outside a single agent framework | AWS-hosted and IAM-centric; Paperclip would still need its own company/run/comment provenance, cost rollups, and likely a plugin wrapper instead of baking AWS semantics into core |
 | [MemOS](https://github.com/MemTensor/MemOS) | memory OS / framework | unified add-retrieve-edit-delete, memory cubes, multimodal memory, tool memory, async scheduler, feedback/correction | strong source for optional capabilities beyond plain search | much broader than the minimal contract Paperclip should standardize first |
 | [supermemory](https://github.com/supermemoryai/supermemory) | hosted memory + context API | `add`, `profile`, `search.memories`, `search.documents`, document upload, settings; automatic profile building and forgetting | strong example of "context bundle" rather than raw search results | heavily productized around its own ontology and hosted flow |
 | [memU](https://github.com/NevaMind-AI/memU) | proactive agent memory framework | file-system metaphor, proactive loop, intent prediction, always-on companion model | good source for when memory should trigger agent behavior, not just retrieval | proactive assistant framing is broader than Paperclip's task-centric control plane |
@@ -79,7 +77,6 @@ These differences are exactly why Paperclip needs a layered contract instead of
 ### 1. Who owns extraction?
 
 - `mem0`, `supermemory`, and `Memori` expect the provider to infer memories from conversations.
-- `AWS Bedrock AgentCore Memory` supports both provider-managed extraction and self-managed pipelines where the host writes curated long-term memory records.
 - `memsearch` expects the host to decide what markdown to write, then indexes it.
 - `MemOS`, `memU`, `EverMemOS`, and `OpenViking` sit somewhere in between and often expose richer memory construction pipelines.
 
@@ -107,7 +104,6 @@ Paperclip should make plain search the minimum contract and richer outputs optio
 ### 4. Is memory synchronous or asynchronous?
 
 - local tools often work synchronously in-process.
-- `AWS Bedrock AgentCore Memory` is synchronous at the API edge, but its long-term memory path includes background extraction/indexing behavior and retention policies managed by the provider.
 - larger systems add schedulers, background indexing, compaction, or sync jobs.
 
 Paperclip needs both direct request/response operations and background maintenance hooks.

doc/plans/2026-03-14-adapter-skill-sync-rollout.md

@@ -1,6 +1,6 @@
 # 2026-03-14 Adapter Skill Sync Rollout
 
-Status: Implemented for local adapters; gateway remains unsupported
+Status: Proposed
 Date: 2026-03-14
 Audience: Product and engineering
 Related:
@@ -25,10 +25,8 @@ Paperclip currently has these adapters:
 
 - `claude_local`
 - `codex_local`
-- `cursor`
+- `cursor_local`
 - `gemini_local`
-- `grok_local`
-- `acpx_local`
 - `opencode_local`
 - `pi_local`
 - `openclaw_gateway`
@@ -41,14 +39,12 @@ The current skill API supports:
 
 Current implementation state:
 
-- `codex_local`: implemented, `ephemeral`
+- `codex_local`: implemented, `persistent`
 - `claude_local`: implemented, `ephemeral`
-- `cursor`: implemented, `persistent`
-- `gemini_local`: implemented, `persistent`
-- `pi_local`: implemented, `persistent`
-- `opencode_local`: implemented, `persistent`, with shared Claude skills home caveats
-- `acpx_local`: implemented, `ephemeral` for Claude/Codex sub-agents and `unsupported` for custom commands
-- `grok_local`: implemented, `ephemeral`
+- `cursor_local`: not yet implemented, but technically suited to `persistent`
+- `gemini_local`: not yet implemented, but technically suited to `persistent`
+- `pi_local`: not yet implemented, but technically suited to `persistent`
+- `opencode_local`: not yet implemented; likely `persistent`, but with special handling because it currently injects into Claude’s shared skills home
 - `openclaw_gateway`: not yet implemented; blocked on gateway protocol support, so `unsupported` for now
 
 ## 3. Product Principles
@@ -68,7 +64,8 @@ These adapters have a stable local skills directory that Paperclip can read and
 
 Candidates:
 
-- `cursor`
+- `codex_local`
+- `cursor_local`
 - `gemini_local`
 - `pi_local`
 - `opencode_local` with caveats
@@ -87,10 +84,7 @@ These adapters do not have a meaningful Paperclip-owned persistent install state
 
 Current adapter:
 
-- `codex_local`
 - `claude_local`
-- `acpx_local` when configured for Claude or Codex
-- `grok_local`
 
 Expected UX:
 
@@ -105,7 +99,6 @@ These adapters cannot support skill sync without new external capabilities.
 
 Current adapter:
 
-- `acpx_local` when configured for custom commands
 - `openclaw_gateway`
 
 Expected UX:
@@ -121,7 +114,7 @@ Expected UX:
 
 Target mode:
 
-- `ephemeral`
+- `persistent`
 
 Current state:
 
@@ -129,15 +122,15 @@ Current state:
 
 Requirements to finish:
 
-- keep runtime-mounted snapshots separate from persistent install snapshots
-- ensure imported company skills can be attached and mounted without manual path work
-- keep `CODEX_HOME/skills` mutation scoped to heartbeat execution, not `skills/sync`
+- keep as reference implementation
+- tighten tests around external custom skills and stale removal
+- ensure imported company skills can be attached and synced without manual path work
 
 Success criteria:
 
-- desired skills are stored in Paperclip
-- selected skills are linked into the effective `CODEX_HOME/skills` during runs
-- no persistent installed/stale state is reported from `skills/sync`
+- list installed managed and external skills
+- sync desired skills into `CODEX_HOME/skills`
+- preserve external user-managed skills
 
 ### 5.2 Claude Local
 
@@ -169,11 +162,18 @@ Target mode:
 
 Technical basis:
 
-- Paperclip reconciles desired skills into `~/.cursor/skills`
+- runtime already injects Paperclip skills into `~/.cursor/skills`
 
-Current state:
+Implementation work:
 
-- implemented
+1. Add `listSkills` for Cursor.
+2. Add `syncSkills` for Cursor.
+3. Reuse the same managed-symlink pattern as Codex.
+4. Distinguish:
+   - managed Paperclip skills
+   - external skills already present
+   - missing desired skills
+   - stale managed skills
 
 Testing:
 
@@ -194,11 +194,14 @@ Target mode:
 
 Technical basis:
 
-- Paperclip reconciles desired skills into `~/.gemini/skills`
+- runtime already injects Paperclip skills into `~/.gemini/skills`
 
-Current state:
+Implementation work:
 
-- implemented
+1. Add `listSkills` for Gemini.
+2. Add `syncSkills` for Gemini.
+3. Reuse managed-symlink conventions from Codex/Cursor.
+4. Verify auth remains untouched while skills are reconciled.
 
 Potential caveat:
 
@@ -216,11 +219,14 @@ Target mode:
 
 Technical basis:
 
-- Paperclip reconciles desired skills into `~/.pi/agent/skills`
+- runtime already injects Paperclip skills into `~/.pi/agent/skills`
 
-Current state:
+Implementation work:
 
-- implemented
+1. Add `listSkills` for Pi.
+2. Add `syncSkills` for Pi.
+3. Reuse managed-symlink helpers.
+4. Verify session-file behavior remains independent from skill sync.
 
 Success criteria:
 
@@ -244,7 +250,9 @@ This is product-risky because:
 
 Plan:
 
-- implemented `listSkills` and `syncSkills`
+Phase 1:
+
+- implement `listSkills` and `syncSkills`
 - treat it as `persistent`
 - explicitly label the home as shared in UI copy
 - only remove stale managed Paperclip skills that are clearly marked as Paperclip-managed
@@ -282,30 +290,6 @@ Future target:
 - likely a fourth truth model eventually, such as remote-managed persistent state
 - for now, keep the current API and treat gateway as unsupported
 
-### 5.8 ACPX Local
-
-Target mode:
-
-- `ephemeral` for built-in Claude/Codex ACPX sub-agents
-- `unsupported` for custom ACP commands
-
-Success criteria:
-
-- Claude/Codex ACPX snapshots show skills as configured for the next session
-- custom command snapshots keep desired skills tracked only and do not imply runtime sync
-
-### 5.9 Grok Local
-
-Target mode:
-
-- `ephemeral`
-
-Success criteria:
-
-- desired skills are stored in Paperclip
-- selected skills are copied into the execution workspace for the next run
-- no persistent installed/stale state is reported from `skills/sync`
-
 ## 6. API Plan
 
 ## 6.1 Keep the current minimal adapter API
@@ -349,13 +333,14 @@ Additional UI requirement for shared-home adapters:
 
 Ship:
 
-- `cursor`
+- `cursor_local`
 - `gemini_local`
 - `pi_local`
 
-Status:
+Rationale:
 
-- implemented
+- these are the closest to Codex in architecture
+- they already inject into stable local skill homes
 
 ### Phase 2: OpenCode shared-home support
 
@@ -363,9 +348,10 @@ Ship:
 
 - `opencode_local`
 
-Status:
+Rationale:
 
-- implemented with shared Claude skills-home warning
+- technically feasible now
+- needs slightly more careful product language because of the shared Claude skills home
 
 ### Phase 3: Gateway support decision
 
@@ -404,10 +390,10 @@ Adapter-wide skill support is ready when all are true:
 
 The recommended immediate order is:
 
-1. `cursor`
+1. `cursor_local`
 2. `gemini_local`
 3. `pi_local`
 4. `opencode_local`
 5. defer `openclaw_gateway`
 
-The local-adapter family now has explicit truth models. The remaining V1 boundary is `openclaw_gateway`, which should stay unsupported until the gateway protocol can report real remote skill state.
+That gets Paperclip from “skills work for Codex and Claude” to “skills work for the whole local-adapter family,” which is the meaningful V1 milestone.

doc/plans/2026-03-17-memory-service-surface-api.md

@@ -7,10 +7,10 @@ Define a Paperclip memory service and surface API that can sit above multiple me
 - company scoping
 - auditability
 - provenance back to Paperclip work objects
-- budget and cost visibility
+- budget / cost visibility
 - plugin-first extensibility
 
-This plan is based on the external landscape summarized in `doc/memory-landscape.md`, the AWS AgentCore comparison captured in [PAP-1274](/PAP/issues/PAP-1274), and the current Paperclip architecture in:
+This plan is based on the external landscape summarized in `doc/memory-landscape.md` and on the current Paperclip architecture in:
 
 - `doc/SPEC-implementation.md`
 - `doc/plugins/PLUGIN_SPEC.md`
@@ -19,26 +19,23 @@ This plan is based on the external landscape summarized in `doc/memory-landscape
 
 ## Recommendation In One Sentence
 
-Paperclip should add a company-scoped memory control plane with company default plus agent override resolution, shared hook delivery, and full operation attribution, while leaving extraction and storage semantics to built-ins and plugins.
+Paperclip should not embed one opinionated memory engine into core. It should add a company-scoped memory control plane with a small normalized adapter contract, then let built-ins and plugins implement the provider-specific behavior.
 
 ## Product Decisions
 
-### 1. Memory resolution is company default plus agent override
+### 1. Memory is company-scoped by default
 
 Every memory binding belongs to exactly one company.
 
-Resolution order in V1:
+That binding can then be:
 
-- company default binding
-- optional per-agent override
-
-There is no per-project override in V1.
-
-Project context can still appear in scope and provenance so providers can use it for retrieval and partitioning, but projects do not participate in binding selection.
+- the company default
+- an agent override
+- a project override later if we need it
 
 No cross-company memory sharing in the initial design.
 
-### 2. Providers are selected by stable binding key
+### 2. Providers are selected by key
 
 Each configured memory provider gets a stable key inside a company, for example:
 
@@ -47,53 +44,36 @@ Each configured memory provider gets a stable key inside a company, for example:
 - `local-markdown`
 - `research-kb`
 
-Agents, tools, and background hooks resolve the active provider by key, not by hard-coded vendor logic.
+Agents and services resolve the active provider by key, not by hard-coded vendor logic.
 
 ### 3. Plugins are the primary provider path
 
 Built-ins are useful for a zero-config local path, but most providers should arrive through the existing Paperclip plugin runtime.
 
-That keeps the core small and matches the broader Paperclip direction that specialized knowledge systems live at the edges.
+That keeps the core small and matches the current direction that optional knowledge-like systems live at the edges.
 
-### 4. Paperclip owns routing, provenance, and policy
+### 4. Paperclip owns routing, provenance, and accounting
 
 Providers should not decide how Paperclip entities map to governance.
 
 Paperclip core should own:
 
-- binding resolution
 - who is allowed to call a memory operation
-- which company, agent, issue, project, run, and subject scope is active
-- what source object the operation belongs to
-- how usage and costs are attributed
-- how operators inspect what happened
+- which company / agent / project scope is active
+- what issue / run / comment / document the operation belongs to
+- how usage gets recorded
 
-### 5. Paperclip exposes shared hooks, providers own extraction
-
-Paperclip should emit a common set of memory hooks that built-ins, third-party adapters, and plugins can all use.
-
-Those hooks should pass structured Paperclip source objects plus normalized metadata. The provider then decides how to extract from those objects.
-
-Paperclip should not force one extraction pipeline or one canonical "memory text" transform before the provider sees the input.
-
-### 6. Automatic memory should start narrow, but the hook surface should be general
+### 5. Automatic memory should be narrow at first
 
 Automatic capture is useful, but broad silent capture is dangerous.
 
-Initial built-in automatic hooks should be:
+Initial automatic hooks should be:
 
-- pre-run hydrate for agent context recall
 - post-run capture from agent runs
-- optional issue comment capture
-- optional issue document capture
+- issue comment / document capture when the binding enables it
+- pre-run recall for agent context hydration
 
-The hook registry itself should be general enough that other providers can subscribe to the same events without core changes.
-
-### 7. No approval gate for binding changes in the open-source product
-
-For the open-source version, changing memory bindings should not require approvals.
-
-Paperclip should still log those changes in activity and preserve full auditability. Approval-gated memory governance can remain an enterprise or future policy layer.
+Everything else should start explicit.
 
 ## Proposed Concepts
 
@@ -103,7 +83,7 @@ A built-in or plugin-supplied implementation that stores and retrieves memory.
 
 Examples:
 
-- local markdown plus semantic index
+- local markdown + vector index
 - mem0 adapter
 - supermemory adapter
 - MemOS adapter
@@ -114,15 +94,6 @@ A company-scoped configuration record that points to a provider and carries prov
 
 This is the object selected by key.
 
-### Memory binding target
-
-A mapping from a Paperclip target to a binding.
-
-V1 targets:
-
-- `company`
-- `agent`
-
 ### Memory scope
 
 The normalized Paperclip scope passed into a provider request.
@@ -134,9 +105,7 @@ At minimum:
 - optional `projectId`
 - optional `issueId`
 - optional `runId`
-- optional `subjectId` for external or user identity
-- optional `sessionKey` for providers that organize memory around sessions
-- optional `namespace` for providers that need an explicit partition hint
+- optional `subjectId` for external/user identity
 
 ### Memory source reference
 
@@ -152,36 +121,24 @@ Supported source kinds should include:
 - `manual_note`
 - `external_document`
 
-### Memory hook
-
-A normalized trigger emitted by Paperclip when something memory-relevant happens.
-
-Initial hook kinds:
-
-- `pre_run_hydrate`
-- `post_run_capture`
-- `issue_comment_capture`
-- `issue_document_capture`
-- `manual_capture`
-
 ### Memory operation
 
-A normalized capture, record-write, query, browse, get, correction, or delete action performed through Paperclip.
+A normalized write, query, browse, or delete action performed through Paperclip.
 
-Paperclip should log every memory operation whether the provider is local, plugin-backed, or external.
+Paperclip should log every operation, whether the provider is local or external.
 
 ## Required Adapter Contract
 
-The required core should be small enough to fit `memsearch`, `mem0`, `Memori`, `MemOS`, or `OpenViking`, but strong enough to satisfy Paperclip's attribution and inspectability requirements.
+The required core should be small enough to fit `memsearch`, `mem0`, `Memori`, `MemOS`, or `OpenViking`.
 
 ```ts
 export interface MemoryAdapterCapabilities {
   profile?: boolean;
+  browse?: boolean;
   correction?: boolean;
+  asyncIngestion?: boolean;
   multimodal?: boolean;
   providerManagedExtraction?: boolean;
-  asyncExtraction?: boolean;
-  providerNativeBrowse?: boolean;
 }
 
 export interface MemoryScope {
@@ -191,8 +148,6 @@ export interface MemoryScope {
   issueId?: string;
   runId?: string;
   subjectId?: string;
-  sessionKey?: string;
-  namespace?: string;
 }
 
 export interface MemorySourceRef {
@@ -213,34 +168,10 @@ export interface MemorySourceRef {
   externalRef?: string;
 }
 
-export interface MemoryHookContext {
-  hookKind:
-    | "pre_run_hydrate"
-    | "post_run_capture"
-    | "issue_comment_capture"
-    | "issue_document_capture"
-    | "manual_capture";
-  hookId: string;
-  triggeredAt: string;
-  actorAgentId?: string;
-  heartbeatRunId?: string;
-}
-
-export interface MemorySourcePayload {
-  text?: string;
-  mimeType?: string;
-  metadata?: Record<string, unknown>;
-  object?: Record<string, unknown>;
-}
-
 export interface MemoryUsage {
   provider: string;
-  biller?: string;
   model?: string;
-  billingType?: "metered_api" | "subscription_included" | "subscription_overage" | "unknown";
-  attributionMode?: "billed_directly" | "included_in_run" | "external_invoice" | "untracked";
   inputTokens?: number;
-  cachedInputTokens?: number;
   outputTokens?: number;
   embeddingTokens?: number;
   costCents?: number;
@@ -248,30 +179,18 @@ export interface MemoryUsage {
   details?: Record<string, unknown>;
 }
 
-export interface MemoryRecordHandle {
-  providerKey: string;
-  providerRecordId: string;
-}
-
-export interface MemoryCaptureRequest {
+export interface MemoryWriteRequest {
   bindingKey: string;
   scope: MemoryScope;
   source: MemorySourceRef;
-  payload: MemorySourcePayload;
-  hook?: MemoryHookContext;
-  mode?: "capture_residue" | "capture_record";
+  content: string;
   metadata?: Record<string, unknown>;
+  mode?: "append" | "upsert" | "summarize";
 }
 
-export interface MemoryRecordWriteRequest {
-  bindingKey: string;
-  scope: MemoryScope;
-  source?: MemorySourceRef;
-  records: Array<{
-    text: string;
-    summary?: string;
-    metadata?: Record<string, unknown>;
-  }>;
+export interface MemoryRecordHandle {
+  providerKey: string;
+  providerRecordId: string;
 }
 
 export interface MemoryQueryRequest {
@@ -283,14 +202,6 @@ export interface MemoryQueryRequest {
   metadataFilter?: Record<string, unknown>;
 }
 
-export interface MemoryListRequest {
-  bindingKey: string;
-  scope: MemoryScope;
-  cursor?: string;
-  limit?: number;
-  metadataFilter?: Record<string, unknown>;
-}
-
 export interface MemorySnippet {
   handle: MemoryRecordHandle;
   text: string;
@@ -306,149 +217,30 @@ export interface MemoryContextBundle {
   usage?: MemoryUsage[];
 }
 
-export interface MemoryListPage {
-  items: MemorySnippet[];
-  nextCursor?: string;
-  usage?: MemoryUsage[];
-}
-
-export interface MemoryExtractionJob {
-  providerJobId: string;
-  status: "queued" | "running" | "succeeded" | "failed" | "cancelled";
-  hookKind?: MemoryHookContext["hookKind"];
-  source?: MemorySourceRef;
-  error?: string;
-  submittedAt?: string;
-  startedAt?: string;
-  finishedAt?: string;
-}
-
 export interface MemoryAdapter {
   key: string;
   capabilities: MemoryAdapterCapabilities;
-  capture(req: MemoryCaptureRequest): Promise<{
-    records?: MemoryRecordHandle[];
-    jobs?: MemoryExtractionJob[];
-    usage?: MemoryUsage[];
-  }>;
-  upsertRecords(req: MemoryRecordWriteRequest): Promise<{
+  write(req: MemoryWriteRequest): Promise<{
     records?: MemoryRecordHandle[];
     usage?: MemoryUsage[];
   }>;
   query(req: MemoryQueryRequest): Promise<MemoryContextBundle>;
-  list(req: MemoryListRequest): Promise<MemoryListPage>;
   get(handle: MemoryRecordHandle, scope: MemoryScope): Promise<MemorySnippet | null>;
   forget(handles: MemoryRecordHandle[], scope: MemoryScope): Promise<{ usage?: MemoryUsage[] }>;
 }
 ```
 
-This contract intentionally does not force a provider to expose its internal graph, file tree, or ontology. It does require enough structure for Paperclip to browse, attribute, and audit what happened.
+This contract intentionally does not force a provider to expose its internal graph, filesystem, or ontology.
 
 ## Optional Adapter Surfaces
 
 These should be capability-gated, not required:
 
+- `browse(scope, filters)` for file-system / graph / timeline inspection
 - `correct(handle, patch)` for natural-language correction flows
 - `profile(scope)` when the provider can synthesize stable preferences or summaries
-- `listExtractionJobs(scope, cursor)` when async extraction needs richer operator visibility
-- `retryExtractionJob(jobId)` when a provider supports re-drive
+- `sync(source)` for connectors or background ingestion
 - `explain(queryResult)` for providers that can expose retrieval traces
-- provider-native browse or graph surfaces exposed through plugin UI
-
-## Lessons From AWS AgentCore Memory API
-
-AWS AgentCore Memory is a useful check on whether this plan is too abstract or missing important operational surfaces.
-
-The broad direction still looks right:
-
-- AWS splits memory into a control plane (`CreateMemory`, `UpdateMemory`, `ListMemories`) and a data plane (`CreateEvent`, `RetrieveMemoryRecords`, `GetMemoryRecord`, `ListMemoryRecords`)
-- AWS separates raw interaction capture from curated long-term memory records
-- AWS supports both provider-managed extraction and self-managed pipelines
-- AWS treats browse and list operations as first-class APIs, not ad hoc debugging helpers
-- AWS exposes extraction jobs instead of hiding asynchronous maintenance completely
-
-That lines up with the Paperclip plan at a high level: provider configuration, scoped writes, scoped retrieval, provider-managed extraction as a capability, and a browse and inspect surface.
-
-The concrete changes Paperclip should take from AWS are:
-
-### 1. Keep config APIs separate from runtime traffic
-
-The rollout should preserve a clean separation between:
-
-- control-plane APIs for binding CRUD, defaults, overrides, and capability metadata
-- runtime APIs and tools for capture, record writes, query, list, get, forget, and extraction status
-
-This keeps governance changes distinct from high-volume memory traffic.
-
-### 2. Distinguish capture from curated record writes
-
-AWS does not flatten everything into one write primitive. It distinguishes captured events from durable memory records.
-
-Paperclip should do the same:
-
-- `capture(...)` for raw run, comment, document, or activity residue
-- `upsertRecords(...)` for curated durable facts and notes
-
-That is a better fit for provider-managed extraction and for manual curation flows.
-
-### 3. Make list and browse first-class
-
-AWS exposes list and retrieve surfaces directly. Paperclip should not make browse optional at the portable layer.
-
-The minimum portable surface should include:
-
-- `query`
-- `list`
-- `get`
-
-Provider-native graph or file browsing can remain optional beyond that.
-
-### 4. Add pagination and cursors for operator inspection
-
-AWS consistently uses pagination on browse-heavy APIs.
-
-Paperclip should add cursor-based pagination to:
-
-- record listing
-- extraction job listing
-- memory operation explorer APIs
-
-Prompt hydration can continue to use `topK`, but operator surfaces need cursors.
-
-### 5. Add explicit session and namespace hints
-
-AWS uses `actorId`, `sessionId`, `namespace`, and `memoryStrategyId` heavily.
-
-Paperclip should keep its own control-plane-centric model, but the adapter contract needs obvious places to map those concepts:
-
-- `sessionKey`
-- `namespace`
-
-The provider adapter can map them to AWS or other vendor-specific identifiers without leaking those identifiers into core.
-
-### 6. Treat asynchronous extraction as a real operational surface
-
-AWS exposes extraction jobs explicitly. Paperclip should too.
-
-Operators should be able to see:
-
-- pending extraction work
-- failed extraction work
-- which hook or source caused the work
-- whether a retry is available
-
-### 7. Keep Paperclip provenance primary
-
-Paperclip should continue to center:
-
-- `companyId`
-- `agentId`
-- `projectId`
-- `issueId`
-- `runId`
-- issue comments, documents, and activity as sources
-
-The lesson from AWS is to support clean mapping into provider-specific models, not to let provider identifiers take over the core product model.
 
 ## What Paperclip Should Persist
 
@@ -456,67 +248,39 @@ Paperclip should not mirror the full provider memory corpus into Postgres unless
 
 Paperclip core should persist:
 
-- memory bindings
-- company default and agent override resolution targets
+- memory bindings and overrides
 - provider keys and capability metadata
 - normalized memory operation logs
-- source references back to issue comments, documents, runs, and activity
 - provider record handles returned by operations when available
-- hook delivery records and extraction job state
-- usage and cost attribution
+- source references back to issue comments, documents, runs, and activity
+- usage and cost data
 
-For external providers, the actual memory payload can remain in the provider.
+For external providers, the memory payload itself can remain in the provider.
 
 ## Hook Model
 
-### Shared hook surface
-
-Paperclip should expose one shared hook system for memory.
-
-That same system must be available to:
-
-- built-in memory providers
-- plugin-based memory providers
-- third-party adapter integrations that want to use memory hooks
-
-### What a hook delivers
-
-Each hook delivery should include:
-
-- resolved binding key
-- normalized `MemoryScope`
-- `MemorySourceRef`
-- structured source payload
-- hook metadata such as hook kind, trigger time, and related run id
-
-The payload should include structured objects where possible so the provider can decide how to extract and chunk.
-
-### Initial automatic hooks
+### Automatic hooks
 
 These should be low-risk and easy to reason about:
 
-1. `pre_run_hydrate`
+1. `pre-run hydrate`
    Before an agent run starts, Paperclip may call `query(... intent = "agent_preamble")` using the active binding.
 
-2. `post_run_capture`
-   After a run finishes, Paperclip may call `capture(...)` with structured run output, excerpts, and provenance.
+2. `post-run capture`
+   After a run finishes, Paperclip may write a summary or transcript-derived note tied to the run.
 
-3. `issue_comment_capture`
-   When enabled on the binding, Paperclip may call `capture(...)` for selected issue comments.
+3. `issue comment / document capture`
+   When enabled on the binding, Paperclip may capture selected issue comments or issue documents as memory sources.
 
-4. `issue_document_capture`
-   When enabled on the binding, Paperclip may call `capture(...)` for selected issue documents.
+### Explicit hooks
 
-### Explicit tools and APIs
-
-These should be tool-driven or UI-driven first:
+These should be tool- or UI-driven first:
 
 - `memory.search`
 - `memory.note`
 - `memory.forget`
 - `memory.correct`
-- memory record list and get
-- extraction-job inspection
+- `memory.browse`
 
 ### Not automatic in the first version
 
@@ -545,69 +309,34 @@ The initial browse surface should support:
 
 - active binding by company and agent
 - recent memory operations
-- recent write and capture sources
-- record list and record detail with source backlinks
+- recent write sources
 - query results with source backlinks
-- extraction job status
-- filters by agent, issue, project, run, source kind, and date
-- provider usage, cost, and latency summaries
+- filters by agent, issue, run, source kind, and date
+- provider usage / cost / latency summaries
 
 When a provider supports richer browsing, the plugin can add deeper views through the existing plugin UI surfaces.
 
 ## Cost And Evaluation
 
-Paperclip should treat memory accounting as two related but distinct concerns:
+Every adapter response should be able to return usage records.
 
-### 1. `memory_operations` is the authoritative audit trail
+Paperclip should roll up:
 
-Every memory action should create a normalized operation record that captures:
-
-- binding
-- scope
-- source provenance
-- operation type
-- success or failure
+- memory inference tokens
+- embedding tokens
+- external provider cost
 - latency
-- usage details reported by the provider
-- attribution mode
-- related run, issue, and agent when available
+- query count
+- write count
 
-This is where operators answer "what memory work happened and why?"
-
-### 2. `cost_events` remains the canonical spend ledger for billable metered usage
-
-The current `cost_events` model is already the canonical cost ledger for token and model spend, and `agent_runtime_state` plus `heartbeat_runs.usageJson` already roll up and summarize run usage.
-
-The recommendation is:
-
-- if a memory operation runs inside a normal Paperclip agent heartbeat and the model usage is already counted on that run, do not create a duplicate `cost_event`
-- instead, store the memory operation with `attributionMode = "included_in_run"` and link it to the related `heartbeatRunId`
-- if a memory provider makes a direct metered model call outside the agent run accounting path, the provider must report usage and Paperclip should create a `cost_event`
-- that direct `cost_event` should still link back to the memory operation, agent, company, and issue or run context when possible
-
-### 3. `finance_events` should carry flat subscription or invoice-style costs
-
-If a memory service incurs:
-
-- monthly subscription cost
-- storage invoices
-- provider platform charges not tied to one request
-
-those should be represented as `finance_events`, not as synthetic per-query memory operations.
-
-That keeps usage telemetry separate from accounting entries like invoices and flat fees.
-
-### 4. Evaluation metrics still matter
-
-Paperclip should record evaluation-oriented metrics where possible:
+It should also record evaluation-oriented metrics where possible:
 
 - recall hit rate
 - empty query rate
 - manual correction count
-- extraction failure count
-- per-binding success and failure counts
+- per-binding success / failure counts
 
-This is important because a memory system that "works" but silently burns budget or silently fails extraction is not acceptable in Paperclip.
+This is important because a memory system that "works" but silently burns budget is not acceptable in Paperclip.
 
 ## Suggested Data Model Additions
 
@@ -615,36 +344,23 @@ At the control-plane level, the likely new core tables are:
 
 - `memory_bindings`
   - company-scoped key
-  - provider id or plugin id
+  - provider id / plugin id
   - config blob
   - enabled status
 
 - `memory_binding_targets`
-  - target type (`company`, `agent`)
+  - target type (`company`, `agent`, later `project`)
   - target id
   - binding id
 
 - `memory_operations`
   - company id
   - binding id
-  - operation type (`capture`, `record_upsert`, `query`, `list`, `get`, `forget`, `correct`)
+  - operation type (`write`, `query`, `forget`, `browse`, `correct`)
   - scope fields
   - source refs
-  - usage, latency, and attribution mode
-  - related heartbeat run id
-  - related cost event id
-  - success or error
-
-- `memory_extraction_jobs`
-  - company id
-  - binding id
-  - operation id
-  - provider job id
-  - hook kind
-  - status
-  - source refs
-  - error
-  - submitted, started, and finished timestamps
+  - usage / latency / cost
+  - success / error
 
 Provider-specific long-form state should stay in plugin state or the provider itself unless a built-in local provider needs its own schema.
 
@@ -666,46 +382,45 @@ The design should still treat that built-in as just another provider behind the
 ### Phase 1: Control-plane contract
 
 - add memory binding models and API types
-- add company default plus agent override resolution
-- add plugin capability and registration surface for memory providers
+- add plugin capability / registration surface for memory providers
+- add operation logging and usage reporting
 
-### Phase 2: Hook delivery and operation audit
-
-- add shared memory hook emission in core
-- add operation logging, extraction job state, and usage attribution
-- add direct-provider cost and finance-event linkage rules
-
-### Phase 3: One built-in plus one plugin example
+### Phase 2: One built-in + one plugin example
 
 - ship a local markdown-first provider
 - ship one hosted adapter example to validate the external-provider path
 
-### Phase 4: UI inspection
+### Phase 3: UI inspection
 
-- add company and agent memory settings
+- add company / agent memory settings
 - add a memory operation explorer
-- add record list and detail surfaces
 - add source backlinks to issues and runs
 
+### Phase 4: Automatic hooks
+
+- pre-run hydrate
+- post-run capture
+- selected issue comment / document capture
+
 ### Phase 5: Rich capabilities
 
 - correction flows
-- provider-native browse or graph views
+- provider-native browse / graph views
+- project-level overrides if needed
 - evaluation dashboards
-- retention and quota controls
 
-## Remaining Open Questions
+## Open Questions
 
-- Which built-in local provider should ship first: pure markdown, markdown plus embeddings, or a lightweight local vector store?
-- How much source payload should Paperclip snapshot inside `memory_operations` for debugging without duplicating large transcripts?
-- Should correction flows mutate provider state directly, create superseding records, or both depending on provider capability?
-- What default retention and size limits should the local built-in enforce?
+- Should project overrides exist in V1 of the memory service, or should we force company default + agent override first?
+- Do we want Paperclip-managed extraction pipelines at all, or should built-ins be the only place where Paperclip owns extraction?
+- Should memory usage extend the current `cost_events` model directly, or should memory operations keep a parallel usage log and roll up into `cost_events` secondarily?
+- Do we want provider install / binding changes to require approvals for some companies?
 
 ## Bottom Line
 
 The right abstraction is:
 
-- Paperclip owns bindings, resolution, hooks, provenance, policy, and attribution.
+- Paperclip owns memory bindings, scopes, provenance, governance, and usage reporting.
 - Providers own extraction, ranking, storage, and provider-native memory semantics.
 
-That gives Paperclip a stable memory service without locking the product to one memory philosophy or one vendor, and it integrates the AWS lessons without importing AWS's model into core.
+That gives Paperclip a stable "memory service" without locking the product to one memory philosophy or one vendor.

doc/plans/2026-04-12-vscode-task-interoperability-plan.md

@@ -1,382 +0,0 @@
-# VS Code Task Interoperability Plan
-
-Status: planning only, no code changes
-Date: 2026-04-12
-Related issue: `PAP-1377`
-
-## Summary
-
-Paperclip should not replace its workspace runtime service model with VS Code tasks.
-It should add a narrow interoperability layer that can discover and adopt supported entries from `.vscode/tasks.json`.
-
-The core product model should stay:
-
-- Paperclip owns long-running workspace services and their desired state
-- Paperclip shows operators exactly which named thing they are starting or stopping
-- Paperclip distinguishes long-running services from one-shot jobs
-
-VS Code tasks should be treated as:
-
-- an import/discovery format for workspace commands
-- a convenience for repos that already maintain `tasks.json`
-- a partial compatibility layer, not a full execution model
-
-## Current State
-
-The current implementation is already service-oriented:
-
-- project workspaces and execution workspaces can store `workspaceRuntime` config plus `desiredState` and per-service `serviceStates`
-- the UI renders one control row per configured service and persists start/stop intent
-- the backend supervises long-running local processes, reuses eligible services, and restores desired services on startup
-
-Relevant files:
-
-- `packages/shared/src/types/workspace-runtime.ts`
-- `server/src/services/workspace-runtime.ts`
-- `server/src/services/project-workspace-runtime-config.ts`
-- `ui/src/components/WorkspaceRuntimeControls.tsx`
-- `ui/src/pages/ProjectWorkspaceDetail.tsx`
-- `ui/src/pages/ExecutionWorkspaceDetail.tsx`
-
-This is directionally correct for Paperclip because it gives the control plane an explicit model for service lifecycle, health, reuse, and restart behavior.
-
-## Problem To Solve
-
-The current UX is still too raw:
-
-- operators have to hand-author runtime JSON
-- a workspace can have multiple attached services, but the higher-level intent is not obvious
-- start/stop controls are visible in multiple places, which makes it easy to lose track of what is being controlled
-- there is no interoperability with repos that already define useful local workflows in `.vscode/tasks.json`
-
-The issue is not that services are the wrong abstraction.
-The issue is that the configuration surface is too low-level and Paperclip does not yet leverage existing workspace metadata.
-
-## Recommendation
-
-Keep Paperclip runtime services as the source of truth for service supervision.
-Add a new workspace command model above the raw JSON layer, with VS Code task discovery as one input.
-
-The product model should become:
-
-1. `Workspace command`
-   A named runnable thing attached to a workspace.
-
-2. `Workspace service`
-   A workspace command that is expected to stay alive and be supervised.
-
-3. `Workspace job`
-   A workspace command that runs once and exits.
-
-4. `Runtime service instance`
-   The live process record that already exists today in Paperclip.
-
-In that model, VS Code tasks are a way to populate workspace commands.
-Only commands that map cleanly to Paperclip service or job semantics should become runnable in Paperclip.
-
-## Why Not Fully Adopt VS Code Tasks
-
-VS Code tasks are broader than Paperclip runtime services.
-They include shell/process tasks, compound tasks, background/watch tasks, presentation settings, extension/task-provider types, variable substitution, and problem-matcher-driven lifecycle.
-
-That creates a bad fit if Paperclip tries to use `tasks.json` as its only runtime model:
-
-- many tasks are one-shot jobs, not long-running services
-- some tasks depend on VS Code task providers or editor-only variable resolution
-- compound task graphs are useful, but they are not the same thing as a supervised service
-- problem matcher readiness is useful metadata, but it is not enough to replace Paperclip's persisted service lifecycle model
-
-The right boundary is interoperability, not replacement.
-
-## Interoperability Contract
-
-Paperclip should support a conservative subset of VS Code tasks and clearly mark unsupported entries.
-
-### Supported in phase 1
-
-- `shell` and `process` tasks with a concrete command Paperclip can resolve
-- optional task `options.cwd`
-- optional task environment values that can be flattened safely
-- task labels and detail text for naming and display
-- `dependsOn` for import-time expansion or display-only dependency hints
-- background/watch-oriented tasks that can reasonably be treated as long-running services
-
-### Maybe supported in later phases
-
-- grouping and default task metadata for better UX
-- selected variable substitution when Paperclip can resolve it safely from workspace context
-- mapping task metadata into Paperclip readiness/expose hints
-- limited compound-task launch flows
-
-### Not supported initially
-
-- extension-provided task types Paperclip cannot execute directly
-- arbitrary VS Code variable substitution semantics
-- problem matcher parsing as the main source of service health
-- full parity with VS Code task execution behavior
-
-## Long-Running Service Detection
-
-Paperclip needs an explicit classification layer instead of assuming every VS Code task is a service.
-
-Recommended classification:
-
-- `service`
-  Explicitly marked by Paperclip metadata, or confidently inferred from background/watch task semantics
-
-- `job`
-  One-shot command expected to exit
-
-- `unsupported`
-  Present in `tasks.json`, but not safely runnable by Paperclip
-
-The important product decision is that service classification must be visible and editable by the operator.
-Inference can help, but it should not be the only source of truth.
-
-## Proposed Product Shape
-
-### 1. Replace raw-first editing with command-first editing
-
-Project and execution workspace pages should stop making raw runtime JSON the primary editing surface.
-
-Default UI should show:
-
-- workspace commands
-- command type: service or job
-- source: Paperclip or VS Code
-- exact command and cwd
-- current state for services
-- explicit start, stop, restart, and run-now actions
-
-Raw JSON should remain available behind an advanced section.
-
-### 2. Add VS Code task discovery on workspaces
-
-For a workspace with `cwd`, Paperclip should look for `.vscode/tasks.json`.
-
-The workspace UI should show:
-
-- whether a `tasks.json` file was found
-- last parse time
-- supported commands discovered
-- unsupported tasks with reasons
-- whether commands are inherited into execution workspaces
-
-### 3. Make the controlled thing explicit
-
-Start and stop UI should always name the exact entry being controlled.
-
-Examples:
-
-- `Start web`
-- `Stop api`
-- `Run db:migrate`
-
-Avoid generic workspace-level labels when multiple commands exist.
-
-### 4. Separate services from jobs in the UI
-
-Do not mix one-shot jobs and long-running services into one undifferentiated list.
-
-Recommended sections:
-
-- `Services`
-- `Jobs`
-- `Unsupported imported tasks`
-
-That resolves the ambiguity called out in the issue.
-
-## Data Model Direction
-
-Do not replace `workspaceRuntime` immediately.
-Instead add a higher-level representation that can compile down to the existing runtime-service machinery.
-
-Suggested workspace metadata shape:
-
-```ts
-type WorkspaceCommandSource =
-  | { type: "paperclip" }
-  | { type: "vscode_task"; taskLabel: string; taskPath: ".vscode/tasks.json" };
-
-type WorkspaceCommandKind = "service" | "job";
-
-type WorkspaceCommandDefinition = {
-  id: string;
-  name: string;
-  kind: WorkspaceCommandKind;
-  source: WorkspaceCommandSource;
-  command: string | null;
-  cwd: string | null;
-  env?: Record<string, string> | null;
-  autoStart?: boolean;
-  serviceConfig?: {
-    lifecycle?: "shared" | "ephemeral";
-    reuseScope?: "project_workspace" | "execution_workspace" | "run";
-    readiness?: Record<string, unknown> | null;
-    expose?: Record<string, unknown> | null;
-  } | null;
-  importWarnings?: string[];
-  disabledReason?: string | null;
-};
-```
-
-`workspaceRuntime` can then become a derived or advanced representation for service-type commands until the rest of the system is migrated.
-
-## VS Code Mapping Rules
-
-Paperclip should map imported tasks with explicit, documented rules.
-
-Recommended rules:
-
-1. A task becomes a `job` by default.
-2. A task becomes a `service` only when:
-   - Paperclip metadata marks it as a service, or
-   - the task clearly represents a background/watch process and the operator confirms the classification.
-3. Unsupported tasks stay visible but disabled.
-4. Task labels become default command names.
-5. `dependsOn` is preserved as metadata, not silently flattened into hidden behavior.
-
-Paperclip-specific metadata can live in a namespaced field on the imported task definition, for example:
-
-```json
-{
-  "label": "web",
-  "type": "shell",
-  "command": "pnpm dev",
-  "isBackground": true,
-  "paperclip": {
-    "kind": "service",
-    "readiness": {
-      "type": "http",
-      "urlTemplate": "http://127.0.0.1:${port}"
-    },
-    "expose": {
-      "type": "url",
-      "urlTemplate": "http://127.0.0.1:${port}"
-    }
-  }
-}
-```
-
-That gives us interoperability without depending on VS Code-only semantics for service readiness and exposure.
-
-## Execution Policy
-
-Project workspaces should be the main place where imported commands are discovered and curated.
-Execution workspaces should inherit that curated command set by default, with optional issue-level overrides.
-
-Recommended precedence:
-
-1. execution workspace override
-2. project workspace command set
-3. imported VS Code tasks from the linked workspace
-4. advanced raw runtime fallback
-
-This matches the existing direction in `doc/plans/2026-03-10-workspace-strategy-and-git-worktrees.md`.
-
-## Implementation Plan
-
-### Phase 1: Discovery and read-only visibility
-
-Goal:
-show imported VS Code tasks in the workspace UI without changing runtime behavior.
-
-Work:
-
-- parse `.vscode/tasks.json` for project workspaces with local `cwd`
-- derive a list of candidate commands plus unsupported items
-- show source, label, command, cwd, and classification
-- show parse warnings and unsupported reasons
-
-Success condition:
-an operator can see what Paperclip would import and why.
-
-### Phase 2: Command model and explicit classification
-
-Goal:
-introduce a first-class workspace command layer above raw runtime JSON.
-
-Work:
-
-- add a persisted command definition model in workspace metadata or a dedicated table
-- allow operator edits to imported command classification
-- separate `service` and `job` in UI
-- keep existing runtime-service storage for live supervised processes
-
-Success condition:
-the workspace UI is command-first, and raw runtime JSON is advanced-only.
-
-### Phase 3: Service execution backed by existing runtime supervisor
-
-Goal:
-run supported imported service commands through the current Paperclip supervisor.
-
-Work:
-
-- compile service commands into the existing runtime service start/stop path
-- persist desired state per named command
-- keep startup restoration behavior for service commands
-- make the active command name explicit everywhere control actions appear
-
-Success condition:
-imported service commands behave like native Paperclip services once adopted.
-
-### Phase 4: Job execution and optional dependency handling
-
-Goal:
-support one-shot imported commands without pretending they are services.
-
-Work:
-
-- add `Run` actions for jobs
-- record output in workspace operations
-- optionally support simple `dependsOn` execution for jobs with clear logging
-
-Success condition:
-one-shot tasks are runnable, but they are not mixed into the service lifecycle model.
-
-### Phase 5: Adapter and execution workspace integration
-
-Goal:
-let agents and issue-scoped workspaces consume the curated command model consistently.
-
-Work:
-
-- expose inherited workspace commands to execution workspaces
-- allow issue-level selection of a default service command when relevant
-- make service selection explicit in issue and workspace views
-
-Success condition:
-agents, operators, and workspaces all refer to the same named commands.
-
-## Non-Goals
-
-- full VS Code task-runner parity
-- support for every VS Code task type
-- removal of Paperclip's own runtime supervision model
-- editor-dependent execution semantics inside the control plane
-
-## Risks
-
-- overfitting Paperclip to VS Code and making the model worse for non-VS-Code repos
-- misclassifying watch tasks as durable services
-- hiding too much detail and making debugging harder
-- allowing imported task graphs to become implicit magic
-
-These risks are manageable if the import layer stays explicit, conservative, and operator-editable.
-
-## Decision
-
-Paperclip should adopt VS Code tasks as an optional workspace command source, not as the canonical runtime model.
-
-The main UX change should be:
-
-- move from raw runtime JSON to named workspace commands
-- separate services from jobs
-- make the exact controlled command explicit
-- let `.vscode/tasks.json` pre-populate those commands when available
-
-## External References
-
-- VS Code tasks documentation: https://code.visualstudio.com/docs/debugtest/tasks
-- Existing Paperclip workspace plan: `doc/plans/2026-03-10-workspace-strategy-and-git-worktrees.md`

doc/plans/2026-04-26-plugin-secret-ref-company-scope.md

@@ -1,86 +0,0 @@
-# Plugin Secret Refs: Company Scope Reintroduction Plan
-
-Date: 2026-04-26
-Status: follow-up after fail-closed mitigation
-Related issue: PAP-2394
-
-## Current state
-
-`PAP-2394` now fails closed:
-
-- `POST /api/plugins/:pluginId/config` rejects any config containing plugin secret refs.
-- `ctx.secrets.resolve()` is disabled for plugin workers.
-
-This removes the release-blocking cross-company exposure path, but it also disables plugin secret-ref support until the runtime carries company scope end to end.
-
-## Vulnerability summary
-
-The original design mixed an instance-global config store with company-scoped secret bindings:
-
-- [server/src/routes/plugins.ts](/Users/dotta/paperclip/.paperclip/worktrees/PAP-2339-secrets-make-a-plan/server/src/routes/plugins.ts:1898) saved one global plugin config row, then wrote bindings into `company_secret_bindings` grouped by each referenced secret's owning company.
-- [packages/db/src/schema/plugin_config.ts](/Users/dotta/paperclip/.paperclip/worktrees/PAP-2339-secrets-make-a-plan/packages/db/src/schema/plugin_config.ts:15) stored one config row per plugin, with no company dimension.
-- [packages/db/src/schema/company_secret_bindings.ts](/Users/dotta/paperclip/.paperclip/worktrees/PAP-2339-secrets-make-a-plan/packages/db/src/schema/company_secret_bindings.ts:5) already modeled bindings as company-scoped.
-- [server/src/services/plugin-secrets-handler.ts](/Users/dotta/paperclip/.paperclip/worktrees/PAP-2339-secrets-make-a-plan/server/src/services/plugin-secrets-handler.ts:212) resolved by `pluginId` + secret UUID, with no active company context from the bridge call.
-- [packages/plugins/sdk/src/worker-rpc-host.ts](/Users/dotta/paperclip/.paperclip/worktrees/PAP-2339-secrets-make-a-plan/packages/plugins/sdk/src/worker-rpc-host.ts:384) exposed `ctx.config.get()` and `ctx.secrets.resolve()` without a company parameter.
-
-This violated Least Privilege, Complete Mediation, and Secure Defaults.
-
-## Recommended end state
-
-Re-enable plugin secret refs only after both of these are true:
-
-1. Plugin config reads/writes are company-scoped.
-2. Runtime secret resolution carries explicit company context and enforces it at resolution time.
-
-## Implementation plan
-
-### 1. Make plugin config company-scoped
-
-- Add `company_id` to `plugin_config`, with a unique index on `(plugin_id, company_id)`.
-- Update registry helpers to require `companyId` for `getConfig`, `upsertConfig`, `patchConfig`, and `deleteConfig`.
-- Update plugin config routes to require `companyId` and call `assertCompanyAccess(req, companyId)`.
-- Keep instance-global plugin lifecycle state separate from company-scoped plugin config.
-
-### 2. Propagate company context through the worker runtime
-
-- Extend the SDK so `ctx.config.get()` and `ctx.secrets.resolve()` can receive or derive `companyId`.
-- Introduce worker request context storage for handlers that already run with company scope:
-  - `getData`
-  - `performAction`
-  - scoped API routes
-  - tool executions
-  - environment driver calls
-- Fail closed when plugin code tries to read company-scoped config or secrets outside an active company context.
-
-### 3. Rebind secrets by `(companyId, pluginId, configPath)`
-
-- On config save, validate every referenced secret belongs to the authorized company.
-- Store bindings only for that company.
-- Resolve secrets only by the current company-scoped binding, never by bare plugin ID plus UUID.
-- Treat stale bindings as invalid and remove them on config replacement.
-
-### 4. Prevent cross-company config disclosure
-
-- When returning config to the UI, only materialize the selected company's secret refs.
-- Never expose another company's secret UUIDs through the global plugin config surface.
-
-## Required regression coverage
-
-- Company A board user cannot save plugin config that references a Company B secret.
-- Company A plugin execution cannot resolve a Company B secret even if the same plugin is configured for Company B.
-- Company-scoped config reads only return the selected company's secret bindings.
-- Config replacement removes stale bindings for the same `(companyId, pluginId)` target.
-- Runtime calls without company context fail closed.
-
-## Migration notes
-
-- Existing `plugin_config` rows need a migration strategy before re-enable.
-- Safest default: do not auto-assume a company for historical secret refs.
-- Prefer one of:
-  - explicit admin migration per company, or
-  - import existing rows as non-secret config only and require re-entry of secret refs.
-
-## Release posture
-
-- Keep plugin secret refs disabled until all steps above land.
-- Do not restore the feature behind a soft warning; the insecure path must remain unavailable by default.

doc/plans/2026-05-05-scaled-kanban-board-design.md

@@ -1,90 +0,0 @@
-# Scaled Kanban Board Design
-
-Date: 2026-05-05
-Branch: `feat/scaled-kanban-board`
-
-## Context
-
-The Issues page currently supports list and board modes. List mode already has grouping, sorting, filtering, nested parent/child rows, deferred row rendering, and incremental render limits. Board mode uses classic status columns with draggable cards. It fetches per-status board data, but the current UI still presents each lane as an unbounded stack of cards, which becomes tall and heavy when a company has hundreds of issues.
-
-The goal is to keep the Kanban mental model while making high-volume boards usable. This is a UI-first change. It should not introduce schema changes or new API contracts in the first pass.
-
-## Problem
-
-When Paperclip has many issues, board columns get too tall and slow. The operator loses the ability to scan the board quickly, and rendering or dragging through long columns becomes unpleasant. The first version should solve this by reducing the number of visible cards per column and by collapsing low-signal columns, not by replacing Kanban with a different inventory surface.
-
-## Design
-
-Board mode remains status-column based. Each column shows its total issue count, a bounded set of visible cards, and a local affordance to reveal more cards in that column. The board should keep active workflow lanes expanded by default and collapse cold or noisy lanes once issue volume is high.
-
-Default high-volume behavior activates when the filtered board has more than 100 issues:
-
-- Compact cards are used by default.
-- `backlog`, `done`, and `cancelled` auto-collapse to narrow rails.
-- `todo`, `in_progress`, `in_review`, and `blocked` remain expanded by default.
-- Each expanded column renders an initial 10 cards by default.
-- The user can choose a page size of 10, 25, or 50 cards per column.
-- The user can reveal one additional page at a time in each column without changing other columns.
-- Drag and drop continues to work for visible cards.
-
-The toolbar should expose compact controls for:
-
-- toggling compact cards
-- hiding or showing cold lanes
-- choosing cards per column
-- resetting board density to defaults
-
-These preferences should persist through the existing issue view-state/localStorage mechanism and remain scoped by company.
-
-## Component Shape
-
-`IssuesList` remains the owner of issue board view state. It should store board-density preferences alongside the existing issue view state, including compact card preference, cold-lane mode, and cards-per-column page size.
-
-`KanbanBoard` receives board tuning props from `IssuesList` and delegates per-lane display to `KanbanColumn`.
-
-`KanbanColumn` owns only local presentation mechanics for a lane:
-
-- whether the lane is rendered as an expanded column or collapsed rail
-- how many cards are currently visible in that lane
-- the local "show more" action
-
-`KanbanCard` gets a compact variant. The compact card should still show the issue identifier, title, live state, priority, and assignee when available, but with tighter spacing and fewer vertical affordances.
-
-## Data Flow
-
-The first implementation uses the current issue data already available to board mode. No database, shared type, or route change is required.
-
-Column totals are computed from the in-memory filtered board issues. If a column reaches the existing remote board query cap, the existing warning remains the truth source that more filtering may be required.
-
-Future server-side column pagination can be added later if the UI-only version is not enough for very large instances.
-
-## Error Handling
-
-This feature should not introduce new network errors. Existing issue loading and update errors continue to surface through the Issues page.
-
-For drag and drop:
-
-- Moving a visible card keeps the current optimistic behavior.
-- Hidden cards remain hidden until revealed.
-- A collapsed lane rail is a valid drop target. Dropping onto it moves the issue to that status and keeps the lane collapsed.
-
-## Testing
-
-Focused tests should cover:
-
-- board mode passes density preferences into `KanbanBoard`
-- columns render only the initial visible card count
-- "show more" reveals more cards in a single column
-- high-volume cold lanes render as collapsed rails by default
-- compact cards preserve identifier/title/live/priority/assignee signals
-- drag/drop status updates still call `onUpdateIssue`
-
-Manual verification should include opening the Issues board with a large fixture or mocked issue set and confirming that columns remain usable with hundreds of issues.
-
-## Out of Scope
-
-- Server-side per-column pagination
-- New issue schema fields
-- Replacing Kanban with a dense table or action-only board
-- Changing issue status semantics
-- Broad visual redesign of the Issues page

doc/plans/2026-05-05-scaled-kanban-board.md

@@ -1,250 +0,0 @@
-# Scaled Kanban Board Implementation Plan
-
-> **For agentic workers:** REQUIRED SUB-SKILL: Use superpowers:subagent-driven-development (recommended) or superpowers:executing-plans to implement this plan task-by-task. Steps use checkbox (`- [ ]`) syntax for tracking.
-
-**Goal:** Make the Issues Kanban board usable with hundreds of issues by adding compact high-volume rendering, collapsed cold lanes, and per-column reveal controls.
-
-**Architecture:** Keep the change UI-only. `IssuesList` owns persisted board density preferences in existing company-scoped view state, while `KanbanBoard` owns lane rendering, card density, collapsed rails, and per-column "show more" state.
-
-**Tech Stack:** React 19, TypeScript, Vite, Vitest/jsdom, `@dnd-kit/core`, `@dnd-kit/sortable`, Tailwind utility classes.
-
----
-
-## File Structure
-
-- Modify `ui/src/components/IssuesList.tsx`: extend `IssueViewState`, derive high-volume board preferences, add toolbar controls, pass props into `KanbanBoard`.
-- Modify `ui/src/components/KanbanBoard.tsx`: add compact cards, collapsed rail lanes, visible-card limits, and per-column reveal behavior.
-- Create `ui/src/components/KanbanBoard.test.tsx`: focused tests for high-volume behavior and drag/drop update callback.
-- Modify `ui/src/components/IssuesList.test.tsx`: update the mocked `KanbanBoard` expectations for new props.
-- Keep `doc/plans/2026-05-05-scaled-kanban-board-design.md` as the design source of truth.
-
-## Task 1: Add Kanban Board Scaling Mechanics
-
-**Files:**
-- Modify: `ui/src/components/KanbanBoard.tsx`
-- Create: `ui/src/components/KanbanBoard.test.tsx`
-
-- [ ] **Step 1: Write focused tests**
-
-Create `ui/src/components/KanbanBoard.test.tsx` with tests that render 60 todo issues and assert:
-
-```tsx
-renderBoard({ issues: createIssues(60, "todo"), compactCards: true, initialVisibleCount: 10, revealIncrement: 10 });
-expect(container.textContent).toContain("Showing 10 of 60");
-expect(container.textContent).toContain("Show 10 more");
-```
-
-Also test collapsed rails:
-
-```tsx
-renderBoard({ issues: createIssues(3, "done"), collapsedStatuses: ["done"] });
-expect(container.textContent).toContain("Done");
-expect(container.textContent).toContain("3");
-expect(container.textContent).not.toContain("Issue 1");
-```
-
-- [ ] **Step 2: Run tests to verify failure**
-
-Run:
-
-```bash
-pnpm exec vitest run ui/src/components/KanbanBoard.test.tsx
-```
-
-Expected: fail because `KanbanBoard.test.tsx` is new and the props/behavior do not exist.
-
-- [ ] **Step 3: Implement minimal board behavior**
-
-In `KanbanBoard.tsx`, add exported constants:
-
-```ts
-export const KANBAN_BOARD_HIGH_VOLUME_THRESHOLD = 100;
-export const KANBAN_COLUMN_PAGE_SIZE_OPTIONS = [10, 25, 50] as const;
-export const KANBAN_COLUMN_DEFAULT_PAGE_SIZE = 10;
-export const KANBAN_COLD_STATUSES = ["backlog", "done", "cancelled"] as const;
-```
-
-Extend props:
-
-```ts
-compactCards?: boolean;
-collapsedStatuses?: string[];
-initialVisibleCount?: number;
-revealIncrement?: number;
-```
-
-Add per-status visible-count state keyed by status. Expanded columns render `issues.slice(0, visibleCount)` and show a button when hidden issues remain. Collapsed columns render a narrow droppable rail with status icon, label, and count, but no cards.
-
-Reset per-status visible-count state when `initialVisibleCount` or `revealIncrement` changes so choosing a smaller cards-per-column preset does not leave a column expanded past the newly selected page size.
-
-- [ ] **Step 4: Preserve drag/drop**
-
-Keep `DndContext`, `SortableContext`, and `handleDragEnd` status detection. Because collapsed rails use `useDroppable({ id: status })`, dropping a visible card onto a rail continues to resolve `targetStatus` through the existing status-id branch.
-
-- [ ] **Step 5: Run focused test**
-
-Run:
-
-```bash
-pnpm exec vitest run ui/src/components/KanbanBoard.test.tsx
-```
-
-Expected: pass.
-
-- [ ] **Step 6: Commit**
-
-```bash
-git add ui/src/components/KanbanBoard.tsx ui/src/components/KanbanBoard.test.tsx
-git commit -m "Scale kanban board columns"
-```
-
-## Task 2: Wire Board Density State Into IssuesList
-
-**Files:**
-- Modify: `ui/src/components/IssuesList.tsx`
-- Modify: `ui/src/components/IssuesList.test.tsx`
-
-- [ ] **Step 1: Write/update tests**
-
-In `IssuesList.test.tsx`, update the `KanbanBoard` mock to capture:
-
-```ts
-compactCards?: boolean;
-collapsedStatuses?: string[];
-initialVisibleCount?: number;
-revealIncrement?: number;
-```
-
-Add a test that stores board mode in localStorage, renders more than 100 issues, and expects:
-
-```ts
-expect(mockKanbanBoard).toHaveBeenLastCalledWith(expect.objectContaining({
-  compactCards: true,
-  collapsedStatuses: expect.arrayContaining(["backlog", "done", "cancelled"]),
-  initialVisibleCount: 10,
-  revealIncrement: 10,
-}));
-```
-
-- [ ] **Step 2: Run test to verify failure**
-
-Run:
-
-```bash
-pnpm exec vitest run ui/src/components/IssuesList.test.tsx
-```
-
-Expected: fail because `IssuesList` does not pass the new props yet.
-
-- [ ] **Step 3: Add persisted board density preferences**
-
-Extend `IssueViewState`:
-
-```ts
-boardCardDensity: "auto" | "compact" | "comfortable";
-boardColdLaneMode: "auto" | "collapsed" | "expanded";
-boardColumnPageSize: 10 | 25 | 50;
-```
-
-Default the density modes to `"auto"` and page size to `10`. Derive:
-
-```ts
-const boardHighVolume = viewState.viewMode === "board" && filtered.length > KANBAN_BOARD_HIGH_VOLUME_THRESHOLD;
-const boardCompactCards = viewState.boardCardDensity === "compact"
-  || (viewState.boardCardDensity === "auto" && boardHighVolume);
-const boardCollapsedStatuses = viewState.boardColdLaneMode === "collapsed"
-  || (viewState.boardColdLaneMode === "auto" && boardHighVolume)
-    ? [...KANBAN_COLD_STATUSES]
-    : [];
-```
-
-- [ ] **Step 4: Add toolbar controls**
-
-When `viewState.viewMode === "board"`, add small outline/icon buttons near the existing view controls:
-
-```tsx
-<Button ... title={boardCompactCards ? "Use comfortable cards" : "Use compact cards"}>...</Button>
-<Button ... title={boardCollapsedStatuses.length > 0 ? "Expand cold lanes" : "Collapse cold lanes"}>...</Button>
-<Button ... title="Cards per column">...</Button>
-<Button ... title="Reset board density">...</Button>
-```
-
-Use lucide icons already available or import `ChevronsDownUp`, `PanelTopClose`, and `RotateCcw`.
-
-- [ ] **Step 5: Pass board props**
-
-Update the `KanbanBoard` call:
-
-```tsx
-<KanbanBoard
-  issues={filtered}
-  agents={agents}
-  liveIssueIds={liveIssueIds}
-  compactCards={boardCompactCards}
-  collapsedStatuses={boardCollapsedStatuses}
-  initialVisibleCount={viewState.boardColumnPageSize}
-  revealIncrement={viewState.boardColumnPageSize}
-  onUpdateIssue={onUpdateIssue}
-/>
-```
-
-- [ ] **Step 6: Run focused tests**
-
-Run:
-
-```bash
-pnpm exec vitest run ui/src/components/IssuesList.test.tsx ui/src/components/KanbanBoard.test.tsx
-```
-
-Expected: pass.
-
-- [ ] **Step 7: Commit**
-
-```bash
-git add ui/src/components/IssuesList.tsx ui/src/components/IssuesList.test.tsx
-git commit -m "Wire issue board density controls"
-```
-
-## Task 3: Verification And PR Prep
-
-**Files:**
-- Verify existing changes only.
-
-- [ ] **Step 1: Run targeted UI tests**
-
-```bash
-pnpm exec vitest run ui/src/components/IssuesList.test.tsx ui/src/components/KanbanBoard.test.tsx
-```
-
-Expected: pass.
-
-- [ ] **Step 2: Run broader cheap test path**
-
-```bash
-pnpm test
-```
-
-Expected: pass.
-
-- [ ] **Step 3: Check worktree**
-
-```bash
-git status --short
-```
-
-Expected: only intentional changes before committing, or clean after final commit.
-
-- [ ] **Step 4: Prepare PR**
-
-Read `.github/PULL_REQUEST_TEMPLATE.md` and use it for the PR body. Include:
-
-- design spec path
-- scaled Kanban behavior summary
-- test commands and results
-- Model Used section with the current Codex model details available in this session
-
-## Self-Review
-
-- Spec coverage: The plan covers compact high-volume board cards, collapsed cold lanes, cards-per-column presets, per-column reveal controls, persisted board preferences, current API reuse, and focused tests.
-- Placeholder scan: No unresolved markers or unspecified implementation placeholders remain.
-- Type consistency: The plan consistently uses `boardCardDensity`, `boardColdLaneMode`, `boardColumnPageSize`, `compactCards`, `collapsedStatuses`, `initialVisibleCount`, and `revealIncrement`.

doc/plans/2026-05-06-llm-wiki-paperclip-asset-security-gate.md

@@ -1,135 +0,0 @@
-# LLM Wiki Paperclip Asset And Work-Product Security Gate
-
-Status: accepted Phase 5 policy
-Date: 2026-05-06
-Owner: Security engineering
-Scope: Paperclip-derived ingestion into the LLM Wiki before any asset or work-product content indexing ships
-
-## Decision
-
-Phase 5 remains **fail-closed** for Paperclip assets and work products.
-
-- Paperclip-derived **text extraction is allowed only** for issue titles/descriptions, issue comments, and issue documents.
-- Paperclip **assets/attachments** and **issue work products** are **metadata-only** in Phase 5.
-- **Linked summaries** and **content extraction** for assets/work products are **not approved** in Phase 5.
-- No implementation may fetch `/api/assets/:id/content`, dereference a work-product `url`, scrape preview pages, or embed binary/blob content into source bundles or source snapshots.
-
-This keeps the secure path easier than the insecure one and avoids broadening the wiki into a second content-distribution channel.
-
-## Allowed Source Kinds
-
-These source kinds may contribute body text to Paperclip-derived source bundles:
-
-| Source kind | Allowed body fields | Reason |
-| --- | --- | --- |
-| Issue | `title`, `description`, identifier/status metadata | First-party Paperclip text under company ACL |
-| Comment | `body` | First-party Paperclip text under company ACL |
-| Document | `body`, `title`, `key`, revision metadata | First-party Paperclip text under company ACL |
-
-## Assets And Work Products
-
-### Assets / attachments
-
-Allowed in Phase 5:
-
-- metadata-only references built from allowlisted structured fields already stored in Paperclip
-- recommended fields: `issueId`, `issueCommentId`, `attachmentId`, `assetId`, `originalFilename`, `contentType`, `byteSize`, `sha256`, `createdAt`, `createdByAgentId`, `createdByUserId`
-
-Disallowed in Phase 5:
-
-- fetching asset bytes from `/api/assets/:id/content`
-- parsing any blob body, including `text/plain`, `text/markdown`, `application/json`, images, SVG, PDFs, archives, or office formats
-- storing `contentPath` in wiki source bundles or source snapshots
-- model summarization of attachment bodies
-
-### Work products
-
-Allowed in Phase 5:
-
-- metadata-only references built from allowlisted structured fields already stored in Paperclip
-- recommended fields: `issueId`, `workProductId`, `type`, `provider`, `title`, `status`, `reviewState`, `healthStatus`, `externalId`, `isPrimary`, `createdAt`, `updatedAt`
-- optional boolean/derived metadata such as `hasUrl: true`
-
-Disallowed in Phase 5:
-
-- fetching or crawling the work-product `url`
-- scraping preview pages, artifacts, pull requests, branches, commits, or custom provider targets through the wiki ingestion path
-- storing raw `url` values in wiki source bundles or source snapshots
-- model-authored linked summaries derived from off-record content
-
-## MIME Allowlists And Size Caps
-
-No MIME allowlist is approved for asset content extraction in Phase 5 because **no asset body extraction is approved at all**.
-
-- Every asset MIME type is treated as opaque for Paperclip-derived indexing.
-- Existing upload limits remain storage concerns, not ingestion approvals.
-- Work-product destinations are also opaque regardless of MIME type or size.
-
-Any future issue that wants blob parsing must define:
-
-- a positive MIME allowlist
-- per-type parser strategy
-- per-source size caps
-- sandbox/isolation requirements
-- prompt-injection handling
-- regression tests for refusal paths
-
-## Redaction Rules
-
-Metadata-only means **structured facts only**, not capability-bearing links.
-
-- Do not persist `contentPath` for assets.
-- Do not persist raw work-product `url` values.
-- Do not persist query strings, fragments, signed URL tokens, or userinfo.
-- Prefer stable identifiers (`assetId`, `workProductId`, `externalId`) over links.
-
-This addresses Sensitive Information Disclosure, Unsafe Consumption of APIs, and Insecure Output Handling risks.
-
-## Provenance Rules
-
-Every metadata-only reference must preserve enough provenance to explain where it came from without reading the underlying content:
-
-- `companyId`
-- `issueId`
-- attachment/work-product id
-- producer identity when available
-- timestamps
-- an explicit `metadata_only` marker in any future reference/snapshot schema
-
-## Review-Required Behavior
-
-Human review is **not** required for plain metadata-only references that stay inside the allowlisted fields above.
-
-Human review **is required**, with a separate security sign-off issue, before enabling any of the following:
-
-- asset body extraction
-- work-product URL fetching
-- linked summaries generated from asset/work-product content
-- storing raw blob links or raw remote URLs in wiki source material
-- non-default-space routing for Paperclip-derived asset/work-product references
-
-## Security Rationale
-
-This gate exists because the current host surfaces have different trust properties:
-
-- issue/comment/document text is first-party Paperclip content already exposed through company-scoped issue/document APIs
-- asset content is a blob download surface (`/api/assets/:id/content`) and can carry prompt-injection or parser-risk payloads
-- work products can point at arbitrary destinations through `url`, which reintroduces SSRF, token leakage, and prompt-injection risk if dereferenced automatically
-
-Relevant threat classes:
-
-- OWASP LLM Top 10: Prompt Injection, Sensitive Information Disclosure, Insecure Output Handling, Excessive Agency
-- OWASP API Top 10: SSRF, Unsafe Consumption of APIs, Broken Object Property Level Authorization
-- Saltzer & Schroeder: Least Privilege, Fail Securely, Complete Mediation, Secure Defaults
-
-## Follow-Up Implementation Scope
-
-A follow-up implementation issue is justified only for **metadata-only references**.
-
-That implementation must:
-
-- keep assets/work products out of source-bundle body text
-- never fetch blob bytes or remote URLs
-- redact capability-bearing link fields
-- mark references as `metadata_only`
-- ship tests proving source bundles/snapshots never contain `contentPath` or raw work-product `url` fields

doc/plans/2026-05-26-skills-cli-catalog-contract.md

@@ -1,486 +0,0 @@
-# Skills CLI And Catalog Contract
-
-Status: Phase A engineering contract
-Date: 2026-05-26
-Source plan: approved Paperclip skills CLI and catalog plan
-
-This document freezes the first implementation contract for the `paperclipai skills`
-command group and the app-shipped skills catalog. It is intentionally a build
-contract, not a full product spec.
-
-## Decisions
-
-- `paperclipai skills` manages Paperclip company skills. It does not manage
-  local adapter homes directly.
-- Installing a skill means adding or updating a company-scoped
-  `company_skills` record.
-- Attaching a skill to an agent is a separate agent desired-state operation.
-- Adapter runtime sync is a third step handled through adapter skill APIs.
-- Root `skills/` remains reserved for Paperclip runtime and operational skills.
-- App-shipped catalog skills live in `packages/skills-catalog`, not root
-  `skills/`.
-- Catalog skills are inspectable before install. Inspection never mutates company
-  state.
-- External sources continue to use the existing company skill import API in the
-  first release. No separate marketplace, tap, or source registry is part of this
-  phase.
-- Agent desired skills continue to live in
-  `adapterConfig.paperclipSkillSync.desiredSkills` for the first release. Do not
-  add a normalized `agent_skills` table unless later implementation evidence
-  requires it.
-
-## Terms
-
-- Company skill: a row in `company_skills`, owned by one company.
-- Catalog skill: an app-shipped skill entry in `@paperclipai/skills-catalog`.
-- Skill ref: a user-supplied company skill reference. The CLI accepts company
-  skill `id`, canonical `key`, or unique `slug`.
-- Catalog ref: a user-supplied catalog reference. The CLI accepts catalog `id`,
-  canonical `key`, or unique `slug`.
-- Desired skills: the skill key set stored on the agent adapter config.
-- Runtime snapshot: the adapter-reported `AgentSkillSnapshot` for desired,
-  installed, missing, stale, external, required, or unsupported skills.
-
-## CLI Contract
-
-All skills commands use the existing client command stack:
-
-- Global client options: `--data-dir`, `--config`, `--context`, `--profile`,
-  `--api-base`, `--api-key`, and `--json`.
-- Company-scoped commands also accept `-C, --company-id <id>` and otherwise use
-  `PAPERCLIP_COMPANY_ID` or the active context profile.
-- Human output goes to stdout. Errors go to stderr.
-- `--json` prints pretty JSON and no decorative labels.
-- Successful commands exit `0`. Validation, API, or conflict errors exit `1`.
-- API errors use the existing `API error <status>: <message>` formatting.
-- Mutating commands print a short summary in human mode and the raw result in
-  JSON mode.
-- Commands that can delete or clear state must prompt in a TTY. In non-TTY mode
-  they must require `--yes`.
-
-### Company Skill Commands
-
-These commands are Phase B and must work over existing APIs.
-
-| Command | Behavior | JSON output |
-|---|---|---|
-| `skills list` | Lists company skills from `GET /api/companies/:companyId/skills`. Human rows include `id`, `key`, `slug`, `name`, `source`, `trust`, `compatibility`, and `attachedAgents`. | `CompanySkillListItem[]` |
-| `skills show <skill-ref>` | Resolves `id`, `key`, or unique `slug`, then reads detail. Ambiguous slugs are conflicts. | `CompanySkillDetail` |
-| `skills file <skill-ref> [--path <path>]` | Resolves the skill, reads a file with default `SKILL.md`, and prints raw file content in human mode. This command must remain pipeable. | `CompanySkillFileDetail` |
-| `skills import <source>` | Calls existing import API. Source may be a local path, GitHub URL, skills.sh URL or command, `owner/repo`, `owner/repo/skill`, or URL-like source already accepted by the server. | `CompanySkillImportResult` |
-| `skills create --name <name> [--slug <slug>] [--description <text>] [--body-file <path|->]` | Creates a managed local company skill. If `--body-file` is omitted, the server default body is used. `-` reads markdown from stdin. | `CompanySkill` |
-| `skills scan-projects [--project-id <id>...] [--workspace-id <id>...]` | Calls project scan. Repeated flags become arrays. With neither flag, scan all accessible project workspaces. | `CompanySkillProjectScanResult` |
-| `skills check [skill-ref]` | Reads update status for one skill, or for every listed company skill when no ref is provided. Unsupported statuses are shown, not hidden. | `CompanySkillCheckRow[]` |
-| `skills update <skill-ref>` | Installs the update for one skill through the existing install-update API. | `CompanySkillUpdateRow` |
-| `skills update --all` | Checks all skills, installs only those with `hasUpdate=true`, and reports skipped unsupported or current skills. | `CompanySkillUpdateRow[]` |
-| `skills remove <skill-ref> [--yes]` | Deletes one company skill after confirmation. | `CompanySkill` |
-
-`CompanySkillCheckRow` is a CLI-side shape:
-
-```ts
-interface CompanySkillCheckRow {
-  skill: Pick<CompanySkillListItem, "id" | "key" | "slug" | "name">;
-  status: CompanySkillUpdateStatus;
-}
-```
-
-`CompanySkillUpdateRow` is a CLI-side shape:
-
-```ts
-interface CompanySkillUpdateRow {
-  skillRef: string;
-  action: "updated" | "skipped" | "failed";
-  skill?: CompanySkill;
-  status?: CompanySkillUpdateStatus;
-  reason?: string;
-}
-```
-
-### Agent Skill Commands
-
-These commands are Phase B and use existing agent skill APIs.
-
-| Command | Behavior | JSON output |
-|---|---|---|
-| `skills agent list <agent-ref>` | Resolves the agent using existing agent reference behavior, then prints the adapter `AgentSkillSnapshot`. Human rows include `key`, `runtimeName`, `desired`, `managed`, `required`, `state`, `origin`, and `detail`. | `AgentSkillSnapshot` |
-| `skills agent sync <agent-ref> --skill <skill-ref>...` | Replaces the agent's non-required desired skill set with the supplied refs and triggers adapter sync. Required Paperclip skills remain enforced by the server. | `AgentSkillSnapshot` |
-| `skills agent clear <agent-ref> [--yes]` | Clears non-required desired skills by sending an empty desired list, then returns the adapter snapshot. | `AgentSkillSnapshot` |
-
-The word `sync` is deliberate: it is a desired-state replacement, not an append.
-An additive command can be added later if operators need it.
-
-### Catalog CLI Commands
-
-These commands are Phase E and depend on the catalog APIs from Phase D.
-
-| Command | Behavior | JSON output |
-|---|---|---|
-| `skills browse [--kind bundled|optional] [--category <slug>] [--query <text>]` | Lists app-shipped catalog skills. Human rows include `id`, `key`, `kind`, `category`, `slug`, `name`, `trust`, and `recommendedForRoles`. | `CatalogSkillListItem[]` |
-| `skills search <query> [--kind bundled|optional] [--category <slug>]` | Alias for catalog browse with `query`. | `CatalogSkillListItem[]` |
-| `skills inspect <catalog-ref>` | Shows app-shipped catalog detail and file inventory. Does not mutate company state. | `CatalogSkillDetail` |
-| `skills install <catalog-ref> [--as <slug>] [--force]` | Installs a catalog skill into a company library. `--as` overrides the company skill slug. `--force` may replace a same-key catalog skill but must not bypass hard validation or dangerous security findings. | `CompanySkillInstallCatalogResult` |
-
-Catalog commands are for the app-shipped Paperclip catalog only. External GitHub,
-skills.sh, local path, and URL installs remain under `skills import <source>` in
-the first release.
-
-## Catalog Package Contract
-
-Add a workspace package:
-
-```text
-packages/skills-catalog/
-  package.json
-  tsconfig.json
-  src/
-    index.ts
-    types.ts
-  catalog/
-    bundled/
-      <category>/
-        <slug>/
-          SKILL.md
-          references/
-          scripts/
-          assets/
-    optional/
-      <category>/
-        <slug>/
-          SKILL.md
-          references/
-          scripts/
-          assets/
-  generated/
-    catalog.json
-  scripts/
-    build-catalog-manifest.ts
-    validate-catalog.ts
-```
-
-Package name: `@paperclipai/skills-catalog`.
-
-The package exports:
-
-- `catalogManifest`
-- `catalogSkills`
-- `resolveCatalogSkillRef(ref)`
-- `getCatalogSkill(id)`
-- TypeScript types for every manifest shape
-
-Server and CLI code must import the generated manifest. They must not crawl
-arbitrary repository paths at request time.
-
-## Catalog Manifest
-
-The generated artifact is `packages/skills-catalog/generated/catalog.json`.
-It is checked in and regenerated by the package build or validation script.
-
-```ts
-interface CatalogManifest {
-  schemaVersion: 1;
-  packageName: "@paperclipai/skills-catalog";
-  packageVersion: string;
-  generatedAt: string;
-  skills: CatalogSkill[];
-}
-
-interface CatalogSkill {
-  id: string;
-  key: string;
-  kind: "bundled" | "optional";
-  category: string;
-  slug: string;
-  name: string;
-  description: string;
-  path: string;
-  entrypoint: "SKILL.md";
-  trustLevel: "markdown_only" | "assets" | "scripts_executables";
-  compatibility: "compatible" | "unknown" | "invalid";
-  defaultInstall: boolean;
-  recommendedForRoles: string[];
-  requires: string[];
-  tags: string[];
-  files: CatalogSkillFile[];
-  contentHash: string;
-}
-
-interface CatalogSkillFile {
-  path: string;
-  kind: "skill" | "markdown" | "reference" | "script" | "asset" | "other";
-  sizeBytes: number;
-  sha256: string;
-}
-```
-
-`id` is path-safe:
-
-```text
-paperclipai:<kind>:<category>:<slug>
-```
-
-`key` is the canonical company skill key installed into `company_skills`:
-
-```text
-paperclipai/<kind>/<category>/<slug>
-```
-
-Example:
-
-```json
-{
-  "id": "paperclipai:bundled:software-development:github-pr-workflow",
-  "key": "paperclipai/bundled/software-development/github-pr-workflow",
-  "kind": "bundled",
-  "category": "software-development",
-  "slug": "github-pr-workflow",
-  "name": "github-pr-workflow",
-  "description": "Prepare pull requests, review responses, and verification notes.",
-  "path": "catalog/bundled/software-development/github-pr-workflow",
-  "entrypoint": "SKILL.md",
-  "trustLevel": "markdown_only",
-  "compatibility": "compatible",
-  "defaultInstall": false,
-  "recommendedForRoles": ["engineer"],
-  "requires": [],
-  "tags": ["github", "pull-requests"],
-  "files": [
-    {
-      "path": "SKILL.md",
-      "kind": "skill",
-      "sizeBytes": 1200,
-      "sha256": "..."
-    }
-  ],
-  "contentHash": "sha256:..."
-}
-```
-
-## Catalog Skill Frontmatter
-
-Each catalog `SKILL.md` must include:
-
-```yaml
----
-name: github-pr-workflow
-description: Prepare pull requests, review responses, and verification notes.
-key: paperclipai/bundled/software-development/github-pr-workflow
-recommendedForRoles:
-  - engineer
-tags:
-  - github
-  - pull-requests
----
-```
-
-Optional frontmatter:
-
-- `slug`
-- `defaultInstall`
-- `requires`
-- `metadata`
-
-The manifest generator owns `kind`, `category`, `path`, `files`,
-`trustLevel`, `compatibility`, and `contentHash`.
-
-## Catalog Validation Rules
-
-Validation must fail when:
-
-- A catalog entry is not under `catalog/bundled/<category>/<slug>` or
-  `catalog/optional/<category>/<slug>`.
-- `SKILL.md` is missing.
-- `category` or `slug` is not a lowercase URL slug.
-- `name` or `description` frontmatter is missing or empty.
-- The frontmatter `key`, when present, does not equal the generated key.
-- Two catalog entries have the same `id`, `key`, or `slug`.
-- File inventory includes absolute paths, `..` segments, broken symlinks, or
-  files outside the skill directory.
-- A file exceeds the package-level size limit chosen by implementation.
-- A skill marked `compatible` cannot be parsed as Agent Skills markdown.
-- The generated manifest differs from the checked-in
-  `generated/catalog.json`.
-
-Trust level is derived from inventory:
-
-- `scripts_executables` when any file is classified as `script`.
-- `assets` when any file is classified as `asset` or `other` and no script is
-  present.
-- `markdown_only` when all files are markdown, references, or `SKILL.md`.
-
-Validation must report all discovered catalog errors when practical, not just
-the first one.
-
-## Catalog API Contract
-
-Phase D adds read APIs and one company install API.
-
-```text
-GET  /api/skills/catalog
-GET  /api/skills/catalog/:catalogId
-GET  /api/skills/catalog/:catalogId/files?path=SKILL.md
-POST /api/companies/:companyId/skills/install-catalog
-```
-
-`GET /api/skills/catalog` accepts:
-
-- `kind=bundled|optional`
-- `category=<slug>`
-- `q=<text>`
-
-`catalogId` is the path-safe manifest `id`. The server should also support
-resolution by `key` or unique `slug` where the ref is carried in a query or body,
-but route parameters use `id` to avoid slash handling ambiguity.
-
-Install request:
-
-```ts
-interface CompanySkillInstallCatalogRequest {
-  catalogSkillId: string;
-  slug?: string | null;
-  force?: boolean;
-}
-```
-
-Install result:
-
-```ts
-interface CompanySkillInstallCatalogResult {
-  action: "created" | "updated" | "unchanged";
-  skill: CompanySkill;
-  catalogSkill: CatalogSkill;
-  warnings: string[];
-}
-```
-
-Install behavior:
-
-- Creates or updates a company skill with `sourceType="catalog"`.
-- Uses catalog `key` as the company skill canonical key.
-- Uses catalog `slug` unless `slug` is provided.
-- Materializes the catalog files into a company-managed skill directory so
-  existing skill file reads continue to work.
-- Stores provenance in metadata:
-  - `catalogId`
-  - `catalogKey`
-  - `catalogKind`
-  - `catalogCategory`
-  - `catalogPath`
-  - `packageName`
-  - `packageVersion`
-  - `originHash`
-  - `originVersion`
-  - `userModifiedAt`
-  - `updateHoldReason`
-- Writes activity log entries for install and update.
-- Returns `409` for duplicate slug/key conflicts that cannot be resolved safely.
-- Returns `422` for invalid, incompatible, or hard-blocked catalog entries.
-- `force` may replace a same-key catalog-managed skill. It must not bypass
-  company boundaries, permission checks, hard validation, or hard security
-  findings.
-
-## Error Semantics
-
-Use existing HTTP semantics:
-
-- `400`: invalid CLI arguments, invalid query/body shape, or malformed refs.
-- `401`: missing or invalid auth.
-- `403`: authenticated principal lacks access or mutation permission.
-- `404`: skill, catalog entry, agent, file, company, or source not found.
-- `409`: ambiguous slug, duplicate key/slug, update conflict, or unsafe overwrite.
-- `422`: semantic violation such as invalid skill content or unsupported source.
-- `500`: unexpected server failure.
-
-CLI messages should name the next useful correction, for example:
-
-- `Skill slug "review" is ambiguous. Use an id or key.`
-- `Company ID is required. Pass --company-id, set PAPERCLIP_COMPANY_ID, or set a context profile.`
-- `Catalog skill contains executable scripts and cannot be force-installed until security review semantics allow it.`
-
-## Phase Acceptance Criteria
-
-Phase A is complete when this contract is available in the repo and the issue
-thread links it.
-
-Phase B, CLI MVP:
-
-- `paperclipai skills --help` exposes the Phase B command group.
-- All Phase B commands work against existing company skills and agent skills
-  APIs without schema or server changes.
-- Skill refs resolve by id, key, or unique slug.
-- Human and JSON output are covered by focused CLI tests.
-- `doc/CLI.md` documents company install vs agent desired sync vs runtime sync.
-
-Phase C, catalog package:
-
-- `packages/skills-catalog` is a workspace package.
-- Build or validation regenerates `generated/catalog.json`.
-- Validation covers frontmatter, id/key/slug uniqueness, directory shape, file
-  inventory, trust derivation, and stale generated output.
-- Server and CLI can import the manifest without crawling arbitrary paths.
-- Root `skills/` is not expanded with the app-shipped catalog.
-
-Phase D, catalog APIs:
-
-- Catalog list/detail/file APIs are read-only and covered by tests.
-- Install-from-catalog creates auditable company-scoped skill records with
-  provenance metadata and materialized files.
-- Company boundary and mutation permission checks match or exceed existing
-  company skill mutations.
-- Duplicate and unsafe overwrite behavior is explicit and tested.
-
-Phase E, catalog CLI:
-
-- Operators can browse, search, inspect, and install app-shipped catalog skills.
-- External source behavior remains routed through `skills import`.
-- Output and errors follow the Phase B CLI conventions.
-- Catalog install is clearly distinct from agent attach/sync in help and docs.
-
-Phase F, update/reset/audit:
-
-- Security review records decisions for origin hash, user modification detection,
-  reset, audit findings, and force behavior.
-- Implementation follows the review or records explicit deferrals.
-- Mutating reset/update actions are activity logged.
-- Tests cover dangerous findings, force behavior, and unchanged/current states.
-
-Phase G, adapter truth model:
-
-- Adapter snapshots accurately report `unsupported`, `persistent`, or
-  `ephemeral`.
-- Desired, missing, installed, stale, external, and required states are tested.
-- External adapter plugins remain dynamically loaded. No hardcoded plugin imports
-  are added.
-
-Phase H, UI:
-
-- The existing Company Skills page is extended rather than replaced.
-- UX guidance covers Company, Bundled, Optional, and External source views.
-- Install preview shows source, trust, provenance, update state, and file
-  inventory.
-- Agent attach/detach states are clear.
-- Frontend handoff includes screenshots or equivalent browser evidence.
-
-Phase I, initial skill content:
-
-- Bundled and optional entries use the finalized frontmatter and category rules.
-- Skill descriptions are specific enough for browse/search.
-- No script-bearing skill lands without explicit security review evidence.
-- Validation fixtures or tests cover representative content.
-
-Phase J, QA and docs:
-
-- QA validates CLI, catalog APIs, UI install, agent sync, portability, and adapter
-  snapshots against a dev instance.
-- Blocking defects are linked as first-class issues.
-- `doc/CLI.md`, `doc/DEVELOPING.md`, and skill workflow docs match shipped
-  behavior.
-
-## Deferrals
-
-- No cloud marketplace.
-- No user-home tap registry.
-- No hidden curator or autonomous catalog mutator.
-- No normalized `agent_skills` table in the first release.
-- No skill sets or bundles in the first release.
-- No automatic install of every optional catalog skill.
-- No replacement of company import/export as the portability path.

doc/plugins/LOCAL_PLUGIN_DEVELOPMENT.md

@@ -1,142 +0,0 @@
-# Local Plugin Development
-
-This is the short happy-path guide for developing a Paperclip plugin from a folder on your machine. You will scaffold a plugin, run it in watch mode, install it into a running Paperclip instance from an absolute local path, and edit code with the plugin worker reloading after each rebuild.
-
-For the full alpha surface — manifest fields, capabilities, managed agents/projects/routines/skills, UI slots, scoped API routes — see [`PLUGIN_AUTHORING_GUIDE.md`](./PLUGIN_AUTHORING_GUIDE.md).
-
-If your plugin has background-like recurring work, model it as managed resources:
-declare managed routines plus managed agents/projects/skills, then reconcile those
-resources in worker actions. This gives operators visible work items, budgets,
-pause controls, and consistent audits instead of hidden daemon behavior.
-
-## Prerequisites
-
-- Node.js 22+ and `pnpm`.
-- A local Paperclip checkout you can run from source. Local plugin installs read source from disk, so the running server must be able to see the path you give it.
-
-## The five steps
-
-```bash
-# 1. Start Paperclip locally
-pnpm paperclipai run
-
-# 2. Scaffold a plugin outside the Paperclip repo
-paperclipai plugin init @acme/hello-plugin --output ~/dev/paperclip-plugins
-
-# 3. Install dependencies and start the watch build
-cd ~/dev/paperclip-plugins/hello-plugin
-pnpm install
-pnpm dev
-
-# 4. In another terminal, install the plugin from its absolute path
-paperclipai plugin install ~/dev/paperclip-plugins/hello-plugin
-
-# 5. Confirm it loaded
-paperclipai plugin list
-paperclipai plugin inspect acme.hello-plugin
-```
-
-That's the loop. The rest of this page explains what each step does and what to expect when you edit code.
-
-### 1. Start Paperclip
-
-```bash
-pnpm paperclipai run
-```
-
-Paperclip listens on `http://127.0.0.1:3100` by default. The CLI talks to that server, so leave it running.
-
-### 2. Scaffold the plugin
-
-```bash
-paperclipai plugin init @acme/hello-plugin --output ~/dev/paperclip-plugins
-```
-
-This creates `~/dev/paperclip-plugins/hello-plugin/` with `src/manifest.ts`, `src/worker.ts`, `src/ui/index.tsx`, an esbuild watch config, a Vitest config, and a snapshot of `@paperclipai/plugin-sdk` from your local Paperclip checkout. You can run the package and tests without publishing anything to npm.
-
-Useful flags:
-
-- `--template <default|connector|workspace|environment>` — starter shape.
-- `--category <connector|workspace|automation|ui|environment>` — manifest category.
-- `--display-name`, `--description`, `--author` — manifest metadata.
-- `--sdk-path <absolute-path>` — point at a specific `packages/plugins/sdk` checkout if you have more than one.
-
-When `plugin init` finishes, it prints the next four commands literally. You can copy them.
-
-### 3. Install dependencies and run the watch build
-
-```bash
-cd ~/dev/paperclip-plugins/hello-plugin
-pnpm install
-pnpm dev
-```
-
-`pnpm dev` runs `esbuild --watch` against the plugin source and emits `dist/manifest.js`, `dist/worker.js`, and `dist/ui/`. Leave it running. Every time you save, esbuild rebuilds the affected output file.
-
-If your plugin has UI and you want a browser-side dev server with hot module replacement during local UI iteration, run `pnpm dev:ui` in a second terminal. It serves `dist/ui/` on `http://127.0.0.1:4177`. This is optional; Paperclip can load the built UI directly from `dist/ui/` without it.
-
-### 4. Install from the absolute path
-
-```bash
-paperclipai plugin install ~/dev/paperclip-plugins/hello-plugin
-```
-
-The CLI auto-detects local paths (anything that looks absolute, starts with `./`, `../`, or `~`, or resolves to an existing folder relative to the current directory) and sends `{ isLocalPath: true }` to `POST /api/plugins/install` with the resolved absolute path. If you want to be explicit, pass `--local`.
-
-You will see a confirmation like:
-
-```
-Installing plugin from local path: /Users/you/dev/paperclip-plugins/hello-plugin
-✓ Installed acme.hello-plugin v0.1.0 (ready)
-Local plugin installs run trusted local code from your machine.
-Keep `pnpm dev` running in /Users/you/dev/paperclip-plugins/hello-plugin;
-Paperclip watches rebuilt dist output and reloads the plugin worker.
-```
-
-Relative paths are resolved against the current working directory, so `paperclipai plugin install .` from inside the plugin folder works too.
-
-### 5. Inspect
-
-```bash
-paperclipai plugin list
-paperclipai plugin inspect acme.hello-plugin
-```
-
-`list` shows plugin key, status, version, and short error. `inspect` prints the same record with the full last error if there is one. Both accept `--json` if you want to script against them.
-
-## Reload semantics, honestly
-
-Paperclip watches the on-disk plugin package after a local install. The watcher targets the runtime entrypoints declared in the package's `paperclipPlugin` field (`dist/manifest.js`, `dist/worker.js`, `dist/ui/`).
-
-What that means in practice:
-
-- **Worker code:** save a `.ts` file → esbuild rewrites `dist/worker.js` → Paperclip debounces ~500ms and restarts the plugin worker. The next worker call uses the new code. There is no in-process hot module replacement for worker code; it is a worker restart.
-- **Manifest:** save `src/manifest.ts` → `dist/manifest.js` rewrites → the worker restarts and the host re-reads the manifest.
-- **Plugin UI:** save a `.tsx` file → esbuild rewrites `dist/ui/` → Paperclip reloads the UI bundle on its next mount. To get HMR during UI iteration, run `pnpm dev:ui` and point at the dev server with `devUiUrl` in your manifest while developing.
-- **Without `pnpm dev`:** the watcher only fires on `dist/*` changes. If you stop the watch build, source edits do not reach Paperclip. Restart `pnpm dev` (or run `pnpm build` once) before expecting changes.
-- **`node_modules`, `.git`, `.paperclip-sdk`, and other dotfolders are ignored.** Adding a dependency requires the new code to actually be imported and rebuilt before the worker sees it.
-
-The server never compiles plugin source for you. The package's own build scripts own that step.
-
-## Local path plugins vs npm packages
-
-Both go through the same install endpoint, but they mean different things:
-
-- **Local path plugins are trusted local code.** Paperclip executes worker code from disk under the same trust boundary as the rest of the running instance. This is meant for developing or operating a plugin against a checkout you control. There is no signature check, no sandboxing of worker code, and no provenance metadata beyond the path. Do not install local-path plugins you did not write.
-- **npm packages are the deployable artifact.** `paperclipai plugin install @acme/plugin-foo` (optionally `--version 1.2.3`) installs from your configured npm registry, version-pins, and produces an install record that other operators can reproduce. Ship plugins this way.
-
-When you are done iterating locally, publish the package and reinstall the npm-package form so the install reflects what you will ship.
-
-## Common things to do next
-
-- **Restart cleanly:** `paperclipai plugin disable <key>` pauses the plugin without removing it. `paperclipai plugin enable <key>` brings it back. `paperclipai plugin uninstall <key>` removes the install record; add `--force` to also purge plugin state and settings.
-- **Browse examples:** `paperclipai plugin examples` lists the bundled example plugins that ship with the repo, each with a ready-to-run `paperclipai plugin install <path>` line.
-- **Go deeper:** [`PLUGIN_AUTHORING_GUIDE.md`](./PLUGIN_AUTHORING_GUIDE.md) covers worker capabilities, managed agents/projects/routines/skills, plugin database namespaces, scoped API routes, and the shared UI components in `@paperclipai/plugin-sdk/ui`. [`PLUGIN_SPEC.md`](./PLUGIN_SPEC.md) is the longer-form specification, including future ideas that are not yet implemented.
-- **Routine-first automation:** If your plugin should produce periodic issue work, prefer managed routines and `ctx.routines.managed` reconciliation over custom process loops or unobserved cron code.
-
-## Troubleshooting
-
-- **`Plugin install returned no plugin record` or `error` status.** Run `paperclipai plugin inspect <key>` for the last error. The most common causes are (1) the plugin has not built yet — run `pnpm dev` or `pnpm build` first, (2) the `paperclipPlugin` entries in `package.json` point at files that do not exist on disk, or (3) the manifest failed validation. The Paperclip server log has the full validation error.
-- **Edits do not seem to reload.** Confirm `pnpm dev` is still running and writing to `dist/`. If you renamed entry files, update the `paperclipPlugin.manifest` / `paperclipPlugin.worker` / `paperclipPlugin.ui` fields in `package.json` so the watcher targets them.
-- **Worker restarts but UI is stale.** Hard-reload the page. If you want HMR, run `pnpm dev:ui` and set `devUiUrl` in your manifest to `http://127.0.0.1:4177` during development.
-- **Path arguments fail on Windows.** Quote paths that contain spaces, and prefer absolute paths over `~`-prefixed paths in non-bash shells.

doc/plugins/PLUGIN_AUTHORING_GUIDE.md

@@ -4,33 +4,34 @@ This guide describes the current, implemented way to create a Paperclip plugin i
 
 It is intentionally narrower than [PLUGIN_SPEC.md](./PLUGIN_SPEC.md). The spec includes future ideas; this guide only covers the alpha surface that exists now.
 
-> **New to plugins?** Start with the short [Local Plugin Development guide](./LOCAL_PLUGIN_DEVELOPMENT.md) — it walks the CLI happy path (`plugin init` → `pnpm dev` → `plugin install <path>`) end to end. Come back here for the full manifest surface, worker capabilities, and UI components.
-
 ## Current reality
 
 - Treat plugin workers and plugin UI as trusted code.
 - Plugin UI runs as same-origin JavaScript inside the main Paperclip app.
 - Worker-side host APIs are capability-gated.
 - Plugin UI is not sandboxed by manifest capabilities.
-- Plugin database migrations are restricted to a host-derived plugin namespace.
-- Plugin-managed surfaces are first-class records (agents, projects, routines, and
-  skills) rather than private plugin-only state.
-- Plugin-owned JSON API routes must be declared in the manifest and are mounted
-  only under `/api/plugins/:pluginId/api/*`.
-- The host provides a small shared React component kit through
-  `@paperclipai/plugin-sdk/ui`; use it for common Paperclip controls before
-  building custom versions.
+- There is no host-provided shared React component kit for plugins yet.
 - `ctx.assets` is not supported in the current runtime.
 
 ## Scaffold a plugin
 
-Use the CLI scaffold command:
+Use the scaffold package:
 
 ```bash
-paperclipai plugin init @yourscope/plugin-name --output /absolute/path/to/plugin-repos
+pnpm --filter @paperclipai/create-paperclip-plugin build
+node packages/plugins/create-paperclip-plugin/dist/index.js @yourscope/plugin-name --output ./packages/plugins/examples
 ```
 
-That creates `<output>/plugin-name/` with:
+For a plugin that lives outside the Paperclip repo:
+
+```bash
+pnpm --filter @paperclipai/create-paperclip-plugin build
+node packages/plugins/create-paperclip-plugin/dist/index.js @yourscope/plugin-name \
+  --output /absolute/path/to/plugin-repos \
+  --sdk-path /absolute/path/to/paperclip/packages/plugins/sdk
+```
+
+That creates a package with:
 
 - `src/manifest.ts`
 - `src/worker.ts`
@@ -41,13 +42,11 @@ That creates `<output>/plugin-name/` with:
 
 Inside this monorepo, the scaffold uses `workspace:*` for `@paperclipai/plugin-sdk`.
 
-Outside this monorepo, the scaffold snapshots `@paperclipai/plugin-sdk` from the local Paperclip checkout into a `.paperclip-sdk/` tarball so you can build and test a plugin without publishing anything to npm first. Pass `--sdk-path /absolute/path/to/paperclip/packages/plugins/sdk` if you have more than one Paperclip checkout.
+Outside this monorepo, the scaffold snapshots `@paperclipai/plugin-sdk` from the local Paperclip checkout into a `.paperclip-sdk/` tarball so you can build and test a plugin without publishing anything to npm first.
 
-## Local development workflow
+## Recommended local workflow
 
-See the short [Local Plugin Development guide](./LOCAL_PLUGIN_DEVELOPMENT.md) for the full happy path (`pnpm dev` → `paperclipai plugin install <absolute-path>` → `paperclipai plugin list`) and reload semantics.
-
-Minimum verification from the generated plugin folder:
+From the generated plugin folder:
 
 ```bash
 pnpm install
@@ -56,6 +55,16 @@ pnpm test
 pnpm build
 ```
 
+For local development, install it into Paperclip from an absolute local path through the plugin manager or API. The server supports local filesystem installs and watches local-path plugins for file changes so worker restarts happen automatically after rebuilds.
+
+Example:
+
+```bash
+curl -X POST http://127.0.0.1:3100/api/plugins/install \
+  -H "Content-Type: application/json" \
+  -d '{"packageName":"/absolute/path/to/your-plugin","isLocalPath":true}'
+```
+
 ## Supported alpha surface
 
 Worker:
@@ -68,15 +77,11 @@ Worker:
 - secrets
 - activity
 - state
-- database namespace via `ctx.db`
-- scoped JSON API routes declared with `apiRoutes`
 - entities
-- projects, project workspaces, and plugin-managed projects
+- projects and project workspaces
 - companies
-- issues, comments, namespaced `plugin:<pluginKey>` origins, blocker relations, checkout assertions, assignment wakeups, and orchestration summaries
-- agents, plugin-managed agents, and agent sessions
-- plugin-managed routines
-- plugin-managed skills
+- issues and comments
+- agents and agent sessions
 - goals
 - data/actions
 - streams
@@ -84,232 +89,6 @@ Worker:
 - metrics
 - logger
 
-### Plugin database declarations
-
-First-party or otherwise trusted orchestration plugins can declare:
-
-```ts
-database: {
-  migrationsDir: "migrations",
-  coreReadTables: ["issues"],
-}
-```
-
-Required capabilities are `database.namespace.migrate` and
-`database.namespace.read`; add `database.namespace.write` for runtime mutations.
-The host derives `ctx.db.namespace`, runs SQL files in filename order before the
-worker starts, records checksums in `plugin_migrations`, and rejects changed
-already-applied migrations.
-
-Migration SQL may create or alter objects only inside `ctx.db.namespace`. It may
-reference whitelisted `public` core tables for foreign keys or read-only views,
-but may not mutate/alter/drop/truncate public tables, create extensions,
-triggers, untrusted languages, or runtime multi-statement SQL. Runtime
-`ctx.db.query()` is restricted to `SELECT`; runtime `ctx.db.execute()` is
-restricted to namespace-local `INSERT`, `UPDATE`, and `DELETE`.
-
-### Scoped plugin API routes
-
-Plugins can expose JSON-only routes under their own namespace:
-
-```ts
-apiRoutes: [
-  {
-    routeKey: "initialize",
-    method: "POST",
-    path: "/issues/:issueId/smoke",
-    auth: "board-or-agent",
-    capability: "api.routes.register",
-    checkoutPolicy: "required-for-agent-in-progress",
-    companyResolution: { from: "issue", param: "issueId" },
-  },
-]
-```
-
-The host resolves the plugin, checks that it is ready, enforces
-`api.routes.register`, matches the declared method/path, resolves company access,
-and applies checkout policy before dispatching to the worker's `onApiRequest`
-handler. The worker receives sanitized headers, route params, query, parsed JSON
-body, actor context, and company id. Do not use plugin routes to claim core
-paths; they always remain under `/api/plugins/:pluginId/api/*`.
-
-## Managed Paperclip resources
-
-Plugins that provide durable Paperclip business objects should declare them in
-the manifest and let the host create or relink the actual records per company.
-Do this for plugin-owned agents, projects, routines, and skills.
-Do not hide long-lived work behind private plugin state when it should be visible
-to the board, scoped to a company, audited, budgeted, and assigned like normal
-Paperclip work.
-
-Content-oriented plugins, such as LLM Wiki-style ingestion or durable knowledge
-systems, should use the same pattern: managed projects for operation issues,
-managed agents plus managed skills for LLM work, and managed routines for
-ingest, lint, refresh, or maintenance runs.
-
-Use these surfaces:
-
-- Managed agents: declare top-level `agents[]` and require
-  `agents.managed`. Use this when the plugin provides a named worker the board
-  should see in the org, budget, pause, invoke, and inspect. Managed agents are
-  normal Paperclip agents with plugin ownership metadata, not background plugin
-  workers.
-- Managed projects: declare top-level `projects[]` and require
-  `projects.managed`. Use this when the plugin needs a stable company-scoped
-  project for its issues, routines, or workspace-oriented UI. Keep plugin work
-  in a project instead of scattering generated issues across unrelated projects.
-- Managed routines: declare top-level `routines[]` and require
-  `routines.managed`. Use this for scheduled, webhook, or manually triggered
-  jobs that should create visible Paperclip issues. Prefer managed routines over
-  plugin `jobs[]` for recurring business work; plugin jobs are for plugin
-  runtime maintenance that does not need a board-visible task trail.
-- Managed skills: declare top-level `skills[]` and require `skills.managed`.
-  Use this for reusable plugin capabilities that should be surfaced to operators and
-  synced into Paperclip managed agents.
-
-Managed resources are resolved by stable plugin keys, not hardcoded database
-ids. In a worker action or data handler, call `ctx.agents.managed.reconcile()`,
-`ctx.projects.managed.reconcile()`, `ctx.routines.managed.reconcile()`, and
-`ctx.skills.managed.reconcile()` for
-the current `companyId`. `reconcile()` creates the missing resource, relinks a
-recoverable binding, or returns the existing resource. `reset()` reapplies the
-manifest defaults when the operator wants to restore the plugin's suggested
-configuration.
-
-Declare dependencies between managed resources with refs. A routine can point
-at a managed agent through `assigneeRef` and at a managed project through
-`projectRef`. Reconcile the referenced agent and project before reconciling the
-routine; if a ref is still missing, the routine resolution reports
-`missing_refs` instead of guessing.
-
-```ts
-import type { PaperclipPluginManifestV1 } from "@paperclipai/plugin-sdk";
-
-const manifest: PaperclipPluginManifestV1 = {
-  id: "example.research-plugin",
-  apiVersion: 1,
-  version: "0.1.0",
-  displayName: "Research Plugin",
-  description: "Creates a managed research agent and scheduled research routine.",
-  author: "Example",
-  categories: ["automation"],
-  capabilities: [
-    "agents.managed",
-    "projects.managed",
-    "routines.managed",
-    "skills.managed",
-    "instance.settings.register",
-  ],
-  entrypoints: {
-    worker: "./dist/worker.js",
-    ui: "./dist/ui",
-  },
-  agents: [
-    {
-      agentKey: "researcher",
-      displayName: "Researcher",
-      role: "research",
-      title: "Research Agent",
-      capabilities: "Runs recurring research briefs for this company.",
-      adapterPreference: ["codex_local", "claude_local", "process"],
-      instructions: {
-        content: "Follow the Paperclip heartbeat and produce concise research briefs.",
-      },
-    },
-  ],
-  projects: [
-    {
-      projectKey: "research",
-      displayName: "Research",
-      description: "Recurring research work created by the Research Plugin.",
-      status: "in_progress",
-    },
-  ],
-  routines: [
-    {
-      routineKey: "weekly-brief",
-      title: "Weekly research brief",
-      description: "Create a short research brief for the board.",
-      assigneeRef: { resourceKind: "agent", resourceKey: "researcher" },
-      projectRef: { resourceKind: "project", resourceKey: "research" },
-      priority: "medium",
-      triggers: [
-        {
-          kind: "schedule",
-          label: "Monday morning",
-          cronExpression: "0 9 * * 1",
-          timezone: "America/Chicago",
-          enabled: false,
-        },
-      ],
-    },
-  ],
-  skills: [
-    {
-      skillKey: "weekly-brief-skills",
-      displayName: "Weekly Briefer",
-      description: "Reusable skill for the managed research workflow.",
-    },
-  ],
-  ui: {
-    slots: [
-      {
-        type: "settingsPage",
-        id: "settings",
-        displayName: "Research",
-        exportName: "SettingsPage",
-      },
-    ],
-  },
-};
-
-export default manifest;
-```
-
-In the worker, expose a small setup action or settings-page action that
-reconciles the resources for the selected company:
-
-```ts
-import { definePlugin } from "@paperclipai/plugin-sdk";
-
-export default definePlugin({
-  setup(ctx) {
-    ctx.actions.register("setup-company", async (params) => {
-      const companyId = String(params.companyId ?? "");
-      if (!companyId) throw new Error("companyId is required");
-
-      const project = await ctx.projects.managed.reconcile("research", companyId);
-      const agent = await ctx.agents.managed.reconcile("researcher", companyId);
-      const routine = await ctx.routines.managed.reconcile("weekly-brief", companyId);
-      const skill = await ctx.skills.managed.reconcile("weekly-brief-skills", companyId);
-
-      return { project, agent, routine, skill };
-    });
-  },
-});
-```
-
-Authoring rules:
-
-- Keep keys stable once published. Renaming `agentKey`, `projectKey`,
-  `routineKey`, or `skillKey` creates a new managed resource from the host's
-  point of view.
-- Use managed agents for plugin-provided labor. Use `ctx.agents.invoke()` or
-  `ctx.agents.sessions` only after you have a real agent id, either selected by
-  the operator or resolved from `ctx.agents.managed`.
-- Use managed routines for recurring or externally triggered work that should
-  produce tasks. Schedule, webhook, and API triggers are visible routine
-  triggers, and each run has the normal Paperclip issue/audit trail.
-- Use managed skills for reusable operator-visible capabilities that are shared
-  by managed agents. Reconcile skill declarations by `skillKey` and keep the
-  declared skill markdown and files in sync with agent behavior.
-- Use managed projects to keep plugin-generated work organized and to give
-  project-scoped plugin UI a stable home. For filesystem access inside a
-  project, still resolve project workspaces through `ctx.projects`.
-- Keep defaults conservative. Managed declarations are suggestions owned by the
-  plugin, but the resulting resources are normal Paperclip records that the
-  operator can inspect, pause, and adjust.
-
 UI:
 
 - `usePluginData`
@@ -325,7 +104,6 @@ Mount surfaces currently wired in the host include:
 - `settingsPage`
 - `dashboardWidget`
 - `sidebar`
-- `routeSidebar`
 - `sidebarPanel`
 - `detailTab`
 - `taskDetailView`
@@ -336,191 +114,6 @@ Mount surfaces currently wired in the host include:
 - `commentAnnotation`
 - `commentContextMenuItem`
 
-## Shared host components
-
-Use shared components from `@paperclipai/plugin-sdk/ui` when the plugin needs a
-Paperclip-native control. The host owns the implementation, so plugins inherit
-the board's current styling, ordering, recent selections, and dark-mode behavior
-without importing `ui/src` internals.
-
-Prefer shared components for common Paperclip UX patterns to reduce drift and
-deprecation risk, especially for task/assignment flows and routine or sidebar-like
-plugin screens.
-
-Currently exposed components include:
-
-- `MarkdownBlock` and `MarkdownEditor` for rendered and editable markdown.
-- `FileTree` for serializable file and directory trees.
-- `IssuesList` for a native company-scoped issue table.
-- `AssigneePicker` for the same agent/user selector used in the new issue pane.
-  Use the controlled `value` format `agent:<id>`, `user:<id>`, or `""`.
-- `ProjectPicker` for the same project selector used in the new issue pane.
-  Use the controlled project id value, or `""` for no project.
-- `ManagedRoutinesList` for plugin-owned routine settings pages.
-
-```tsx
-import { AssigneePicker, ProjectPicker } from "@paperclipai/plugin-sdk/ui";
-
-export function PluginAssignmentControls({ companyId }: { companyId: string }) {
-  const [assignee, setAssignee] = useState("");
-  const [projectId, setProjectId] = useState("");
-
-  return (
-    <>
-      <AssigneePicker
-        companyId={companyId}
-        value={assignee}
-        onChange={(value) => setAssignee(value)}
-      />
-      <ProjectPicker
-        companyId={companyId}
-        value={projectId}
-        onChange={setProjectId}
-      />
-    </>
-  );
-}
-```
-
-## File and path UI
-
-Plugin UI often needs to render a file tree, accept a folder path, or browse a
-project workspace. There are three different surfaces for that, and they map to
-different trust and data-flow boundaries. Pick the surface that matches the
-data the plugin actually has.
-
-### When to use the shared `FileTree`
-
-Use `FileTree` from `@paperclipai/plugin-sdk/ui` whenever the plugin only needs
-to render a serializable file/directory list and react to selection or
-expand/collapse. The host owns the implementation, so plugin UI inherits the
-board's icons, indent, focus ring, and dark-mode styling without importing host
-internals.
-
-```tsx
-import {
-  FileTree,
-  type FileTreeNode,
-} from "@paperclipai/plugin-sdk/ui";
-
-const nodes: FileTreeNode[] = [
-  { name: "AGENTS.md", path: "AGENTS.md", kind: "file", children: [] },
-  {
-    name: "wiki",
-    path: "wiki",
-    kind: "dir",
-    children: [
-      { name: "index.md", path: "wiki/index.md", kind: "file", children: [] },
-    ],
-  },
-];
-
-export function WikiTree() {
-  const [expanded, setExpanded] = useState<Set<string>>(() => new Set(["wiki"]));
-  const [selected, setSelected] = useState<string | null>(null);
-
-  return (
-    <FileTree
-      nodes={nodes}
-      selectedFile={selected}
-      expandedPaths={expanded}
-      onSelectFile={(path) => setSelected(path)}
-      onToggleDir={(path) =>
-        setExpanded((current) => {
-          const next = new Set(current);
-          next.has(path) ? next.delete(path) : next.add(path);
-          return next;
-        })
-      }
-    />
-  );
-}
-```
-
-Good fits:
-
-- LLM Wiki page navigation in `packages/plugins/plugin-llm-wiki` builds a
-  `FileTreeNode[]` from worker query results and renders it through `FileTree`.
-- The example `plugin-file-browser-example` lazily fetches a directory's
-  children through a `loadFileList` action when `onToggleDir` fires, then
-  merges the children into the local tree state — letting the shared component
-  handle rendering and selection.
-
-Boundary rules:
-
-- Keep the prop surface serializable (`nodes`, `expandedPaths`, `checkedPaths`,
-  `fileBadges`, `fileTones`). Do not pass arbitrary render functions across the
-  plugin/host boundary in v1; the supported escape hatches are
-  `fileBadges` (status pill keyed by path) and `fileTones` (row tone keyed by
-  path).
-- Do not import the host's `FileTree.tsx` or any `ui/src/*` module. The SDK
-  declaration is the only supported import path for plugin UI.
-- The shared `FileTree` is for rendering and selection. Plugin-specific editors,
-  ingest flows, query forms, and lint runs stay inside the plugin and do not
-  belong as `FileTree` props.
-
-### When to declare `localFolders`
-
-When the plugin needs operator-configured filesystem roots — typically for
-trusted local plugins like wiki tooling — declare `localFolders[]` on the
-manifest and add the `local.folders` capability. The host renders a settings
-surface for the operator to set the absolute path, validates the path
-server-side (containment, symlinks, required files/directories), and exposes
-`ctx.localFolders.readText()` and `ctx.localFolders.writeTextAtomic()` in the
-worker.
-
-```ts
-export const manifest = {
-  capabilities: ["local.folders"],
-  localFolders: [
-    {
-      folderKey: "content-root",
-      displayName: "Content root",
-      access: "readWrite",
-      requiredDirectories: ["sources", "pages"],
-      requiredFiles: ["schema.md"],
-    },
-  ],
-};
-```
-
-Use this when:
-
-- The data lives outside any project workspace.
-- Reads and writes need company-scoped configuration.
-- The operator picks the path once in plugin settings and the worker resolves
-  files relative to that root.
-
-Do not use `localFolders` to grant the UI direct browser-side access to the
-filesystem — there is no such capability. The browser still goes through the
-worker via `getData` / `performAction`, and the worker only exposes paths it
-chose to expose.
-
-### When to keep worker-mediated project workspace browsing
-
-When the data lives inside an existing project workspace, keep the browsing
-flow worker-mediated:
-
-- The worker uses `ctx.projects.listWorkspaces()` to resolve the workspace
-  path, then reads its filesystem with normal Node APIs.
-- The plugin UI calls a `getData` handler for the root listing and an action
-  for lazy children, then renders them through `FileTree`.
-- The worker is the only side that touches the disk. The browser receives a
-  serializable tree and never sees raw absolute paths it can replay.
-
-The example `plugin-file-browser-example` is the reference for this pattern:
-the worker registers `fileList` (data) and `loadFileList` (action) over the
-same handler, and the UI uses the action for on-toggle directory loading so the
-shared `FileTree` stays the rendering surface.
-
-### Mixing surfaces
-
-A single plugin can use more than one of these. The LLM Wiki uses
-`localFolders` for its content root, then renders the resulting page list
-through `FileTree`. The file browser example uses `ctx.projects.listWorkspaces`
-to pick a workspace and renders its on-disk tree through `FileTree` with lazy
-loading. Pick the boundary per data source, not per plugin.
-
 ## Company routes
 
 Plugins may declare a `page` slot with `routePath` to own a company route like:

doc/plugins/PLUGIN_SPEC.md

@@ -27,10 +27,7 @@ Current limitations to keep in mind:
 - Published npm packages are the intended install artifact for deployed plugins.
 - The repo example plugins under `packages/plugins/examples/` are development conveniences. They work from a source checkout and should not be assumed to exist in a generic published build unless they are explicitly shipped with that build.
 - Dynamic plugin install is not yet cloud-ready for horizontally scaled or ephemeral deployments. There is no shared artifact store, install coordination, or cross-node distribution layer yet.
-- The current runtime ships a small host-provided plugin UI component kit through `@paperclipai/plugin-sdk/ui`, but does not support plugin asset uploads/reads yet. Treat plugin asset APIs as future-scope ideas, not current implementation promises.
-- Scoped plugin API routes are JSON-only and must be declared in `apiRoutes`.
-  They mount under `/api/plugins/:pluginId/api/*`; plugins cannot shadow core
-  API routes.
+- The current runtime does not yet ship a real host-provided plugin UI component kit, and it does not support plugin asset uploads/reads. Treat those as future-scope ideas in this spec, not current implementation promises.
 
 In practice, that means the current implementation is a good fit for local development and self-hosted persistent deployments, but not yet for multi-instance cloud plugin distribution.
 
@@ -319,10 +316,7 @@ export interface PaperclipPluginManifestV1 {
   version: string;
   displayName: string;
   description: string;
-  author: string;
   categories: Array<"connector" | "workspace" | "automation" | "ui">;
-  minimumHostVersion?: string;
-  /** @deprecated Use `minimumHostVersion` instead. Retained for backwards compatibility. */
   minimumPaperclipVersion?: string;
   capabilities: string[];
   entrypoints: {
@@ -338,42 +332,15 @@ export interface PaperclipPluginManifestV1 {
     description: string;
     parametersSchema: JsonSchema;
   }>;
-  database?: PluginDatabaseDeclaration;
-  apiRoutes?: PluginApiRouteDeclaration[];
-  environmentDrivers?: PluginEnvironmentDriverDeclaration[];
-  agents?: PluginManagedAgentDeclaration[];
-  projects?: PluginManagedProjectDeclaration[];
-  routines?: PluginManagedRoutineDeclaration[];
-  skills?: PluginManagedSkillDeclaration[];
-  localFolders?: PluginLocalFolderDeclaration[];
-  /** Legacy top-level launcher declarations. Prefer `ui.launchers` for new manifests. */
-  launchers?: PluginLauncherDeclaration[];
   ui?: {
-    launchers?: PluginLauncherDeclaration[];
     slots: Array<{
-      type: "page"
-        | "detailTab"
-        | "taskDetailView"
-        | "dashboardWidget"
-        | "sidebar"
-        | "routeSidebar"
-        | "sidebarPanel"
-        | "projectSidebarItem"
-        | "globalToolbarButton"
-        | "toolbarButton"
-        | "contextMenuItem"
-        | "commentAnnotation"
-        | "commentContextMenuItem"
-        | "settingsPage"
-        | "companySettingsPage";
+      type: "page" | "detailTab" | "dashboardWidget" | "sidebar" | "settingsPage";
       id: string;
       displayName: string;
       /** Which export name in the UI bundle provides this component */
       exportName: string;
       /** For detailTab: which entity types this tab appears on */
       entityTypes?: Array<"project" | "issue" | "agent" | "goal" | "run">;
-      /** For page and companySettingsPage: single route segment */
-      routePath?: string;
     }>;
   };
 }
@@ -384,17 +351,10 @@ Rules:
 - `id` must be globally unique
 - `id` should normally equal the npm package name
 - `apiVersion` must match the host-supported plugin API version
-- `minimumHostVersion` is preferred, with `minimumPaperclipVersion` retained for
-  backwards compatibility
 - `capabilities` must be static and install-time visible
 - config schema must be JSON Schema compatible
 - `entrypoints.ui` points to the directory containing the built UI bundle
 - `ui.slots` declares which extension slots the plugin fills, so the host knows what to mount without loading the bundle eagerly; each slot references an `exportName` from the UI bundle
-- declare managed declarations with the matching `*.managed` capability:
-  - `agents` → `agents.managed`
-  - `projects` → `projects.managed`
-  - `routines` → `routines.managed`
-  - `skills` → `skills.managed`
 
 ## 11. Agent Tools
 
@@ -664,62 +624,7 @@ Required SDK clients:
 
 Plugins that need filesystem, git, terminal, or process operations handle those directly using standard Node APIs or libraries. The host provides project workspace metadata through `ctx.projects` so plugins can resolve workspace paths, but the host does not proxy low-level OS operations.
 
-## 14.1 Issue Orchestration APIs
-
-Trusted orchestration plugins can create and update Paperclip issues through `ctx.issues` instead of importing server internals. The public issue contract includes parent/project/goal links, board or agent assignees, blocker IDs, labels, billing code, request depth, execution workspace inheritance, and plugin origin metadata.
-
-Plugins that perform durable work should declare managed Paperclip resources rather than using private plugin state:
-
-- `agents` + `ctx.agents.managed.*` for named, invokable operators (`agents.managed` required)
-- `projects` + `ctx.projects.managed.*` for stable, scoped issue/workspace ownership (`projects.managed` required)
-- `routines` + `ctx.routines.managed.*` for schedule/webhook/manual execution with issue trails (`routines.managed` required)
-- `skills` + `ctx.skills.managed.*` for reusable agent capabilities (`skills.managed` required)
-
-The LLM Wiki plugin is the current reference for this pattern: it declares managed
-agents, projects, routines, and skills in manifest, reconciles them per company,
-and uses managed routines for periodic wiki maintenance and ingest operations.
-Content-oriented plugins should follow the same model instead of running
-unmanaged background loops: make the LLM-facing worker an operator-visible
-managed agent, attach reusable prompt/tool guidance as managed skills, keep
-operation issues in a managed project, and drive recurring work through managed
-routines.
-
-Origin rules:
-
-- Built-in core issues keep built-in origins such as `manual` and `routine_execution`.
-- Plugin-managed issues use `plugin:<pluginKey>` or a sub-kind such as `plugin:<pluginKey>:feature`.
-- The host derives the default plugin origin from the installed plugin key and rejects attempts to set `plugin:<otherPluginKey>` origins.
-- `originId` is plugin-defined and should be stable for idempotent generated work.
-
-Relation and read helpers:
-
-- `ctx.issues.relations.get(issueId, companyId)`
-- `ctx.issues.relations.setBlockedBy(issueId, blockerIssueIds, companyId)`
-- `ctx.issues.relations.addBlockers(issueId, blockerIssueIds, companyId)`
-- `ctx.issues.relations.removeBlockers(issueId, blockerIssueIds, companyId)`
-- `ctx.issues.getSubtree(issueId, companyId, options)`
-- `ctx.issues.summaries.getOrchestration({ issueId, companyId, includeSubtree, billingCode })`
-
-Governance helpers:
-
-- `ctx.issues.assertCheckoutOwner({ issueId, companyId, actorAgentId, actorRunId })` lets plugin actions preserve agent-run checkout ownership.
-- `ctx.issues.requestWakeup(issueId, companyId, options)` requests assignment wakeups through host heartbeat semantics, including terminal-status, blocker, assignee, and budget hard-stop checks.
-- `ctx.issues.requestWakeups(issueIds, companyId, options)` applies the same host-owned wakeup semantics to a batch and may use an idempotency key prefix for stable coordinator retries.
-
-Plugin-originated issue, relation, document, comment, and wakeup mutations must write activity entries with `actorType: "plugin"` and details fields for `sourcePluginId`, `sourcePluginKey`, `initiatingActorType`, `initiatingActorId`, and `initiatingRunId` when a user or agent run initiated the plugin work.
-
-Scoped API routes:
-
-- `apiRoutes[]` declares `routeKey`, `method`, plugin-local `path`, `auth`,
-  `capability`, optional checkout policy, and company resolution.
-- The host enforces auth, company access, `api.routes.register`, route matching,
-  and checkout policy before worker dispatch.
-- The worker implements `onApiRequest(input)` and returns a JSON response shape
-  `{ status?, headers?, body? }`.
-- Only safe request headers are forwarded; auth/cookie headers are never passed
-  to the worker.
-
-## 14.2 Example SDK Shape
+## 14.1 Example SDK Shape
 
 ```ts
 /** Top-level helper for defining a plugin with type checking */
@@ -791,46 +696,20 @@ The host enforces capabilities in the SDK layer and refuses calls outside the gr
 - `project.workspaces.read`
 - `issues.read`
 - `issue.comments.read`
-- `issue.documents.read`
-- `issue.relations.read`
-- `issue.subtree.read`
 - `agents.read`
 - `goals.read`
 - `activity.read`
 - `costs.read`
-- `issues.orchestration.read`
-- `database.namespace.read`
 
 ### Data Write
 
 - `issues.create`
 - `issues.update`
 - `issue.comments.create`
-- `issue.interactions.create`
-- `issue.documents.write`
-- `issue.relations.write`
-- `issues.checkout`
-- `issues.wakeup`
+- `assets.write`
+- `assets.read`
 - `activity.log.write`
 - `metrics.write`
-- `telemetry.track`
-- `assets.read`
-- `assets.write`
-- `database.namespace.migrate`
-- `database.namespace.write`
-- `goals.create`
-- `goals.update`
-- `projects.managed`
-- `routines.managed`
-- `skills.managed`
-- `agents.managed`
-- `agents.pause`
-- `agents.resume`
-- `agents.invoke`
-- `agent.sessions.create`
-- `agent.sessions.list`
-- `agent.sessions.send`
-- `agent.sessions.close`
 
 ### Plugin State
 
@@ -843,10 +722,8 @@ The host enforces capabilities in the SDK layer and refuses calls outside the gr
 - `events.emit`
 - `jobs.schedule`
 - `webhooks.receive`
-- `local.folders`
 - `http.outbound`
 - `secrets.read-ref`
-- `environment.drivers.register`
 
 ### Agent Tools
 
@@ -859,7 +736,6 @@ The host enforces capabilities in the SDK layer and refuses calls outside the gr
 - `ui.page.register`
 - `ui.detailTab.register`
 - `ui.dashboardWidget.register`
-- `ui.commentAnnotation.register`
 - `ui.action.register`
 
 ## 15.2 Forbidden Capabilities
@@ -896,13 +772,6 @@ Minimum event set:
 - `issue.created`
 - `issue.updated`
 - `issue.comment.created`
-- `issue.document.created`
-- `issue.document.updated`
-- `issue.document.deleted`
-- `issue.relations.updated`
-- `issue.checked_out`
-- `issue.released`
-- `issue.assignment_wakeup_requested`
 - `agent.created`
 - `agent.updated`
 - `agent.status_changed`
@@ -912,8 +781,6 @@ Minimum event set:
 - `agent.run.cancelled`
 - `approval.created`
 - `approval.decided`
-- `budget.incident.opened`
-- `budget.incident.resolved`
 - `cost_event.created`
 - `activity.logged`
 
@@ -968,7 +835,6 @@ Job rules:
 3. The host prevents overlapping execution of the same plugin/job combination unless explicitly allowed later.
 4. Every job run is recorded in Postgres.
 5. Failed jobs are retryable.
-6. For recurring business workflows that should create visible Paperclip work, prefer managed routines and managed resources over jobs. Jobs remain useful for private plugin-runtime maintenance tasks.
 
 ## 18. Webhooks
 
@@ -1051,23 +917,13 @@ export function DashboardWidget({ context }: PluginWidgetProps) {
 
 The SDK includes a `ui` subpath export that plugin frontends import. This subpath provides:
 
-- **Bridge hooks**: `usePluginData(key, params)`, `usePluginAction(key)`, `useHostContext()`, `useHostNavigation()`
+- **Bridge hooks**: `usePluginData(key, params)`, `usePluginAction(key)`, `useHostContext()`
 - **Design tokens**: colors, spacing, typography, shadows matching the host theme
 - **Shared components**: `MetricCard`, `StatusBadge`, `DataTable`, `LogView`, `ActionBar`, `Spinner`, etc.
 - **Type definitions**: `PluginPageProps`, `PluginWidgetProps`, `PluginDetailTabProps`
 
 Plugins are encouraged but not required to use the shared components. A plugin may render entirely custom UI as long as it communicates through the bridge.
 
-`useHostNavigation()` is the supported way for plugin UI to navigate to
-Paperclip-internal pages. It exposes `resolveHref(to)`, `navigate(to,
-options?)`, and `linkProps(to, options?)`. Plugin links should prefer
-`linkProps()` so anchors keep real `href` values for copy-link, modifier-click,
-middle-click, and open-in-new-tab behavior while plain left-clicks route through
-the host SPA router. The host resolves company-scoped paths against the active
-company prefix without double-prefixing already-prefixed paths. Plugin UI should
-not use raw same-origin `href`s or `window.location.assign()` for internal
-Paperclip navigation because those can force a full document reload.
-
 ### 19.0.2 Bundle Isolation
 
 Plugin UI bundles are loaded as standard ES modules, not iframed. This gives plugins full rendering performance and access to the host's design tokens.
@@ -1147,11 +1003,6 @@ The host SDK ships shared components that plugins can import to quickly build UI
 | `LogView` | Scrollable log output with timestamps | Webhook deliveries, job output, process logs |
 | `JsonTree` | Collapsible JSON tree for debugging | Raw API responses, plugin state inspection |
 | `Spinner` | Loading indicator | Data fetch states |
-| `FileTree` | Host-styled file/directory tree | Wiki pages, workspace files, import previews |
-| `IssuesList` | Host issue list | Plugin pages that need a native issue view |
-| `AssigneePicker` | Host assignee picker for agents and board users | Creating issues, assigning routines, filtering work |
-| `ProjectPicker` | Host project picker | Creating issues, scoping dashboards, filtering work |
-| `ManagedRoutinesList` | Host routine list | Plugin settings pages that manage routines |
 
 Plugins may also use entirely custom components. The shared components exist to reduce boilerplate and keep visual consistency, not to limit what plugins can render.
 
@@ -1209,8 +1060,6 @@ For plugins that need richer settings UX beyond what JSON Schema can express, th
 
 Both approaches coexist: a plugin can use the auto-generated form for simple config and add a custom settings page slot for advanced configuration or operational dashboards.
 
-For plugins that need a company-scoped settings surface, declare a `companySettingsPage` slot with a `routePath`. The host renders a sidebar item under Company Settings and mounts the component at `/:companyPrefix/company/settings/:routePath`. The page receives `companyId` and `companyPrefix` in its host context. Core settings routes such as `access`, `invites`, `environments`, and `secrets` are reserved and cannot be shadowed by plugin declarations.
-
 ## 20. Local Tooling
 
 Plugins that need filesystem, git, terminal, or process operations implement those directly. The host does not wrap or proxy these operations.
@@ -1389,8 +1238,6 @@ Plugin-originated mutations should write:
 
 - `actor_type = plugin`
 - `actor_id = <plugin-id>`
-- details include `sourcePluginId` and `sourcePluginKey`
-- details include `initiatingActorType`, `initiatingActorId`, and `initiatingRunId` when a user or agent run triggered the plugin work
 
 ## 21.5 Plugin Migrations
 
@@ -1460,14 +1307,6 @@ Each plugin may expose a company-context main page:
 
 This page is where board users do most day-to-day work.
 
-## 24.4 Company Settings Plugin Page
-
-Each ready plugin may expose a company settings page:
-
-- `/:companyPrefix/company/settings/:routePath`
-
-The host adds a matching Company Settings sidebar item using the slot `displayName`. Plugin settings route segments are single-segment slugs and must not collide with core company settings pages.
-
 ## 25. Uninstall And Data Lifecycle
 
 When a plugin is uninstalled, the host must handle plugin-owned data explicitly.