Panda Suite Docs
v1.9.2GitHub ↗
Panda Suite / Release v1.4.0

v1.4.0 — Panda Craft

Panda Suite adds panda-craft, bringing the catalog to 22 independent skills. It implements the supplied Skill Composition & Execution Harness proposal as an optional coordinator for explicitly selected Panda or external specialists.

Changes

  • Shared outcome and acceptance contract, compact evidence/authorization handoffs, actual specialist instruction loading and bounded correction.
  • Chanda, Viriya, Citta and Vīmaṃsā guide intent, sustained execution, focus and examination without a mandatory Buddhist Method dependency or separate runtime.
  • Specialist methods, scope, verification budgets and permission limits are preserved. Missing skills and tools are reported without invented execution.
  • Completion reports distinguish implementation from VERIFIED, PARTIALLY VERIFIED, BLOCKED and NOT VERIFIED evidence status.
  • Lead routing, English/Thai catalogs, usage examples and a generated Craft guide.
  • Eight blind evaluation scenarios, a green-suite contract-gap fixture, a correct reviewer control, and a tooling regression for all 24 case/arm preparations.
  • Stored machine-specific paths normalized to relative references, including historical task/run records. The provenance note explains how these normalized representations relate to original evidence.

Verification and limitations

See Craft’s contract and actual evaluation and the release verification record. One fresh-context direct-specialist/Craft pair completed the implementation case; independent supplied-suite, contract and usage-example reruns passed for both. This establishes no incremental correctness, speed, cost or reliability benefit. Seven other Craft behavioral cases, a Lead comparison, repeated samples and real Impeccable UI composition remain Not Run. Host discovery and package validation are reported separately from interactive plugin activation.

Compatibility and recovery

Portable and Claude manifests advance from 1.3.0 to 1.4.0. Existing skills and selectors remain supported. No service, dependency or migration is introduced; Lead retains its existing coordination capability. Craft is optional and does not become a prerequisite for direct specialist use. Pinned upstream content and license limitations remain unchanged.

Use tag v1.3.0 for the previous catalog. Preserve customized installed skills before replacement. Publication does not refresh installed plugin caches. The source release needs no application rollout or data migration. GitHub Pages publishes the documentation from main through the existing workflow; its result is checked separately after pushing.