v4 ecosystem tasks — follow-up slices (build integration, MCP launch, CI/CD polish)

[raifdmueller]

Tracks the remaining slices from the now-implemented ecosystem tasks #57–#60 (walking skeletons shipped in #56). The install + agent-hint tasks, the lint runner and the pipeline scaffold are merged; these are the deferred follow-ups, each independently shippable as a thin vertical slice.

Bausteinsicht (from #58)

• bausteinsicht build task — run bausteinsicht sync to (re)generate the diagram exports into imageDirs during a docs build, so building-block views are reproducibly built rather than hand-exported.
• Prerequisite — PATH: ensure ~/.doctoolchain/bin is on PATH for task subprocesses (so a freshly installed bausteinsicht is found by the build), or invoke it by absolute path. installBausteinsicht already prints a PATH hint for interactive use.

daCLI (from #59)

• dacli runtime task — launch dacli-mcp --docs-root <inputPath> as a task so MCP clients can attach. Mind the long-running stdio lifecycle: pass stdio through cleanly, no task banners, verified through the dtcw4 → dtcw path.

lintAsciiDoc (from #57)

• Zero-install option — bundle/vendor the linter (container or pinned download) so no separate uv/pip step is needed (we shipped the shell-out + install-hint variant).
• Document the pre-commit hook integration.

generateCICD / CI-CD integration (from #60)

• Reusable workflow — publish a versioned GitHub Actions reusable workflow / composite action (and a GitLab include) so projects consume a pipeline instead of a copied file.
• Warm-cache speed validation — confirm the libs/JDK cache hit is measurably faster than a cold run.
• Refresh the CI/CD tutorial under src/docs/ and align/replace the ci-cd-demo repo the landing page links to.
• Optional: Confluence/Jira publishing from CI (with secret-handling guidance).

References

Implemented base: #56. Closed source issues: #57, #58, #59, #60.