fix(lint,spec): export the two new rule ids from the lint barrel; re-anchor the retirement-jurisdiction citation to the docblock that decided it

- packages/lint/src/index.ts: FLOW_DECISION_MODE_INVALID and
  FLOW_DECISION_INCLUSIVE_OVERLAP join the flow-pattern export block
  (rule-id-barrel-exports pin).
- conversions/registry.ts: the retiredFromLoadPath jurisdiction is cited
  from MetadataConversion's docblock and ADR-0087's 2026-07-31 addendum,
  not from a tracker number that no longer resolves.
- schemaless-node-config.zod.ts: the mode JSDoc no longer spells an
  omitted-means-every sentence the empty-state gate has to classify.

Claude-Session: https://claude.ai/code/session_01CiCTczDo7tGhafXjf61dUJ
Co-authored-by: Claude <noreply@anthropic.com>

Author: claude

packages/lint/src/index.ts

@@ -841,6 +841,8 @@ export {
   FLOW_MULTI_WRITE_UNFILTERED,
   FLOW_LOOP_BODY_UNCONTAINED,
   FLOW_TRY_CATCH_WITHOUT_CATCH,
+  FLOW_DECISION_MODE_INVALID,
+  FLOW_DECISION_INCLUSIVE_OVERLAP,
 } from './lint-flow-patterns.js';
 
 export { lintLivenessProperties } from './lint-liveness-properties.js';

packages/spec/src/automation/schemaless-node-config.zod.ts

@@ -543,8 +543,9 @@ export const DecisionConfigSchema = lazySchema(() => strictObject({
     .describe('Ordered decision branches (first true expression wins; omit to branch purely on edge conditions)'),
   /**
    * How many out-edges an edge-branched decision takes when more than one
-   * condition holds — `'exclusive'` (the first, in declaration order; what an
-   * omitted key means) or `'inclusive'` (every one). Read by the engine's
+   * condition holds: `'exclusive'` is the first, in declaration order, and is
+   * the reading an absent key gets — the narrower one, a single branch;
+   * `'inclusive'` is all of them. Read by the engine's
    * traversal: see "Where `mode` is honoured" above. Any other value is
    * refused with {@link decisionModePrescription}; either member beside a
    * non-empty `conditions` list is refused by the `.superRefine` below, with

packages/spec/src/conversions/registry.ts

@@ -11383,9 +11383,11 @@ const reportJoinedChartRemoved: MetadataConversion = {
  * `--from`. `retiredFromLoadPath: true` keeps it off the authoring funnel
  * (`normalizeStackInput`), where an author who wrote two branches today, against
  * the contract that says an omitted `mode` is exclusive, must not be rewritten
- * into an inclusive gateway. The flag's jurisdiction ends there (#16864), so
- * every data-at-rest seam that opens the retired window has to refuse this id
- * by name, on the artifact door's precedent for `app-hidden-to-unpublished`
+ * into an inclusive gateway. The flag's jurisdiction ends there — its own
+ * docblock on `MetadataConversion` says so, and ADR-0087's 2026-07-31 addendum
+ * is why: data-at-rest seams replay retired entries on purpose — so every
+ * data-at-rest seam that opens the retired window has to refuse this id by
+ * name, on the artifact door's precedent for `app-hidden-to-unpublished`
  * (#17885, `DEFAULT_FLIPS_NOT_REPLAYED_HERE` in `@objectstack/metadata-core`):
  * the automation engine's flow rehydration seam does (`registerFlow` serves
  * code-shipped flows, REST bodies and Studio saves alike, none of them dated),