Status

status is the quickest read on the Boundline 0.82.0 planning gates.

What To Look For

When a plan exists or is blocked, look for:

• plan_quality_state
• plan_quality_findings
• plan_quality_assumptions
• backlog_quality_state
• backlog_quality_findings
• backlog_task_count
• backlog_mvp_scope
• backlog_unmapped_items
• planning_analysis_state
• planning_analysis_findings
• planning_analysis_coverage
• repository_map_state
• snapshot_cache_state
• context_pack_entry_count
• context_omission_finding_count
• patch_safe_edit_attempt_count
• capability_provider_status
• capability_provider_id
• capability_provider_activation_state
• capability_provider_capability_ids
• capability_provider_setup_requirements
• capability_provider_summary
• next_command
• assistant_next_command
• blocked or recovery guidance

Older snapshots remain readable. The additive plan-quality fields are runtime output, not configuration keys.

When planning_analysis_state is blocked, execution is not admitted even if the earlier planning gates are ready. Read the finding source, then follow the emitted planning continuation instead of routing directly to run.

When the large-codebase substrate is active, the same summary may also show typed context entry lines, omission reasons, and patch-safe edit guardrails. Treat blocked omissions, stale tracked cache, or unsafe full-read refusal as real planning stops rather than advisory context notes.

When provider-backed execution is configured, the same summary can also expose provider activation state, declared capability IDs, setup requirements, and the latest validation disposition or failure class. Treat provider readiness, permission, or evidence failures as real bounded stops rather than hidden retry signals.