Refine public validation documentation

README.md

@@ -115,7 +115,8 @@ clearly labeled limited-evidence report but will not invent time totals.
 See [PRIVACY.md](PRIVACY.md) for the data-handling rules and
 [CONTRIBUTING.md](CONTRIBUTING.md) for development checks. Planned improvements
 are listed in [ROADMAP.md](ROADMAP.md). Maintainers can reuse the
-[launch kit](PROMOTION.md) for privacy-accurate project announcements.
+[launch kit](PROMOTION.md) for privacy-accurate project announcements. Public
+product updates are recorded in [docs/CHANGELOG.md](docs/CHANGELOG.md).
 
 ## License
 

ROADMAP.md

@@ -1,13 +1,24 @@
 # Roadmap
 
-## v0.2
+## Released In v0.2.0
 
 - Weekly, monthly, and custom-range reports with trends, projects, categories,
   and billable-time totals.
 - Local JSON attribution rules that operate on sanitized titles only.
 - Customer-timesheet, weekly-review, and app-trend templates.
 - GitHub Pages landing page and privacy-first design-partner research.
 
+## Validation Now
+
+- Invite independent consultants, freelancers, creators, and developers through
+  GitHub Discussions without collecting email addresses or activity records.
+- Publish a short public update every two weeks in
+  [`docs/CHANGELOG.md`](docs/CHANGELOG.md): feedback themes, decisions, and
+  the next validation question.
+- Use the evidence thresholds in
+  [`docs/VALIDATION_SCORECARD.md`](docs/VALIDATION_SCORECARD.md) before
+  designing a paid Pro trial.
+
 ## Future Exploration
 
 - Additional local time-trackers through explicit adapters, without weakening

docs/CHANGELOG.md

@@ -0,0 +1,28 @@
+# Public Changelog
+
+This is a privacy-safe product and validation log. It records decisions and
+feedback themes, never ActivityWatch events, window titles, URLs, account
+names, local paths, or behavioral telemetry.
+
+## 2026-07-26 - v0.2.0 Launch And Validation Setup
+
+### Shipped
+
+- Released local project, category, client, billable-time, weekly, monthly,
+  and custom-range reports in v0.2.0.
+- Published a bilingual GitHub Pages landing page with a fully synthetic report
+  preview and no analytics, tracking pixel, or email form.
+- Opened GitHub Discussions for design partners, use cases, and feature votes.
+
+### Decision
+
+- Keep the free core local, open source, account-free, and unlimited.
+- Do not add payment, cloud sync, team monitoring, advertising, or activity
+  telemetry during validation.
+
+### Next Validation Question
+
+Which private report is used repeatedly enough to justify a paid local Pro
+trial: client timesheets, personal weekly reviews, or long-term app trends?
+
+See [VALIDATION_SCORECARD.md](VALIDATION_SCORECARD.md) for the evidence gate.

docs/DESIGN_PARTNERS.md

@@ -5,12 +5,39 @@ creators, and developers who want better local work reviews.
 
 ## Join
 
-Open a GitHub Discussion using one of these titles. Do not include raw
+Open a GitHub Discussion with one of the templates below. Do not include raw
 ActivityWatch exports, window titles, URLs, account names, or local paths.
 
-- `Design partner: I want to test client timesheets`
-- `Use case: My weekly work review workflow`
-- `Vote: The report I would pay to save time on`
+### Join testing
+
+```text
+Title: Design partner: I want to test local work reviews
+
+I am a [consultant / freelancer / creator / developer].
+The report I would test is [client timesheet / weekly review / app trend].
+I would use it [how often] because [high-level workflow].
+My non-negotiable privacy boundary is [boundary].
+```
+
+### Share a use case
+
+```text
+Title: Use case: My weekly work review workflow
+
+Today I reconstruct my week by [high-level method].
+The hardest part is [problem].
+A private local report would help if it showed [outcome].
+```
+
+### Vote on a feature
+
+```text
+Title: Vote: The report I would pay to save time on
+
+My first choice is [client timesheet / weekly review / app trend / other].
+I would use it [frequency].
+The result that would save me time is [outcome].
+```
 
 ## Questions