[criptogus]

Summary

/solutions → explicit inputs, dependency order, context budget, approved version-locked bundles
/evidence → comparable version/model/experiment cohorts, measured counts and 95% intervals
/account/teams → database-enforced roles, private immutable versions, independent review and pins
/admin/curation → conservative overlap candidates, provenance/license review report
MCP → list_solutions + compare_task_evidence (read-only)

Adds 21 original candidate skills across six business categories and four goal-based playbooks, with complete scripts, references and fixtures. Preserves all accepted UTF-8 files in immutable hashed plugin archives, retaining the original manifest version. Structural conformance cannot publish a package; approval and live-version changes require genuine adversarial evidence for the exact version. Public bundle exports remain free-package only.

Evidence

• Before: plugin import retained only the first skill and regenerated away auxiliary files; recommendations favored unrelated popularity; no team, solution or matched-evidence UI.
  After: complete multi-skill archive and tamper tests, business relevance ranking with the same trust gate, and the four routes above.
• 206 Node tests; application and SDK types; production build; strict lint with zero explicit any; dependency/content audits; generated mirrors and plugin checks.
• 46 executable Python helper fixtures, including actual OEE/RPN/frame-time/reconciliation values and invalid ranges. These are input/calculation checks, not model evaluation.
• 35 actual PostgreSQL authorization assertions in rollback transactions; 92-table RLS/anonymous-access audit. Desktop/mobile signup and eight business UI fixture scenarios run locally with intercepted requests; screenshots personally inspected.
• Native database migration and 25 unpublished drafts applied. Skills use immutable version 0.1.1; playbooks use 0.1.0. No trust scores or certifications were fabricated. No Lovable generation/agent calls were made. Jev advisory timed out; review continued locally without repeated calls.
• Release metadata is already bumped and validated in this PR (chore: bump platform version 0.5.7 to 0.6.0), intentionally preventing a redundant post-merge version-bot bump.

The concurrent main merge had restored a legacy snapshot, including the removed any debt and deleted validation tooling. This PR retains the fixes from PRs 60–62 and integrates the genuine new preview-auth typing, investigation-document rename, Bun binary-release setup and Vite configuration 2.26.5. The merged tree is validated after a clean locked install.

Merge Danger

Door: two-way for application code; additive database state is retained on rollback.

Blast Radius: platform

Introduces seven RLS-protected tables and narrowly scoped security-definer functions. Team writes are serialized and authorized in PostgreSQL; invitations are email-bound, expiring and single-use; the owner is protected; reviewers cannot approve their own skill. Public certification for new content remains pending real model-specific adversarial evaluation. Telemetry is observational and reports tokens/latency, not invented monetary savings. No automatic execution, award, payment, email, merge or deletion is added.