Carried locally by GG Forge as definition-rename.patch (development pin 0.1.0-forge.ee782b7d6ea8-rename1). Upstreaming it so a published release can carry the change and Forge can drop that pin.
Change
DocumentDefinitionService.rename(table, id, name) plus native authoring actions document_generation_{type,stock,template}_author_rename ("Rename"). The form loads the current name and saves only the trimmed name: nonblank, at most 200 characters, no control characters.
document-generation.configure is checked at discovery/preparation and again at save; credential/channel write ceilings still apply. Native UpdateAction keeps the host's field-level audit.
GenerationStore.update admits an id+name-only write for type and stock rows; geometry, bindings, drafts, published revisions and queued pins remain immutable. No schema change.
Prepare-step selection message generalised from "document template" to "document definition" since type/stock rows now use it.
Docs: docs/AUTHORING.md describes the action; README.md and docs/RELEASE-STATUS.md record the addition and verification. The repo keeps no CHANGELOG.
Verification
./mvnw -pl foundation -am verify on this branch (Java 21, wrapper, offline local repository): 232 tests, 0 failures/errors/skips, Checkstyle clean, JaCoCo gates met, including the Docker MySQL 8.4 and PostgreSQL 17 suites. Forge's prior evidence: 37 rename-related tests on H2, MySQL and PostgreSQL 17 (rename-linux-verify.log, rename-linux-db-verify.log).
Carried locally by GG Forge as `definition-rename.patch` (development pin `0.1.0-forge.ee782b7d6ea8-rename1`). Upstreaming it so a published release can carry the change and Forge can drop that pin.
## Change
- `DocumentDefinitionService.rename(table, id, name)` plus native authoring actions `document_generation_{type,stock,template}_author_rename` ("Rename"). The form loads the current name and saves only the trimmed name: nonblank, at most 200 characters, no control characters.
- `document-generation.configure` is checked at discovery/preparation and again at save; credential/channel write ceilings still apply. Native `UpdateAction` keeps the host's field-level audit.
- `GenerationStore.update` admits an id+name-only write for type and stock rows; geometry, bindings, drafts, published revisions and queued pins remain immutable. No schema change.
- Prepare-step selection message generalised from "document template" to "document definition" since type/stock rows now use it.
- Docs: `docs/AUTHORING.md` describes the action; `README.md` and `docs/RELEASE-STATUS.md` record the addition and verification. The repo keeps no CHANGELOG.
## Verification
`./mvnw -pl foundation -am verify` on this branch (Java 21, wrapper, offline local repository): 232 tests, 0 failures/errors/skips, Checkstyle clean, JaCoCo gates met, including the Docker MySQL 8.4 and PostgreSQL 17 suites. Forge's prior evidence: 37 rename-related tests on H2, MySQL and PostgreSQL 17 (`rename-linux-verify.log`, `rename-linux-db-verify.log`).
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Add DocumentDefinitionService.rename and the native authoring actions
document_generation_{type,stock,template}_author_rename. The form loads
the current name and saves only the trimmed name; names must be nonblank,
at most 200 characters and free of control characters. The configure
permission is checked at discovery and again at save, and the native
UpdateAction keeps the host's field-level audit. GenerationStore.update
now admits an id+name-only write for type and stock rows, so geometry,
bindings, drafts, published revisions and queued pins stay immutable.
No schema change.
Carried locally by GG Forge as definition-rename.patch (pin
0.1.0-forge.ee782b7d6ea8-rename1); upstreamed so a published release can
replace that pin. The prepare-step selection message is generalised to
cover type and stock rows. Docs: AUTHORING.md describes the action,
README and RELEASE-STATUS record the addition and its verification
(./mvnw -pl foundation -am verify: 232 tests, Checkstyle and coverage
gates met, including the Docker MySQL and PostgreSQL suites).
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Signed-off-by: James Maes <james@kof22.com>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Carried locally by GG Forge as
definition-rename.patch(development pin0.1.0-forge.ee782b7d6ea8-rename1). Upstreaming it so a published release can carry the change and Forge can drop that pin.Change
DocumentDefinitionService.rename(table, id, name)plus native authoring actionsdocument_generation_{type,stock,template}_author_rename("Rename"). The form loads the current name and saves only the trimmed name: nonblank, at most 200 characters, no control characters.document-generation.configureis checked at discovery/preparation and again at save; credential/channel write ceilings still apply. NativeUpdateActionkeeps the host's field-level audit.GenerationStore.updateadmits an id+name-only write for type and stock rows; geometry, bindings, drafts, published revisions and queued pins remain immutable. No schema change.docs/AUTHORING.mddescribes the action;README.mdanddocs/RELEASE-STATUS.mdrecord the addition and verification. The repo keeps no CHANGELOG.Verification
./mvnw -pl foundation -am verifyon this branch (Java 21, wrapper, offline local repository): 232 tests, 0 failures/errors/skips, Checkstyle clean, JaCoCo gates met, including the Docker MySQL 8.4 and PostgreSQL 17 suites. Forge's prior evidence: 37 rename-related tests on H2, MySQL and PostgreSQL 17 (rename-linux-verify.log,rename-linux-db-verify.log).🤖 Generated with Claude Code
Add DocumentDefinitionService.rename and the native authoring actions document_generation_{type,stock,template}_author_rename. The form loads the current name and saves only the trimmed name; names must be nonblank, at most 200 characters and free of control characters. The configure permission is checked at discovery and again at save, and the native UpdateAction keeps the host's field-level audit. GenerationStore.update now admits an id+name-only write for type and stock rows, so geometry, bindings, drafts, published revisions and queued pins stay immutable. No schema change. Carried locally by GG Forge as definition-rename.patch (pin 0.1.0-forge.ee782b7d6ea8-rename1); upstreamed so a published release can replace that pin. The prepare-step selection message is generalised to cover type and stock rows. Docs: AUTHORING.md describes the action, README and RELEASE-STATUS record the addition and its verification (./mvnw -pl foundation -am verify: 232 tests, Checkstyle and coverage gates met, including the Docker MySQL and PostgreSQL suites). Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Signed-off-by: James Maes <james@kof22.com>