pi-toolbox-discovery v0.1.1

Changed

• Removed the agent-vent toolbox bundle alias.
• The diagnostic bundle id is only agent_vent.

Validation: package npm run check passed locally before release.

pi-agent-vent v0.1.2

Fixed

• Hardened extension load so review-state command schema construction has a local fallback if the Pi extension loader sees a stale REVIEW_STATES import during reload.

Validation: package npm run check passed locally and in isolated worktree before release.

pi-agent-vent v0.1.1

Changed

• Removed the /agent-vent command compatibility alias.
• Runtime-facing tool, command, and toolbox bundle naming is now singularly agent_vent.

Validation: package npm run check passed locally before release.

pi-society-orchestrator v0.2.0

Changed

• Routed runtime sqlite3, dolt, and rocs-cli read paths through async, timeout-bound supervised helpers instead of synchronous runtime execFileSync calls.
• Tightened cognitive-tool lookup by name so non-cognitive prompt templates cannot be injected into dispatch or loop execution.
• Made explicit societyDb targeting outrank ambient AK_DB for ak-backed runtime calls.
• Expanded society_query read-only gating to allow valid read-only WITH ... SELECT ... diagnostics while still rejecting mutating or stacked SQL.
• Isolated npm run release:check installs behind a temporary NPM_CONFIG_PREFIX so routine release validation does not mutate the default global npm package space.
• Routed cognitive_dispatch evidence recording through a shared ak-first helper instead of a bespoke direct SQL insert.
• Centralized evidence-write behavior behind recordEvidence(...), keeping SQL fallback explicit while aligning runAk(...) with the configured SOCIETY_DB / AK_DB target.
• Migrated ontology_context and /ontology from raw ontology SQL reads to a shared rocs-cli adapter that resolves ROCS build/index artifacts against the configured ontology repo.
• Replaced package-local docs/dev/ usage with docs/project/ + docs/adr/ nomenclature and updated package handoff/README links accordingly.
• Clarified monorepo AK task/work-item guidance in AGENTS/README: use the repo-root ak wrapper (or ../.ak from this package) instead of treating a package folder as an independent repo root.
• Updated the package template in parallel so new monorepo package scaffolds inherit the same docs placement and AK-wrapper guidance.
• Moved /evidence off raw sqlite reads onto ak evidence search and isolated society_query behind a dedicated bounded diagnostic-exception helper.
• Gated Level-4 post-integration cleanup packets so cleanup dry-runs require exact peer run ids with valid candidate-peer registry sidecars, executable cleanup/fallback commands require exact peer ids, worktrees, branches, and successful integration closeout, and Level-4 reports surface compact registry-sidecar readiness.
• Made Level-4 cleanup reports explicitly distinguish blocked, dry-run-ready, and execute-ready cleanup posture so destructive cleanup readiness is visible without reading raw tool details.
• Added a Level-4 post-fan-in promotion handoff packet/report section that carries measured-packet fan-in, owner review, finalizer-token request, AK evidence, and post-closeout cleanup sequencing as one visible owner-gated tail.
• Added a post-fan-in finalizer closeout receipt to make review_blocked, committed_cleaned, and failed_closed outcomes auditable across validation, finalizer apply, evidence handoff, and cleanup handoff without executing owner-gated mutations.

pi-peer-messaging v0.1.0

Initial public component release of @tryinget/pi-peer-messaging.\n\nHighlights:\n- Stable same-machine peer-session messaging core.\n- Deterministic local broker/client runtime.\n- Intercom-compatible adapter with list/send/ask/reply/pending/status.\n- Canonical PEER_ACK/PEER_FINAL status/watch support by peerRunId and legacy QUEST compatibility by questId.\n- Peer and quest protocol ledgers are vocabulary-isolated when ids collide.

pi-autoresearch v0.1.0

Initial public component release of @tryinget/pi-autoresearch.\n\nHighlights:\n- Governed bounded experiment runtime and /autoresearch operator surface.\n- Runtime setup/status/run/loop/finalization surfaces with append-only receipts.\n- Candidate binding, empirical posture, closeout/evidence/learning packet family, and adapter validation.\n- Candidate-result validation fails closed on malformed candidate internals before downstream adapters consume packets.