[jung-thomas]

Summary

Four small independent cleanups in one PR:

C1 — Expanded CLI-deprecation lint rules (spec task 4.4)

Adds 5 new advisory rules to scripts/lint-rules/data/cli-deprecations.json (all severity 'warning', never block builds):

Rule	Removed/deprecated in
cf map-route --hostname	CF CLI v8
cf create-route --hostname	CF CLI v8
cf push --no-route	CF CLI v8
cds run	@sap/cds 6 (deprecated for cds watch)
npm install -g @sap/cds	@sap/cds-dk 7 (should be @sap/cds-dk)

Also adds a quarterly-review reminder header comment to scripts/lint-rules/deprecated-cli.ts (per spec task 4.4) with links to official changelogs and documents the needsOwnerReview interface field.

Rules needing owner review (marked "needsOwnerReview": true in the JSON — these fire at 'warning' but need confirmation against official changelogs):

• cf map-route --hostname — parallel to existing --hostname removal, high confidence but not independently verified against CF CLI v8 release notes
• cf create-route --hostname — same reasoning
• cf push --no-route — same reasoning
• cds run — deprecated in favour of cds watch, but exact version not confirmed
• npm install -g @sap/cds — @sap/cds-dk installs the cds CLI, @sap/cds is runtime-only, but exact "deprecated since" version needs owner verification

C2 — New promotion-warning lint rule (advisory 'notice' severity)

Adds promotionWarningRule to scripts/lint-rules/authoring-aids.ts, registered in the RULES array in scripts/lint-tutorial-markdown.ts.

Assumption (flagged for confirmation): The rule detects :::promotion-warning container directive blocks in PROD tutorial source. Semantics assumed analogous to :::qa-only — an author-placed "do not promote without resolving this" marker. The :::promotion-warning directive has not yet been deployed to the platform; this rule pre-declares the lint gate for when authors begin using the pattern. The exact directive syntax may need adjusting once it ships. Owners: confirm the pattern or adjust before promoting this rule beyond DEV.

Severity is 'notice' (below 'warning'), which means it is advisory only and never blocks a build even with --strict.

C3 — Fix stale §3.5.2 doc (OS option-tab fallback behavior)

docs/authors/writing-tutorials.md §3.5.2 still described the pre-#2820 "closest match" fallback ("No Linux instructions for this step — showing macOS."). Since commit e82393c (#2820) the platform performs exact-match-only rendering: if the chosen OS has no panel in a step group, it shows "No <OS> instructions for this step." — no substitution. Updated to describe the current behavior.

D — Fix MCP slicer latent static-import bug (#3029 pattern)

packages/mcp/tutorial-step-slicer.js had a static import { renderDirectivesAsText } from '../../scripts/parsers/directives.js'. At CF runtime, scripts/parsers/ is not deployed into gen/srv, so this fails. It was masked by KG_STEP_SLICER_ENABLED defaulting off and the srv/lib shim's bundle fallback.

Applied the same fix #3029 used in freshness-detector.js: replace the static import with a memoised lazy await import() that tries the workspace path first and falls back to the pre-built _shared/parsers.bundle.mjs (already created by scripts/bundle-shared.cjs).

How tested

• npx tsx scripts/run-static-guards.ts — 17/17 checks pass (180s)
• npx vitest run scripts/lint-rules/__tests__/ — all lint rule tests pass (8 new for C2 promotion-warning rule, all existing tests unchanged)
• npx vitest run test/unit/tutorial-step-slicer*.test.js — 18/18 pass after D fix
• C3 is a doc-only change (no runtime behavior)

Deploy scope

Backend only (srv/* changes) + docs (docs/authors/). No approuter, no Hugo changes. No schema migrations. No feature flags — all changes are defensive (lint rules advisory-only, import fix fail-open).

C1/C2 lint rules: 'warning'/'notice' severity — they MUST NOT and DO NOT fail builds.
D: KG_STEP_SLICER_ENABLED defaults off in all environments; fix takes effect when the flag is enabled.