docs: template exit-code prose, copyright step and bl_info rationale match the code

The template READMEs and CLAUDE.md said failures exit 2+ while their own
tables and code reserve 2 for argparse usage (#490). The extension template
README never told users to replace copyright, so following it shipped an
add-on credited to the template author, and its 'from inside Blender'
heading led into a shell command. The bl_info comment claimed a pre-manifest
fallback that its 4.5 floor makes impossible.

Closes #539

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01LpkeXRvikhJZSVGBFM91Dv
Signed-off-by: TM Hospitality Strategies <TMHospitalityStrategies@gmail.com>

Author: TMHSDigital

CLAUDE.md

@@ -105,7 +105,7 @@ matching its `globs` does. Changing a glob changes when the rule fires.
 - Import, unit-scale check, transform apply, origin, normals, evaluated tris
 - LOD chain and optional convex/box collider
 - Unity / Godot / Unreal glTF export via the engine-export-presets contract
-- Explicit exit codes matching `headless-batch-script-template` (0, then 2+)
+- Explicit exit codes matching `headless-batch-script-template` (0, then 3+; 2 is argparse usage only)
 
 ## Snippets (31)
 

templates/ai-asset-pipeline-template/README.md

@@ -73,8 +73,8 @@ header; templates are not a package.
 ## Exit codes
 
 Same convention as `templates/headless-batch-script-template/`
-(`script.py` / its README: 0 success, 2+ distinct failure modes;
-argparse usage errors also exit 2). Not a repo-wide table; examples such
+(`script.py` / its README: 0 success, 3 and up for distinct failure
+modes; 2 is argparse usage only). Not a repo-wide table; examples such
 as `export-preset-axis` number their own checks independently.
 
 | Code | Meaning |

templates/extension-addon-template/README.md

@@ -18,7 +18,10 @@ Targets Blender 4.5 LTS and 5.x.
    `id` (Python identifier, no hyphens) that is unique in your namespace.
 2. Edit `blender_manifest.toml`:
    - Change `id`, `name`, `tagline` (max 64 characters, no trailing
-     period), `maintainer`, `version`, and `website`.
+     period), `maintainer`, `version`, `website`, and `copyright` (it
+     ships as the template author's; put your own name and year).
+   - Review `license`: the template ships `SPDX:GPL-3.0-or-later`; the
+     Extensions Platform hosts add-ons only under GPL-compatible licenses.
    - Adjust `tags` to match your add-on's category. Allowed values come
      from the Extensions Platform tag list.
    - Set `blender_version_min` to the lowest Blender you actually
@@ -32,12 +35,10 @@ Targets Blender 4.5 LTS and 5.x.
 
 ## Install for development
 
-From inside Blender:
-
-1. Build a package from the template directory (it holds
+1. From a shell, build a package from the template directory (it holds
    `blender_manifest.toml`):
    `blender --command extension build --source-dir . --output-dir dist`
-2. Edit > Preferences > Get Extensions > the drop-down menu > Install from
+2. In Blender: Edit > Preferences > Get Extensions > the drop-down menu > Install from
    Disk, and pick the `.zip` in `dist/`. "Install from Disk" takes a `.zip`
    (or a `.py`), not a directory.
 3. Enable the add-on.

templates/extension-addon-template/__init__.py

@@ -12,9 +12,11 @@
 #     because the unregister_class call invalidates the type the binding
 #     points at.
 #
-# bl_info is kept alongside the manifest for backward compatibility with
-# Blender versions before manifests were honored. The manifest is the
-# source of truth.
+# bl_info is read only when the package is installed as a legacy add-on
+# (no manifest, for example dropped into scripts/addons) and is ignored when
+# it installs as an extension. Its "blender" floor is 4.5, so it does not make
+# the add-on load on Blender older than the manifest era either. The manifest
+# is the source of truth.
 
 bl_info = {
     "name": "Example Addon",

templates/headless-batch-script-template/README.md

@@ -37,8 +37,8 @@ it is forwarded to `script.py` as `sys.argv`.
    operator per object. The new modifier runs after any existing ones.
    Every modifier on the object is applied, not only the new one.
 4. Exports the scene to a `.glb` at the given output path.
-5. Returns explicit exit codes (0 success, 2-4 different failure modes)
-   so a CI pipeline can detect failures.
+5. Returns explicit exit codes (0 success, 3 and up for distinct failure
+   modes; 2 is argparse usage only) so a CI pipeline can detect failures.
 
 ## Exit codes