release: v0.1.0

[RyanAlberts]

What

The terminal Phase 1 PR. Bumps 0.0.1 → 0.1.0, finalizes CHANGELOG, ships a PyPI Trusted-Publishing release workflow, and updates the README quickstart to the actual v0.1 commands.

Closes #5.

What's in 0.1.0

Layer	Status
Repo bootstrap, secrets hygiene, CI	✅ Phase 0
Scraper + sanitizer + coverage probe	✅ PR #6
LLM enrichment + anti-hallucination Layer 1	✅ PR #7
Enriched dashboard + cited-URL publish gate	✅ PR #8
Resilience + parser tightening (0% schema-failure rate)	✅ PR #9
Release plumbing (this PR)	✅

103 tests passing. Mypy --strict clean. make publish-check clean.

Local smoke (already done)

python -m build
# -> dist/yc_ai_pulse-0.1.0-py3-none-any.whl  (38 KB)
# -> dist/yc_ai_pulse-0.1.0.tar.gz             (134 KB)

pipx install --force dist/yc_ai_pulse-0.1.0-py3-none-any.whl
ycai version
# yc-ai-pulse 0.1.0

cd /tmp/clean-dir
ycai run-coverage --batch winter-2026 --yc-official-count 196 --skip-link-check
# headline: 63.3% of Winter 2026 analyzed (124 of 196 companies)

PyPI publish — one-time setup needed

The release workflow uses PyPI Trusted Publishing, which needs a one-time configuration on the PyPI side:

1. Go to https://pypi.org/manage/account/publishing/
2. Add a new pending publisher:
   • PyPI Project Name: yc-ai-pulse
   • Owner: RyanAlberts
   • Repo name: yc-ai-pulse
   • Workflow filename: release.yml
   • Environment name: pypi
3. Optionally also configure on TestPyPI for dry-run testing.

Until that's done, the publish job in release.yml will fail; the github-release job still uploads the built wheels to the GitHub release. Re-running the workflow after PyPI setup will publish.

Release sequence (after this PR merges)

git checkout main && git pull
git tag -a v0.1.0 -m "v0.1.0"
git push origin v0.1.0
# release.yml fires: build → publish (if Trusted Publishing configured) → attach to GitHub release
gh release create v0.1.0 --generate-notes --title "v0.1.0"

After release: close v0.1 milestone, promote B007 to a v0.2 issue, open v0.2 milestone.

Backlog status at release

ID	Status
B001	resolved (PR #6 ADR amend)
B002	open — yc-oss caching headroom check
B003	open — Node 20 → Node 24 deadline 2026-06-02
B004	open — calibrate MIN_DESCRIPTION_CHARS
B005	open — name missing-from-upstream W26 companies
B006	resolved (PR #9)
B007	open — depth=1 website crawl for tech_stack / oss_posture. Biggest signal lever for v0.2.
B008	resolved (PR #9)

Acceptance

• python -m build produces a clean wheel + sdist
• pipx install works, ycai version returns 0.1.0
• ycai run-coverage succeeds end-to-end from a clean dir
• release.yml configured for PyPI Trusted Publishing
• CHANGELOG.md reflects 0.1.0
• All Phase 1 acceptance gates from the plan green
• make publish-check clean
• BACKLOG groomed; surviving items will move to v0.2 issues post-merge

🤖 Generated with Claude Code

[gemini-code-assist]

Code Review

This pull request prepares the project for its first publishable release, version 0.1.0. Key changes include updating the version across the codebase, documenting the Phase 0 and Phase 1 milestones in the changelog, and refreshing the README with updated quickstart instructions and status tables. Feedback suggests using generic date placeholders in the README command examples to avoid user confusion.

[gemini-code-assist]

The placeholder date in the example command '2026-05-01' should be replaced with a generic placeholder or variable to avoid confusion for users running this command on different dates.

Suggested change

	ycai resume runs/2026-05-01-XXXXXX
	ycai resume runs/YYYY-MM-DD-XXXXXX

[gemini-code-assist]

The placeholder date in the example command '2026-05-01' should be replaced with a generic placeholder or variable to avoid confusion for users running this command on different dates.

Suggested change

	ycai dashboard runs/2026-05-01-XXXXXX
	ycai dashboard runs/YYYY-MM-DD-XXXXXX