docs: remove CHANGELOG.md and changelog workflow

.github/workflows/dependency-submission.yml

@@ -14,14 +14,11 @@ permissions:
 jobs:
   dependency-submission:
     runs-on: ubuntu-latest
-    # Quote as a block scalar so the colon in "chore: update build number"
-    # is not parsed as YAML mapping syntax (line 17 syntax error).
     if: |
       github.event_name != 'push' ||
       (
         !contains(github.event.head_commit.message, 'Dependency Submission') &&
-        !contains(github.event.head_commit.message, '[skip ci]') &&
-        !contains(github.event.head_commit.message, 'chore: update build number')
+        !contains(github.event.head_commit.message, '[skip ci]')
       )
 
     steps:

AGENTS.md

@@ -25,11 +25,8 @@ This file provides guidance for AI agents operating in the Percussion CMS codeba
   3. Include issue number in branch name (e.g., `bugfix/123-fix-logging`)
 - All changes must be tested locally before pushing
 - On every pull request:
-  1. Do NOT manually increment the `buildNumber` in `Version.properties` files (e.g., in `system/VersionControl/Version.properties`). This is automatically handled by a GitHub Actions workflow upon merge.
-  2. A corresponding changelog entry must be written to the repository `CHANGELOG.md` file.
-     - The changelog entry header must use the placeholder `GH_POST_PR_COMMIT_RUN_ID` for the build number (e.g., `## [8.1.7 Build GH_POST_PR_COMMIT_RUN_ID] - YYYY-MM-DD`).
-     - The changelog must follow the [Common Changelog](https://common-changelog.org/) format.
-     - When the PR is merged into `main`, the workflow will automatically replace the `GH_POST_PR_COMMIT_RUN_ID` placeholder with the correct sequential build number.
+  1. Do NOT add or edit a repository `CHANGELOG.md`. That file is removed; per-PR changelog inserts were serializing every merge.
+  2. Do NOT edit `Version.properties` `buildNumber` on a feature PR.
 
 ## Build Commands
 

CHANGES.md

@@ -6,7 +6,7 @@ This file documents changes that have been made to API's / public interfaces.
 
 ### Editor decoration region grid
 
-See `CHANGELOG.md` (issue #2, 8.1.7 entry) for the full product / support note, including the temporary customer theme override snippet for sites already on 8.1.7+.
+See issue #2 (8.1.7) for the full product / support note, including the temporary customer theme override snippet for sites already on 8.1.7+.
 
 ### Test / Debug Tools
 

docs/ai-generated/tasks/8.1.x-codeql-baseline/codeql-pr-playbook.md

@@ -26,8 +26,8 @@ Operational guide for closing CodeQL (Critical/High) alerts on the 8.1.x release
    built distribution tree.
 7. **Task 10** — `accepted-risks.md` with re-review dates for unfixable
    sinks.
-8. **Task 12** — `CHANGELOG.md` entries per family with the
-   `GH_POST_PR_COMMIT_RUN_ID` placeholder.
+8. **Task 12** — do **not** add a `CHANGELOG.md` entry. Document the
+   family in the PR body and in `clusters.md` / `suppressions.md` instead.
 9. **Task 13** — sign-off PR re-runs the pipeline and asserts zero
    Critical/High open.
 

modules/DesktopContentExplorer/src/main/resources/com/percussion/cx/Version.properties

@@ -44,7 +44,7 @@ microVersion=${parsedVersion.incrementalVersion}
 # release build is created.
 buildId=${buildId}
 
-# The build number, which is automatically updated by a GitHub Actions workflow upon merge.
+# The build number for this release line.
 buildNumber=${buildNumber}
 
 # This is a monotonically increasing value that is only incremented when

system/VersionControl/Version.properties

@@ -44,7 +44,7 @@ microVersion=${parsedVersion.incrementalVersion}
 # release build is created.
 buildId=${buildId}
 
-# The build number, which is automatically updated by a GitHub Actions workflow upon merge.
+# The build number for this release line.
 buildNumber=${buildNumber}
 
 # This is a monotonically increasing value that is only incremented when