DottaandPaperclip fd61dc1dd5 docs(skills): distinguish Paperclip verification targets (#16145) ...

## Thinking Path

> - Paperclip is the open source app people use to manage AI agents for
work.
> - Verification must show which runtime and user journey passed.
> - The existing skill centers on an empty instance launched from
source.
> - Seeded data, reused databases, published packages, and hosted stacks
prove different outcomes.
> - This pull request makes the target and starting conditions explicit.
> - It routes deployment to private Cloud skills and keeps feature
checks in Verify Paperclip.

## Linked Issues or Issue Description

**Issue type**
Missing documentation.

**Where is the issue?**
`.agents/skills/verify-paperclip/SKILL.md`.

**What's wrong?**
The skill does not distinguish source development, npm installation,
staging, and production. It also needs to distinguish fresh onboarding
from seeded or reused data and make platform scope explicit.

**Suggested fix**
Add target selection and focused references. Preserve the existing
empty-instance helper. Name the private Cloud deployment skills as a
separate prerequisite when deployment is requested. No duplicate
documentation PR was found in the open-PR search.

## What Changed

- Record artifact, environment, starting data, platform, and journey
before testing.
- Document dev servers, fresh instances, seeded/reused test drives, and
cloned worktrees.
- Separate exact-version canary and stable npm verification from source
and Cloud evidence.
- Document staging and production checks and route deployment to
`deploy-paperclip-stack` or `deploy-cloud-harness` in the private Cloud
repo.
- Limit local ownership helpers to instances created by their launcher.

## Verification

- Current-head GitHub CI: 55 passed, 2 skipped, no failures. Typecheck,
tests, build, and the aggregate gate passed. Greptile: 5/5, all threads
resolved.

- Skill validator: passed.
- Relative Markdown file links: passed across the changed skills and
references (29 links in final validation).
- `python3 -m unittest discover -s .agents/skills/verify-paperclip/tests
-v`: 2 passed.
- `node scripts/check-maps.mjs`: passed (structural coverage only).
- `git diff --check`: passed.
- `pnpm -r typecheck`, `pnpm test:run`, and `pnpm build`: attempted;
blocked by missing workspace dependencies (`node_modules`, Node type
definitions, and the checkout tsx entry point). These are not passing
full-suite results.
- Existing published-launcher test attempt was blocked by sandbox
loopback permissions; it does not provide package-install evidence.
- Reviewed commands against development docs, release workflow, and
current Cloud runbooks. No live deployment, publication, or production
mutation was performed for these documentation changes.

## Risks

- Low runtime risk: only skill documentation changes.
- Private deployment skills require access to the Cloud repo and must be
available before that handoff works. The verifier reports the
prerequisite when unavailable.
- Workflow changes can make command guidance stale. The skills direct
readers to maintained workflows and runbooks before use.

## Model Used

OpenAI GPT-6 via Codex, with reasoning, file editing, shell execution,
and GitHub CLI access. The runtime does not expose a more specific model
ID or context-window size.

## Checklist

- [x] I have included a thinking path that traces from project context
to this change
- [x] I have specified the model used (with version and capability
details)
- [x] I have checked ROADMAP.md and confirmed this PR does not duplicate
planned core work
- [x] I have searched GitHub for duplicate or related PRs and linked
them above
- [x] I have either (a) linked existing issues with `Fixes: #` / `Closes
#` OR (b) described the issue in-PR following the relevant issue
template
- [x] I have not referenced internal/instance-local Paperclip issues or
links (only public GitHub `#NNN` / `github.com/paperclipai/paperclip`
URLs)
- [x] My branch name describes the change and contains no internal
Paperclip ticket id or instance-derived details
- [x] I have run tests locally and they pass (the focused ownership
suite; full-suite limits are listed above)
- [x] I have added or updated tests where applicable (no runtime change;
existing tests retained)
- [x] I have updated relevant documentation to reflect my changes
- [x] I have considered and documented any risks above
- [x] All Paperclip CI gates are green
- [x] Greptile is 5/5 with no open P2s, recommendations, or follow-ups
- [x] I will address all Greptile and reviewer comments before
requesting merge

---------

Co-authored-by: Paperclip <noreply@paperclip.ing>

2026-10-13 07:02:37 -05:00

..

skills

docs(skills): distinguish Paperclip verification targets (#16145)

2026-10-13 07:02:37 -05:00