v0.4.2 - Practical agent workflow and bounded live communication

v0.4.2 - Practical agent workflow and bounded live communication

PIC v0.4.2 is the practical package snapshot for agent-output checking, workflow verification, residual ledgers, bounded external intake, and local agent-to-agent candidate exchange.

The public message is practical first: use PIC to turn agent text, local files, explicit web/feed inputs, and agent messages into auditable JSON reports with evidence routing, unresolved-work ledgers, and next safe actions. The deeper ASI-proxy framing remains protocol-relative. This release does not prove real ASI, physical outcomes, simulator truth, oracle truth, or policy success.

First command

python -m pip install percolation-inversion-compiler==0.4.2
pic agent check --compact --text "Candidate packet: preserve residuals." --profile development
pic agent runbook --profile development

Use a source checkout for canonical TeX audits, repository fixtures, full examples/..., development checks, and release engineering.

What changed

• Added pic agent check --compact as the first command for humans, CI jobs, and agents.
• Added installed-package demos and bootstrap examples for practical PyPI use.
• Made explicit-source live intake bounded and candidate-only by default. Use --no-allow-live-connectors for local-only dry runs.
• Added local agent relay commands: pic agent message send, pic agent message receive, pic agent inbox verify, and pic agent relay-readiness.
• Expanded ECPT/BIT/TRC/SQOT/ALT theory-fidelity reports: phase-control audit summaries, bottleneck witness reports, frontier debt reports, scheduler diagnostics, and value-bridge diagnostics.
• Extended JSON Schema and portability conformance examples for non-Python ports.
• Updated docs and glossary so project-specific terms map to common workflow language.

How to read the result

• accepted=true means the finite report envelope passed checks.
• workflow_usable=true means the compact workflow can guide next safe actions.
• operationally_usable=true means the deeper runtime report can guide routing under the selected profile.
• settled=true only means scoped finite obligations are discharged.
• settled=false is often the correct safe result when obligations remain.
• residual_ledger, missing_obligations, and unresolved_obligations must be preserved downstream.

Safety boundary

• No hidden promotion from accepted, workflow_usable, or packet volume to settled.
• No background crawling, autonomous polling, shell execution, page script execution, form submission, repository mutation, or credential use.
• External intake and agent messages remain packet candidates until verifier, identity, nonce, provenance, rollback, semantic-edge, and residual policies pass.
• Local relay output is not proof of external-world truth.
• ASI-proxy phase-control remains a protocol-relative coordination target, not a real ASI proof.

Release integrity

The PyPI package and GitHub Release package assets remain the published v0.4.2 artifacts. PyPI does not allow replacing an already published file for the same version, so this release keeps artifact integrity instead of publishing mismatched same-version wheels.

After publication, the repository main branch was revalidated and hardened for release operations:

• portability conformance hashes are LF-normalized for cross-platform source checkouts;
• the Security workflow uses the Gitleaks CLI container path, avoiding the licensed GitHub Action failure mode;
• latest main CI and Security runs are green.

These post-publication hardening commits do not change the PyPI v0.4.2 artifact. Use a future version if package bytes need to include further code changes.

Verification

Release gates passed: pytest with coverage >=90%, ruff, mypy, bandit, pip-audit, twine check, distribution artifact check, publish-safety, citation validation, Zizmor, portability conformance, canonical-suite audit, fidelity audit, provenance/SBOM smoke, and wheel install smoke.