0.0.0-alpha.4

Architekton 0.0.0-alpha.4 turns the complete Gateway Server dogfood into a stronger, still-conservative experimental alpha.

Added

• architekton:verify, a read-only, diff-aware and intent-aware checker with explicit independent or degraded assessment provenance.
• Bounded static GitHub Actions analysis for overlapping triggers, notification error masking, conditional or path-filtered required-check risk, notification check noise, docs-only validation gaps, unsafe .gitignore classification, runtime version drift, and Dependabot target-branch conflicts.
• Exact handoffs for hosted GitHub controls, security state, Slack receipt, and other outcomes that local inspection cannot prove.
• Regression coverage derived from sanitized Gateway Server dogfooding scenarios.

Changed

• architekton:inspect now separates effective state, conflicts, verified facts, unknown or unsupported facts, exact next actions, and optional deeper checks.
• architekton:bootstrap now proactively recommends a canonical ENGINEERING.md when practice is fragmented and requires at least one real maintainer-answer round.
• architekton:maintain now treats existing ENGINEERING.md as first-class, shows the exact proposal early, and accepts one approval for an unchanged proposal.
• Engineering contracts are detected structurally. The legacy Architekton marker is optional and non-normative.
• Deterministic findings now disclose scope, evidence type, and limitations; actionable unknowns include bounded handoffs.

Safety and limitations

• Inspection and verification remain read-only.
• Static workflow analysis does not execute GitHub Actions or prove hosted configuration, Slack receipt, deployment, or runtime success.
• Arbitrary code, workflow, configuration, and hosted remediation remains outside architekton:maintain.