assembles `bin/containerization-x86_64- .tar.gz` (cctl + cloud-hypervisor + virtiofsd + initfs.ext4 + kernel) for x86_64 Linux deployment, cross-compiled inside the aarch64 dev container via the Static Linux SDK (Swift) and `cargo zigbuild
current function-calling exercises |
| **`qwen3.5:4b`** | Stage 7 (debate / eval / observability / streaming / deploy mechanics) | 3.4 GB official Ollama tag. These exercises do not depend on function calling; this row does
expert guidance on using n8n-mcp MCP tools effectively for building n8n workflows, plus deploying the self-hosted n8n that runs them.
**Architecture**:
- **n8n-mcp MCP Server**: Provides data access
Reserve `panic` for startup-time fail-fast (`config.MustGet`, cluster-scorer boot failure, invalid `ROUTER_DEPLOYMENT_MODE`) where misconfiguration must abort process.
- **Never introduce DI container, reflection-based wiring, or service
boot, `main.go` panics. Misconfiguration must abort the process rather than silently degrade.
- Validate deployment target overrides through `policy.Registry.ValidateDeployment` after provider/model configuration is resolved. A partial or catalog-incompatible explicit target
format` (Biome formatter)
- **Sanity Studio**: `npm run sanity:dev` (start Sanity Studio development server)
- **Deploy GraphQL**: `npm run sanity:deploy` (deploy GraphQL API to Sanity)
- **Generate Types**: `npm run schema
feature relates to CESP/MCP/packs)
## Website
`docs/` contains the static landing page ([peonping.com](https://peonping.com)), deployed via Vercel. A `vercel.json` in `docs/` provides the `/install` redirect so `curl -fsSL peonping.com/install
particularly to check files that haven't been changed.
# Documentation
Docs are rendered and deployed through the `pydantic/unified-docs` pipeline. Do not use MkDocs checks in this repository.
When linking between
forwarding lifecycle events
### Demo Environment
A comprehensive demo manifest is available for testing:
```bash
# Deploy 60 services across 2 namespaces
kubectl apply -f test/manifests/demo-microservices.yaml
# Forward all demo services with
/marketplace.json` points at it.
- `docs/`: `safety.md`, `backends.md`, `deployment.md`. `scripts/`: install, demo, smoke, screenshots, check, deploy, verify.
- `tests/`: the suites that span packages (both roles on all three paths); each package
kernel. **Lean** uses a generated Skill capsule plus that kernel. Both are unavailable for deployment until paired evidence satisfies [`references/prompt-profiles.json`](references/prompt-profiles.json).
- Evaluation-only compact assemblies are visibly `deployment_eligible: false
push to R2, and write a source-vs-derived parity report
- `/portaljs-deploy` — one-shot deploy to Vercel or static hosting
- `/portaljs-connect-ckan` — wire a portal to a CKAN backend over
A file Claude Code reads at the start of every session. It holds the commands, conventions and warnings the agent needs for this project.
Where does it go?
At the repository root. Claude Code also reads CLAUDE.md files in subdirectories when it works there.
What should it contain?
Build and test commands, the project's layout, conventions that aren't obvious from the code, and mistakes to avoid. Short files tend to work better than long ones.
CLAUDE.md or AGENTS.md?
Claude Code reads CLAUDE.md; most other agents read AGENTS.md. Many projects keep one and point the other at it.