Last ned code-a-cv 0.3.0

Release Notes
- Test WinGet installation, command discovery, PDF generation, and uninstall on Windows; use an explicit output directory when testing older releases.
- Add opt-in WinGet update PR automation for voxvanhieu.code-a-cv, with Windows release smoke tests and initial submission instructions.
- Rewrite the contribution guide as a first-PR quick start and document branch naming prefixes and issue/PR label usage.
- Automatically start npm publication and Homebrew formula PR creation after stable releases; support the first npm publish in CI with a temporary token.
- Add npm packaging for npx @voxvanhieu/code-a-cv, native macOS release archives
for Apple Silicon and Intel, and a cross-platform tested npm publication workflow.
- Restore the PR check requiring contributions under themes/ to exclude files outside that directory.
- Rename cac fmt --check to --dry-run; formatting now writes files by default, removing the need for --write. Stdin continues to produce stdout.
- Make cac fmt preserve the source type and Markdown style, support JSON/YAML/TOML, and resolve the project root from settings. YAML/TOML formatting may remove comments.

Section metadata and theme extensibility
- Accept Kind: and Id: below Markdown section headings; Markdown conversion
emits these readable fields while continuing to accept legacy annotations.
- Preserve theme-defined section kinds in Markdown, JSON, YAML, TOML, and the
shared theme view. Unrecognized categories use custom entries and generic
layouts; themes can specialize by kind or ID without rebuilding the CLI.
- Rust API: SectionKind now includes Named(String) and no longer implements
Copy. Unknown valid section identifiers are accepted rather than rejected.

Added
- Add explicit Markdown profile/entry fields, mixed entry kinds, repeated section titles, multiline prose, nested and ordered lists, labeled contacts, single event dates, and unknown date endpoints
- Add cac fmt with content-preserving output, default in-place writing and --dry-run, plus cac check --explain
- Document Markdown authoring and provide editor snippets and a richer shared-theme fixture
- Enriched the default CV used by cac init and cac theme init with full contacts, a summary, multiple roles, and detailed project, publication, skill, and advisory examples
- Added a shared theme contract with complete CV fields, structured linked contacts, reusable flow/table/label helpers, and shared classic composition at /.cac/base.typ
- Added cac theme test --shared with content, order, and link checks across a bundled reusable-theme corpus
- Added optional Markdown section annotations for explicit IDs and semantic kinds, including semantic export and line diagnostics
- Added cac theme init, cac theme test, and cac theme pack for scaffolding, validating, previewing, hashing, and reproducibly packaging project-local themes
- Added the themeProject project marker, settings validation, and protections for the active development theme
- Added configurable build artifact naming through the naming setting
- Restored cac schema to synchronize the project-local settings schema and validate settings.json
- Made cac init and cac build keep .cac/settings.schema.json synchronized with the running binary

Fixed
- Preserve summaries, punctuation, entry metadata, tags, and kinds in Markdown conversion; reject unsupported content and lossy conversions before writing
- Render locations, project/publication URLs, and publication dates in HTML as well as PDF
- Reject silently discarded skill dates and publication ranges, and malformed or unsupported JSON Resume input fields
- Limit classic theme date columns to entry titles so descriptions and highlights use the full width below
- Preserve locations and standalone project/publication URLs in PDFs, and use complete fallback for mixed table sections
- Allow oversized shared entries to continue across pages
- Reject unsafe theme paths, symlinked development directories, and manifests that hash themselves
- Escape theme README metadata as literal text and verify the complete packaged file inventory
- Validate theme initialization arguments before prompting and protect dangling targets from writes
- Stage generated theme artifacts without rewriting sources and clean up temporary ZIPs on failure
- Require a selected theme in the settings schema when themeProject is present

Changed
- Make missing contact details advisory; allow optional organizations and institutions to be omitted in all native formats
- Infer Markdown section kinds only from documented conventional titles; use an explicit section annotation for other titles previously matched by English substrings
- Preserve omitted JSON Resume period endpoints as unknown instead of inferring Present; reject JSON Resume exports that cannot preserve the complete CV
- Extend shared rich nodes with paragraphs, breaks, and lists, add prose entries, and project ordered entry content into description metadata; shared themes must pass the expanded corpus
- Remove theme version declarations and checks; themes use the shared CV data and styling contract, with defaults for omitted override dictionaries
- Renamed the cac themes command to cac theme
- Made generated settings reference .cac/settings.schema.json for editor validation and completion
- Grouped rendering settings under page, typography, style, spacing, and pagination while keeping root and theme at the top level
- Generate the project-local settings schema from the internal Rust model instead of tracking a standalone schema file
- Rename the default generated-document directory from dist/ to offering/
- Move the runnable example projects under docs/examples/

Install cac 0.3.0

Install prebuilt binaries via shell script
curl --proto '=https' --tlsv1.2 -LsSf https://github.com/voxvanhieu/code-a-cv/releases/download/v0.3.0/cac-installer.sh | sh

Install prebuilt binaries via powershell script
powershell -ExecutionPolicy Bypass -c "irm https://github.com/voxvanhieu/code-a-cv/releases/download/v0.3.0/cac-installer.ps1 | iex"

Install prebuilt binaries into your npm project
npm install @voxvanhieu/code-a-cv@0.3.0

Download cac 0.3.0
─────────────────────────────────────────┬───────────────────┬─────────────
File │Platform │Checksum
─────────────────────────────────────────┼───────────────────┼─────────────
cac-aarch64-apple-darwin.tar.xz │Apple Silicon macOS│checksum
─────────────────────────────────────────┼───────────────────┼─────────────
cac-x86_64-apple-darwin.tar.xz │Intel macOS │checksum
─────────────────────────────────────────┼───────────────────┼─────────────
cac-x86_64-pc-windows-msvc.zip │x64 Windows │checksum
─────────────────────────────────────────┼───────────────────┼─────────────
cac-aarch64-unknown-linux-gnu.tar.xz │ARM64 Linux │checksum
─────────────────────────────────────────┼───────────────────┼─────────────
cac-x86_64-unknown-linux-gnu.tar.xz │x64 Linux │checksum
─────────────────────────────────────────┴───────────────────┴─────────────

Verifying GitHub Artifact Attestations
The artifacts in this release have attestations generated with GitHub Artifact Attestations. These can be verified by using the GitHub CLI:
gh attestation verify <file-path of downloaded artifact> --repo voxvanhieu/code-a-cv
You can also download the attestation from GitHub and verify against that directly:
gh attestation verify <file-path of downloaded artifact> --bundle <file-path of downloaded attestation>