docs(intent): lifecycle stages, report scope, and statuses by name

[delchev]

Documents the intent DSL additions from eclipse-dirigible/dirigible#6647 (issue eclipse-dirigible/dirigible#6645). The vendor-neutral specification wording is proposed separately as IntentFile/intent-specification#6.

The problem being documented: an aggregation over an entity that carries a function: EntityStatus counted drafts nobody had issued, cancelled documents and voided ones, unless the author remembered a status predicate in filter: — and nothing in the DSL, the generator or the editor said the report was incomplete without one. The report generated, the SQL was valid, the tile rendered a number, and the number was wrong.

/help/intent/dsl-reference

• seeds → stage — the draft | live | cancelled | void vocabulary as a table, that it is metadata and never becomes a column (the CSV and imported table are unchanged), and the id / vocabulary / stage-property-collision rules.
• seeds → Statuses by name, not by id — every site that accepts a seeded name, and why names are the better default: an id is positional, so inserting a status mid-nomenclature silently retargets every guard authored against the old numbering. The red-storno-vs-Void ledger case is named concretely, because "prefer names" is unconvincing without it.
• reports → scope — the three shapes, the exact three conditions under which an unscoped aggregate defaults to live (and why a status dimension or an authored status filter stands it down), and a warning callout for the case that matters most: when the nomenclature is unclassified, the Generate warning is the omission's only signal — visible in the Intent Editor's notes strip, the Builder shell's publish panel, and the warnings field of POST /services/ide/intent/generate.
• The transitions snippet now shows symbolic statuses; the cross-model boundary is listed under Planned.

npm run docs:build is clean and the three new anchors resolve (#stage-what-a-status-means-to-the-lifecycle, #statuses-by-name-not-by-id, #scope-which-lifecycle-rows-an-aggregate-counts), as do the cross-references between them.