character-wizard-cli 0.5.1

Native level-1 SRD character creation CLI
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58

# Releasing character-wizard

character-wizard follows Semantic Versioning. The crate version, lockfile,
Git tag, executable version, changelog heading, and release title must agree.

## Release checklist

1. Confirm the Quality, Dependency Audit, and Native binaries workflows pass on
   the exact release commit.
2. Update the package version in `Cargo.toml`, refresh `Cargo.lock` if
   needed, and update `docs/roadmap.md` plus `CHANGELOG.md`.
3. Run the complete local gate:

   ```console
   cargo +1.88.0 fmt --check
   cargo +1.88.0 clippy --all-targets -- -D warnings
   cargo +1.88.0 test --locked
   cargo +1.88.0 audit
   cargo +1.88.0 deny check
   cargo +1.88.0 build --release --locked
   target/release/character-wizard --version
   ```

4. Smoke-test `validate`, `show`, and `create --from-json` with the supported
   development template. Confirm the optimized executable contains no PDF fixture.
5. Commit and push the release changes. After all commit workflows pass, create
   and push an annotated tag:

   ```console
   git tag -a vX.Y.Z -m "character-wizard X.Y.Z"
   git push origin vX.Y.Z
   ```

The tag-triggered Native binaries workflow rebuilds and smoke-tests Linux x86-64,
Windows x86-64, macOS ARM64, and macOS x86-64 binaries, creates archives and
SHA-256 files, and publishes the existing tag through a GitHub Release.

If publication fails after a successful tag build, recover without moving the tag:

```console
gh workflow run "Native binaries" --ref main -f release_tag=vX.Y.Z
```

If an authenticated release push does not create workflows, manually dispatch
`Quality`, `Dependency Audit`, and `Native binaries` on the unchanged default
branch. Verify that every run uses the exact release commit before tagging.
Workflow concurrency includes the commit SHA so delayed events for an older
commit cannot cancel verification of a newer release commit.

Audit every release for four archives and four matching checksum files, correct
version output, and absence of the SRD and character-sheet PDFs.

## Signing and notarization

Native binaries remain unsigned. Do not describe them as trusted merely because
they came from GitHub; users should verify SHA-256 first. Authenticode and Apple
Developer ID signing/notarization remain deferred until project credentials are
available.