acture hard don'ts — pre-merge checklist

Read before merging any non-trivial change. These are anti-patterns the reference research collectively rules out. They MUST be enforced in code review.

Source: docs/redesign_takeaways.md §3.

1. No conditional logic in command metadata

Symptom: command.if, command.unless, command.when with logical operators in flight, command.dependsOn with computation, command "inheritance," polymorphic command records.

Why it's wrong: Inner Platform Effect. Command metadata growing toward a mini-language ends in a Greenspun's-Tenth-Rule lisp.

Fix: If you want conditional logic, refactor into two commands OR push the conditional into execute. The closed CommandRecord shape is the structural guardrail.

Exception: the when field (DSL or (ctx) => boolean) — this is the upper bound of acceptable metadata complexity, and even it is a frequent source of confusion in VS Code.

2. No god-package

Symptom: A single acture package import gives you the palette, the AI adapter, the MCP server, the migration helpers, the form rendering, undo, telemetry, etc.