Skip to content

v0.5 Candidate Release Readiness Audit

Audit date: 2026-07-27. Scope: the Engineering Process Intelligence increment merged in main at 83941ab, carried into the release-state merge commit f546b76, and included in the final PR #88 merge f6232e4.

Executive summary

The v0.5 candidate implementation scope is present in main and covered by accepted ADRs, versioned protocol contracts, pure application analysis, and authenticated local daemon handlers. Release preparation has synchronized the workspace packages to 0.5.0-beta.1; npm next still points to the published 0.4.0-beta.1 artifact, and no v0.5 tag or npm publication is authorized.

Remote compatibility verification is complete. This audit remains a readiness record, not authorization to publish a tag or npm artifact.

Candidate scope

CapabilityContract and implementation evidenceCLIDaemonMCPBoundary
Workflow variant summaryADR-0037, WORKFLOW_VARIANT_SUMMARY_V0_1_SPEC.md, summarizeWorkflowVariantsNoYesNoDeterministic sequence counts only
Observed duration metricsADR-0038, WORKFLOW_DURATION_METRICS_V0_1_SPEC.md, summarizeWorkflowDurationsNoYesNoElapsed case duration only
Conformance trend summaryADR-0039, CONFORMANCE_TREND_SUMMARY_V0_1_SPEC.md, summarizeConformanceTrendNoYesNoCaller-supplied reports only
Workflow repetition summaryADR-0040, WORKFLOW_REPETITION_SUMMARY_V0_1_SPEC.md, summarizeWorkflowRepetitionsNoYesNoRepetition is not labelled rework or retry
Observed transition intervalsADR-0041, WORKFLOW_TRANSITION_INTERVALS_V0_1_SPEC.md, summarizeWorkflowTransitionIntervalsNoYesNoAdjacent timestamp intervals only

All five operations remain local, read-only, deterministic, project-scoped, and provider-neutral. They do not infer waiting time, rework, bottlenecks, productivity, quality, causality, actor performance, remote evidence, persistence, or model judgments.

Verification matrix

GateStatusEvidence or remaining action
ADR and specification coveragePASSADR-0037 through ADR-0041 and matching v0.1 specifications are merged
Protocol/application/daemon implementationPASSCanonical protocol methods, pure analysis operations, application bridges, and authenticated daemon routing are in main
Deterministic testsPASSProcess-intelligence focused tests and the merged baseline full suite passed before the release-state documentation work; PR #88 CI passed all 12 compatibility checks
Workspace version synchronizationPASSRoot, all workspace manifests, and generated core version are synchronized to 0.5.0-beta.1
Release changelog and release-state updatePASSv0.5 candidate section, workspace/npm boundary, roadmap, and publishing notes are updated
Build, pack, and dry-run publicationPASSnpm pack --dry-run --json and npm publish --dry-run --tag next --access public pass for intentloom@0.5.0-beta.1; PR #88 remote compatibility CI passed all 12 checks (local pnpm build remains unavailable because the environment is missing @types/node)
Git tag and npm publicationBLOCKEDRequires explicit maintainer authorization, npm ownership/permissions, and a successful readiness review

Release blockers and non-goals

  • The current published artifact remains intentloom@0.4.0-beta.1 under next; npm latest remains 0.1.0-alpha.3.
  • A v0.5 release must not silently add CLI or MCP claims for operations that currently expose only protocol, application, and daemon surfaces.
  • Waiting-time semantics, rework classification, bottleneck inference, causal analysis, live providers, external MCP ingestion, persistence, and model interpretation remain outside this candidate.
  • No tag, npm publication, dist-tag change, or trusted-publishing configuration is performed by this preparation step.

Verdict

Release preparation ready for an explicit publication decision; publication is not authorized by this audit. Package dry-runs and the PR #88 remote compatibility matrix pass for 0.5.0-beta.1. The subsequent release step has pushed Git tag v0.5.0-beta.1; npm publication remains incomplete pending one-time-password confirmation.