jpcite v0.5.0¶

Release date: 2026-05-16 Versioning: Semantic Versioning 2.0.0 Changelog format: Keep a Changelog 1.1.0 Previous release: v0.4.0 (2026-05-12)

Summary¶

v0.5.0 introduces the agent runtime contract layer — a stable response envelope that AI agents can rely on across tool calls. The release also seals the production deployment readiness gate and adds budget guardrails for the underlying data pipeline.

What's new¶

Agent runtime contract layer¶

19 Pydantic response models covering Citation, Evidence, OutcomeContract, Disclaimer, BillingHint, and RateLimitHint surfaces.
21 JSON Schemas under the jpcir/ canonical registry, round-trip validated against the Pydantic models.
Every default-gate tool now performs egress validation through this contract layer — agents receive a predictable shape on every call.

New machine-readable artifacts¶

policy_decision_catalog — disclaimer envelope per regulated surface (lawyer/accountant/tax/social-insurance scope rulings).
csv_private_overlay_contract — column-level egress contract for customer-private CSV overlays with PII redaction and audit-log requirements.
billing_event_ledger — append-only billing event contract with idempotency-cache binding.
aws_budget_canary_attestation — budget canary attestation artifact for pipeline cost guardrails.

Operations and safety¶

Cloudflare Pages rollback automation script set with retry, idempotency, post-rollback smoke, and attestation steps.
Emergency kill-switch scripts and Makefile target for operator-initiated stop.
Production deployment readiness gate now passes all 7 checks.

Tests and quality¶

Test coverage raised to 76-77% project-wide, with high-impact modules raised significantly (composition_tools 19.8 to 72 percent, intel_competitor_landscape 23.4 to 84 percent, realtime_signal_v2 0 to 58 percent).
mypy --strict: 0 errors on src/.
ruff: 0 errors.
pytest: 8200+ tests pass.

Breaking changes¶

None — this release is additive only.

Public API surface (REST /v1/*, MCP tool list) is backward-compatible.
Existing tool count and tool names are unchanged.
Existing migrations and table structures are unchanged.
Existing API keys and Stripe subscriptions continue to work without action.

Security¶

Fail-closed policy validator (17 axes)¶

Rows in blocked_* / quarantine / deny states always return public_compile_allowed=false. CI gates detect any of the 17 axes turning red.

Two-stage operator unlock¶

Live data-pipeline commands require explicit operator unlock — the readiness state and the live-command flag are intentionally separated to prevent accidental side-effects.

CI guards strengthened¶

Forbidden LLM API imports / env vars blocked in src/, scripts/cron/, scripts/etl/, and tests/.
ACK fingerprint helper enforces a single canonical hash routine.

Migration guide¶

Existing users — no action required¶

v0.4.0 → v0.5.0 is fully backward compatible.

REST /v1/* and MCP tool calls are unchanged.
Existing API keys and Stripe subscriptions continue to work.
Schema migrations apply automatically at boot (size-aware to avoid hangs on large databases).

New cookbook recipes¶

Five new agent recipes are available for v0.5.0:

r17 — Cursor IDE MCP setup
r18 — ChatGPT Custom GPT Actions (slim 30-path OpenAPI)
r19 — Gemini extension
r20 — OpenAI Agents SDK
r21 — Prefecture × program heatmap (cohort matcher)

Developer migration notes¶

New tools should validate their egress through agent_runtime/contracts.py Pydantic models.
New JSON Schemas must be registered in schemas/jpcir/_registry.json and pass the contract round-trip check.
New preflight gates must register their artifact in release_capsule_manifest.json and pass the sequence-integrity check.

Known limitations¶

Test coverage at 76-77 percent — target 80+ percent for the next minor.
A small number of legacy scripts/ files with naming-convention exceptions are suppressed via per-file-ignores in pyproject.toml; whole-repo ruff is clean.

CHANGELOG.md — main changelog in Keep a Changelog format (repo 復旧後に再リンク)。
Agent runtime contracts — response envelope documentation.

Operator: Bookyou株式会社 (適格請求書発行事業者番号 T8010001213708, 代表梅田茂利)