profile-data-template v0.3.0 — first scaffold release (engine 0.3.0)

The first tagged release of the scaffold, for engine @profile-as-code/cli@0.3.0.

What you get

• A forkable data workspace: facts in content/*.yaml, per-platform texts
  rendered from them, and profiles/ committed as the deploy artifact.
• One source of truth: deterministic facts, drift/GEO checks, per-language
  variants (en essential, es native).
• Evidence registry (D17/§18): projects[].evidence[] for claims,
  content/credentials.yaml for third-party attestations, and
  content/artifacts.yaml for works — kept distinct, linked by id.
• Deploy ledger (D18): pasco status --mark records what was pasted where;
  pasco status --write-checklist regenerates CHECKLIST.md.
• Automation: build.yml installs the pinned engine and commits profiles/
  in user workspaces; it refuses in this template (fail-closed is_template
  guard).
• Docs: start flow, CONTRIBUTING (setup, CI, releases, fork re-sync),
  per-platform checklist, evidence packs, and symlink/stow tradeoffs.

Start

gh repo create profile-data-<username> \
  --template ChristianLuciani/profile-data-template \
  --private

Then edit content/, run pasco validate + pasco check + pasco build, and
deploy. Full flow in the README.

Notes

• Engine pin: @profile-as-code/cli@0.3.0; Node 22+.
• .pascorc uses diff.tagPattern: v* so pasco diff finds this release tag.
• Publication hardening landed right after this tag (SECURITY.md, private
  disclosure, SHA-pinned actions, secret scan, template privacy guard,
  English/Spanish README). It is on main; the next scaffold release is
  v0.3.1.

Full history: CHANGELOG.md.