@stackwright-pro/launch-stackwright-pro 0.4.0-alpha.1 → 0.4.0-alpha.101

package/LICENSE

@@ -0,0 +1,21 @@
+PROPRIETARY SOFTWARE LICENSE
+
+Copyright (c) 2024-2026 Per Aspera LLC. All Rights Reserved.
+
+This software and associated documentation files (the "Software") are the
+proprietary and confidential property of Per Aspera LLC ("Company").
+
+RESTRICTIONS: You may not use, copy, modify, merge, publish, distribute,
+sublicense, sell, or otherwise exploit this Software or any portion thereof
+without the express prior written consent of the Company.
+
+GOVERNMENT USE: Use, duplication, or disclosure by the U.S. Government is
+subject to restrictions as set forth in FAR 52.227-19 (Commercial Computer
+Software - Restricted Rights) and DFARS 252.227-7013 (Rights in Technical
+Data and Computer Software), as applicable.
+
+THE SOFTWARE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED. IN NO EVENT SHALL THE COMPANY BE LIABLE FOR ANY CLAIM, DAMAGES, OR
+OTHER LIABILITY ARISING FROM THE USE OF THE SOFTWARE.
+
+For licensing inquiries: legal@peraspera.com

package/README.md

@@ -15,14 +15,20 @@ to automatically wire up Pro features:
    - MCP server configuration in `.code-puppy.json`
    - Role-based dev scripts (`dev:admin`, `dev:analyst`, `dev:viewer`)
 3. **Post-processing** → Copies Pro templates, adds auth config, generates README
+4. **Auto-install** → `pnpm install` runs automatically after scaffolding —
+   citizen developers get a project ready to use without knowing what a package manager is
 
 ## Quick Start
 
 ```bash
-npx launch-stackwright-pro my-app --yes
+# Works — project created in $cwd/my-app
+pnpx @stackwright-pro/launch-stackwright-pro --name my-app -y
+# Dependencies install automatically (~7s)
 cd my-app
-pnpm install
-pnpm dev
+npx @stackwright-pro/raft   # Start the otter raft
+
+# Equivalent explicit form
+pnpx @stackwright-pro/launch-stackwright-pro my-app --name my-app -y
 ```
 
 ### With an OpenAPI Spec
@@ -49,8 +55,9 @@ my-app/
 │   └── prebuild.js           # Reads stackwright.yml → runs OpenAPI plugin
 ├── specs/                    # Only if --spec was provided
 │   └── <your-spec>.yaml
-├── .stackwright/
-│   └── otters/               # 🦦 Brand, foreman, page, & theme otters
+├── node_modules/
+│   ├── @stackwright/otters/       # 🦦 OSS otters (brand, theme, page, foreman)
+│   └── @stackwright-pro/otters/   # 🦦 Pro otters (api, data, dashboard, foreman)
 ├── stackwright.yml           # Theme + auth + integrations config
 ├── next.config.js            # Pro config (transpile pro pkgs + yaml-loader)
 ├── yaml.d.ts                 # TS declarations for YAML imports
@@ -69,7 +76,7 @@ Options:
   --force              Overwrite existing directory
   --skip-otters        Skip otter raft setup
   -y, --yes            Skip prompts, use defaults
-  --spec <path>        Path to an OpenAPI spec (YAML or JSON)
+  --spec <paths...>    Paths to OpenAPI specs (can be specified multiple times)
   --spec-name <name>   Name for the API integration (default: derived from filename)
   -V, --version        Output the version number
   -h, --help           Display help
@@ -114,3 +121,14 @@ automatically via the hooks system:
 
 See the main [Stackwright Pro documentation](https://github.com/Per-Aspera-LLC/stackwright-pro)
 for architecture details, auth deep-dives, and deployment guides.
+
+## Starting the Otter Raft
+
+```bash
+cd my-app
+npx @stackwright-pro/raft
+```
+
+The raft verifies otter integrity, loads project context from `.stackwright/init-context.json`, and spawns code-puppy in foreman mode. Tell the foreman about your specs in natural language — it coordinates the API, auth, data, and page otters to build your app.
+
+All state lives in `.stackwright/` — you can interrupt and resume at any time.