Update documentation to reflect current workflow and command structure

- Fix CLAUDE.md to distinguish between generated project and cookiecutter repo workflows
- Update README.md workflow description to match actual release.yaml behavior
- Correct README section header from release.yml to release.yaml
- Ensure all poe commands and workflow descriptions are accurate and current

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <[email protected]>

Author: JnyJny

CLAUDE.md

@@ -88,10 +88,13 @@ Generated projects include comprehensive GitHub automation:
 
 **Workflows:**
 - `release.yaml` - Multi-stage CI/CD pipeline with matrix testing and PyPI publishing via trusted publishers
-- `github-release.yml` - Automatic GitHub release creation with changelog generation
+- `github-release.yml` - Automatic GitHub release creation with changelog generation  
 - `docs.yml` - GitHub Pages deployment for MkDocs documentation
 - `dependabot.yaml` - Automated dependency updates for Python packages and GitHub Actions
 
+**Cookiecutter Repository Workflows:**
+- `release.yaml` - Test validation and automatic GitHub release creation with changelog generation
+
 **Issue & PR Templates:**
 - Bug report template with structured fields
 - Feature request template

README.md

@@ -334,15 +334,14 @@ templates][github-templates]. You should edit them to reflect your
 projects needs and personality. You may want to uncomment and edit
 issue links in `config.yaml` if it suits your needs.
 
-### .github/workflows/release.yml
-
-The `release.yaml` workflow defines a matrix of operating systems and
-Python versions to test against. Tests are run when a [semantic
-versioning][semantic-version] tag or a tag with the suffix "-test" is
-pushed to a branch. If and when the requested tests complete
-successfully, the package will be built and published to PyPI, unless
-the triggering tag has a "-test" suffix in which case the workflow
-skips publishing.
+### .github/workflows/release.yaml
+
+The `release.yaml` workflow runs a fast test subset to validate core 
+functionality when a [semantic versioning][semantic-version] tag is 
+pushed. If tests pass successfully, it automatically creates a GitHub 
+release with generated release notes and changelog integration. This 
+ensures the cookiecutter template repository itself maintains quality 
+and provides automated release management.
 
 Tests are designed to be run against matrices of Operating System and
 Python version values. The matrices can be a list with a single item