Manual rewrite combining the CI-driven release artifacts with fixes
the release pipeline missed and a fix for the GitHub Actions docs
workflow:

1. CHANGELOG.md NEXT_RELEASE_VERSION/NEXT_RELEASE_DATE placeholders
   stamped to [1.6.0] - 2026-05-22.
2. README.md version badge bumped 1.5.0 -> 1.6.0.
3. integ/constructs/package.json and installer/package.json bumped to
   1.6.0 (lerna --force-publish missed them; they're not in
   release_version_package's artifact list).
4. .kiro/steering/module-creation.md example versions updated to 1.6.0.
5. .gitlab-ci.yml: cornerstone_build_distributions, cornerstone_package_artifact,
   and cornerstone_upload now exclude CI_GROUP_TOKEN-triggered pipelines,
   matching every other release job's pattern. Without this, the
   post-prerelease-push pipeline failed graph validation because
   release_version_package was excluded but the cornerstone jobs
   referenced it via needs:.
6. .github/workflows/docs.yml: replace the deleted scripts/generate_docs.sh
   invocation with the three modular scripts that replaced it
   (prepare.sh, typedocs.sh, mkdocs.sh). The original monolithic script
   was split into scripts/generate_docs/ during the script refactor but
   the GitHub Actions workflow was never updated, breaking the
   Publish Documentation workflow on release. Per-package SCHEMA.md
   generation now happens in scripts/build/build_package.sh during
   lerna run build, so step 5 of the original script (schema-docs) is
   covered implicitly by the existing 'Build MDAA' workflow step.

Public-facing release files (CHANGELOG, README) and standalone packages
(installer, integ/constructs) are missing from release_version_package's
artifact paths, which is why version_release.sh stamps them in CI but
push_git_prerelease.sh's fresh git checkout reverts those changes before
the commit. Worth a follow-up to add them to the artifact list and the
two standalone packages to lerna's bumping strategy.