Fix preview overlap and add launch assets

README.md

@@ -42,6 +42,8 @@ npx @focaxisdev/deja-vu init --dry-run
 npx @focaxisdev/deja-vu doctor
 ```
 
+![Deja Vu initializes and verifies the three-file memory setup](./docs/assets/deja-vu-terminal-demo.gif)
+
 Then start the next agent session with:
 
 > Follow AGENTS.md. Scan memory/impressions.jsonl before substantial work, load only the matching memory, and write back durable project context only.

docs/launch-copy.md

@@ -4,6 +4,11 @@ Use this copy only after the public npm quick start has been verified. Keep the
 
 Project URL: <https://github.com/focaxisdev/deja-vu>
 
+Launch assets:
+
+- social preview: [`docs/assets/deja-vu-social-preview.png`](./assets/deja-vu-social-preview.png)
+- terminal demo: [`docs/assets/deja-vu-terminal-demo.gif`](./assets/deja-vu-terminal-demo.gif)
+
 ## Short post
 
 I got tired of re-explaining the same repo to every new AI coding-agent session.
@@ -36,31 +41,29 @@ Quick start: `npx @focaxisdev/deja-vu init`
 
 <https://github.com/focaxisdev/deja-vu>
 
-## Show HN
-
-Title:
+## Show HN — human-written only
 
-> Show HN: Deja Vu – three-file project memory for AI coding agents
+Hacker News asks users not to post generated or AI-edited text. Do not paste launch copy from this file into an HN submission or comment. The maintainer should write the title and first comment from scratch, in their own words.
 
-First comment:
+Useful facts to verify while writing:
 
-> I built Deja Vu because coding agents kept losing the reasoning that lives between commits: rejected approaches, architecture intent, fragile workarounds, and unresolved follow-ups.
->
-> The minimum setup is `AGENTS.md`, `memory/summary.md`, and `memory/impressions.jsonl`. The impressions file is a tiny cue router: no match loads nothing, a weak match loads one summary, and a strong match loads one to three linked records. The agent writes back only durable context after the task.
->
-> It is intentionally a file convention first. The CLI only creates and checks those files; npm, embeddings, and the optional TypeScript engine are not required. I would especially value feedback on the three-file boundary, the recall budget, and whether the existing-AGENTS merge behavior feels safe.
+- the problem personally observed
+- why the minimum setup is three files
+- what `init` and `doctor` actually do
+- why the protocol avoids transcript archives, embeddings, and hosted storage
+- what specific design feedback would be useful
 
 ## GitHub release intro
 
 Deja Vu v0.7.0 makes the public quick start real: the npm package now includes the unified CLI and starter kit, while the protocol remains file-first and package-optional.
 
 This release adds safe merging for existing `AGENTS.md` files, stricter setup diagnostics, cross-platform onboarding, link validation, isolated package verification, and a clearer before/after product story.
 
-## Alternate titles
+## Non-HN launch angles
 
-- Show HN: Stop re-explaining your repo to every new coding-agent session
-- Show HN: Repo-local memory for Codex, Claude Code, Cursor, and Windsurf
 - Deja Vu: project memory that fits in a pull request
+- Stop re-explaining your repo to every new coding-agent session
+- Repo-local memory for Codex, Claude Code, Cursor, and Windsurf
 - Store less, recall better: a file-first memory protocol for coding agents
 
 ## Taglines

memory/impressions.jsonl

@@ -6,3 +6,4 @@
 {"schema_version":1,"id":"v060-release-readiness","scope":"project:deja-vu","title":"v0.6.0 release readiness","keywords":["v0.6.0","release","readiness","checklist","candidate"],"aliases":["release-candidate"],"record_path":"memory/summary.md","updated":"2026-08-09","weight":0.4,"status":"superseded","superseded_by":"v070-npm-release-gap"}
 {"schema_version":1,"id":"v070-npm-release-gap","scope":"project:deja-vu","title":"Publish and verify the first CLI-capable npm release","keywords":["v0.7.0","npm","publish","npx","latest","cli","release"],"aliases":["npm-release-gap","cli-release"],"record_path":"memory/open-loops/publish-v0.7.0.md","updated":"2026-08-09","weight":0.4,"status":"superseded","superseded_by":"v070-release-complete"}
 {"schema_version":1,"id":"v070-release-complete","scope":"project:deja-vu","title":"v0.7.0 public release is live and verified","keywords":["v0.7.0","npm","published","npx","latest","cli","github-release"],"aliases":["v070-released","cli-release-live"],"record_path":"memory/summary.md","updated":"2026-08-09","weight":0.85,"status":"active"}
+{"schema_version":1,"id":"v070-distribution-cycle","scope":"project:deja-vu","title":"Run the first focused v0.7.0 distribution cycle","keywords":["v0.7.0","launch","distribution","social-preview","demo","testers","adoption","feedback"],"aliases":["launch-cycle","early-adoption"],"record_path":"memory/open-loops/distribute-v0.7.0.md","updated":"2026-08-09","weight":0.85,"status":"active"}

memory/open-loops/distribute-v0.7.0.md

@@ -0,0 +1,43 @@
+---
+id: distribute-v0.7.0
+title: Run the first focused v0.7.0 distribution cycle
+status: active
+scope: project:deja-vu
+updated: 2026-08-09
+---
+
+# Run the First Focused v0.7.0 Distribution Cycle
+
+## Owner
+
+Repository maintainer.
+
+## Opened
+
+2026-08-09.
+
+## Next trigger
+
+Revisit after the GitHub social preview is live or the first external setup feedback arrives.
+
+## Why it matters
+
+The package and quick start are public and verified, but maintainers still need evidence that people outside the project understand the promise, complete setup, and find the memory boundary useful.
+
+## Prepared
+
+- A 1280 by 640 social preview is versioned with the repository.
+- A short terminal demo shows the real `init` and `doctor` flow.
+- Channel copy keeps the file-first promise precise.
+
+## Remaining work
+
+- Upload the social preview in GitHub repository settings.
+- Invite a small set of hands-on testers to try setup in real repositories.
+- Record where onboarding, existing `AGENTS.md` handling, or the three-file model causes confusion.
+- Use only human-written text for Hacker News submissions and comments.
+- Turn repeated feedback into narrowly scoped issues or the next release plan.
+
+## Done when
+
+The project has feedback from real external setups and enough evidence to choose the next product improvement without broadening the protocol speculatively.

memory/summary.md

@@ -39,6 +39,7 @@ Released on 2026-08-09, npm `latest` now resolves to v0.7.0 and exposes the unif
 ## Open loops
 
 - No v0.7.0 release blockers remain.
+- Run a focused distribution cycle and collect onboarding feedback from real external setups; see `memory/open-loops/distribute-v0.7.0.md`.
 
 ## Boundaries