v1: Migration plan — unify credentials + GTM engine into /ship

[maxtechera]

Context

The repo has two strong but disconnected pieces: a working credentials preflight checker and a GTM pipeline engine with supervisors. The README currently describes the product as /credentials — not /ship. v1 unifies them under a single identity and gets both pieces fully functional.

Current State

Component	Status
credentials/ sub-skill + Python checker	✅ most functional (29 services, 23/29 connected)
engine/ GTM pipeline stages	⚠️ structure exists, Linear integration untested
supervisors/ control loop	⚠️ defined, wiring to stage supervisors incomplete
README identity	❌ says "/credentials" — should be "/ship"
ship-engine v0.2	⚠️ explicitly "in progress" per README
user-invocable: false in SKILL.md	⚠️ blocks direct user invocation

v1 Milestone — What "Working" Means

A user runs /ship start "<idea>" and the full GTM pipeline runs: Intake → Validate → Strategy → Awareness → Lead Capture → Nurture → Closing → Launch → Measure. Credentials preflight fires automatically before Launch. Linear tickets are created and progressed.

Work Required

1. Identity + README

• Update README title and description to /ship (not /credentials)
• Make user-invocable: true in SKILL.md
• Add /ship command table to README (start, status, stage, credentials)

2. Credentials sub-skill — polish to v1

• Audit remaining 6 unconnected services — fix or document as optional
• Validate --fix flag output accuracy for each failing service
• Test check_local.py --quiet and --json modes end-to-end
• Extension mechanism (*.yml drop-in) tested with one real example

3. GTM pipeline engine

• /ship start "<idea>" creates a Linear run ticket and kicks off Intake
• Each stage supervisor completes and hands off to next stage
• Critic gates fire between stages (ship-critic rubrics)
• Stage status is reflected on the Linear ticket

4. Launch preflight integration

• Launch stage invokes credentials/scripts/check_local.py before deploy
• Any credential failure blocks Launch with a clear report
• Fix commands printed inline

5. OSS tool product type

• oss_tool product type (recently added) integrated into Intake stage
• Validate it flows through all stages correctly

6. Distribution

• End-to-end install test: Claude Code plugin
• End-to-end install test: clawhub install ship
• End-to-end install test: manual git clone

Out of Scope for v1

• Multi-product / portfolio runs
• Paid tier or SaaS wrapper
• CI/CD integration beyond credential gate
• Analytics dashboard

Definition of Done

• /ship start "test idea" completes Intake and creates Linear ticket
• Credentials preflight blocks Launch on a missing token
• README accurately describes /ship (not /credentials)
• Install via git clone works on a clean machine