feat: integrate framework files into monorepo under packages/mosaic/framework/

Moves all Mosaic framework runtime files from the separate bootstrap repo
into the monorepo as canonical source. The @mosaic/mosaic npm package now
ships the complete framework — bin scripts, runtime configs, tools, and
templates — enabling standalone installation via npm install.

Structure:
  packages/mosaic/framework/
  ├── bin/          28 CLI scripts (mosaic, mosaic-doctor, mosaic-sync-skills, etc.)
  ├── runtime/      Runtime adapters (claude, codex, opencode, pi, mcp)
  ├── tools/        Shell tooling (git, prdy, orchestrator, quality, etc.)
  ├── templates/    Agent and repo templates
  ├── defaults/     Default identity files (AGENTS.md, STANDARDS.md, SOUL.md, etc.)
  ├── install.sh    Legacy bash installer
  └── remote-install.sh  One-liner remote installer

Key files with Pi support and recent fixes:
- bin/mosaic: launch_pi() with skills-local loop
- bin/mosaic-doctor: --fix auto-wiring for all 4 harnesses
- bin/mosaic-sync-skills: Pi as 4th link target, symlink-aware find
- bin/mosaic-link-runtime-assets: Pi settings.json patching
- bin/mosaic-migrate-local-skills: Pi skill roots, symlink find
- runtime/pi/RUNTIME.md + mosaic-extension.ts

Package ships 251 framework files in the npm tarball (278KB compressed).

packages/mosaic/framework/tools/portainer/README.md

@@ -0,0 +1,212 @@
+# Portainer CLI Scripts
+
+CLI tools for managing Portainer stacks via the API.
+
+## Setup
+
+### Environment Variables
+
+Set these environment variables before using the scripts:
+
+```bash
+export PORTAINER_URL="https://portainer.example.com:9443"
+export PORTAINER_API_KEY="your-api-key-here"
+```
+
+You can add these to your shell profile (`~/.bashrc`, `~/.zshrc`) or use a `.env` file.
+
+### Creating an API Key
+
+1. Log in to Portainer
+2. Click your username in the top right corner > "My account"
+3. Scroll to "Access tokens" section
+4. Click "Add access token"
+5. Enter a descriptive name (e.g., "CLI scripts")
+6. Copy the token immediately (you cannot view it again)
+
+### Dependencies
+
+- `curl` - HTTP client
+- `jq` - JSON processor
+
+Both are typically pre-installed on most Linux distributions.
+
+## Scripts
+
+### stack-list.sh
+
+List all Portainer stacks.
+
+```bash
+# List all stacks in table format
+stack-list.sh
+
+# List stacks in JSON format
+stack-list.sh -f json
+
+# List only stack names
+stack-list.sh -f names
+stack-list.sh -q
+
+# Filter by endpoint ID
+stack-list.sh -e 1
+```
+
+### stack-status.sh
+
+Show status and containers for a stack.
+
+```bash
+# Show stack status
+stack-status.sh -n mystack
+
+# Show status in JSON format
+stack-status.sh -n mystack -f json
+
+# Use stack ID instead of name
+stack-status.sh -i 5
+```
+
+### stack-redeploy.sh
+
+Redeploy a stack. For git-based stacks, this pulls the latest from the repository.
+
+```bash
+# Redeploy a stack by name
+stack-redeploy.sh -n mystack
+
+# Redeploy and pull latest images
+stack-redeploy.sh -n mystack -p
+
+# Redeploy by stack ID
+stack-redeploy.sh -i 5 -p
+```
+
+### stack-logs.sh
+
+View logs for stack services/containers.
+
+```bash
+# List available services in a stack
+stack-logs.sh -n mystack
+
+# View logs for a specific service
+stack-logs.sh -n mystack -s webapp
+
+# Show last 200 lines
+stack-logs.sh -n mystack -s webapp -t 200
+
+# Follow logs (stream)
+stack-logs.sh -n mystack -s webapp -f
+
+# Include timestamps
+stack-logs.sh -n mystack -s webapp --timestamps
+```
+
+### stack-start.sh
+
+Start an inactive stack.
+
+```bash
+stack-start.sh -n mystack
+stack-start.sh -i 5
+```
+
+### stack-stop.sh
+
+Stop a running stack.
+
+```bash
+stack-stop.sh -n mystack
+stack-stop.sh -i 5
+```
+
+### endpoint-list.sh
+
+List all Portainer endpoints/environments.
+
+```bash
+# List in table format
+endpoint-list.sh
+
+# List in JSON format
+endpoint-list.sh -f json
+```
+
+## Common Workflows
+
+### CI/CD Redeploy
+
+After pushing changes to a git-based stack's repository:
+
+```bash
+# Redeploy with latest images
+stack-redeploy.sh -n myapp -p
+
+# Check status
+stack-status.sh -n myapp
+
+# View logs to verify startup
+stack-logs.sh -n myapp -s api -t 50
+```
+
+### Debugging a Failing Stack
+
+```bash
+# Check overall status
+stack-status.sh -n myapp
+
+# List all services
+stack-logs.sh -n myapp
+
+# View logs for failing service
+stack-logs.sh -n myapp -s worker -t 200
+
+# Follow logs in real-time
+stack-logs.sh -n myapp -s worker -f
+```
+
+### Restart a Stack
+
+```bash
+# Stop the stack
+stack-stop.sh -n myapp
+
+# Start it again
+stack-start.sh -n myapp
+
+# Or just redeploy (pulls latest images)
+stack-redeploy.sh -n myapp -p
+```
+
+## Error Handling
+
+All scripts:
+
+- Exit with code 0 on success
+- Exit with code 1 on error
+- Print errors to stderr
+- Validate required environment variables before making API calls
+
+## API Reference
+
+These scripts use the Portainer CE API. Key endpoints:
+
+| Endpoint                                          | Method | Description              |
+| ------------------------------------------------- | ------ | ------------------------ |
+| `/api/stacks`                                     | GET    | List all stacks          |
+| `/api/stacks/{id}`                                | GET    | Get stack details        |
+| `/api/stacks/{id}/file`                           | GET    | Get stack compose file   |
+| `/api/stacks/{id}`                                | PUT    | Update/redeploy stack    |
+| `/api/stacks/{id}/git/redeploy`                   | PUT    | Redeploy git-based stack |
+| `/api/stacks/{id}/start`                          | POST   | Start inactive stack     |
+| `/api/stacks/{id}/stop`                           | POST   | Stop running stack       |
+| `/api/endpoints`                                  | GET    | List all environments    |
+| `/api/endpoints/{id}/docker/containers/json`      | GET    | List containers          |
+| `/api/endpoints/{id}/docker/containers/{id}/logs` | GET    | Get container logs       |
+
+For full API documentation, see:
+
+- [Portainer API Access](https://docs.portainer.io/api/access)
+- [Portainer API Examples](https://docs.portainer.io/api/examples)
+- [Portainer API Docs](https://docs.portainer.io/api/docs)