[launch] Public launch execution checklist

[Seven128]

This tracks the external steps for the renamed Project Tiny Context Harness launch. The goal is to make the project discoverable without claiming unproven benchmark wins.

Pre-launch

• Merge launch-readiness changes into main.
• Rename GitHub repository to Seven128/project-tiny-context-harness.
• Set GitHub repository description to: Minimal project memory and validation harness for AI coding agents.
• Set GitHub topics from docs/launch/README.md.
• Confirm GitHub detects the MIT license from the default branch.
• Push the Project Tiny Context Harness rename commit to main.
• Add repo-hosted social preview asset: docs/launch/assets/social-preview.png.
• Upload docs/launch/assets/social-preview.png as the GitHub repository social preview image.
• Publish project-tiny-context-harness@0.2.41 so npm picks up the renamed README, license, homepage, repository, bugs and keywords metadata.
• Run npm run launch:strict-external after npm publish and clear all blocking external metadata issues.
• Publish the GitHub Release for Project Tiny Context Harness 0.2.41.

Demo and first post

• Record or refresh the 60-90 second demo from docs/launch/README.md#demo-storyboard ([launch] Record the 60-90s recovery demo #5).
• Create and pin an issue for adoption reports and missing recovery facts ([launch] Share adoption reports and missing recovery facts #4).
• Create starter issues for docs/demo/example/benchmark work ([launch] Record the 60-90s recovery demo #5, [docs] Expand the fresh-agent recovery walkthrough into a complete sample #6, [benchmark] Rerun Minimal Context delivery benchmark #7, [docs] Add launch FAQ from first-user feedback #8).
• Add SECURITY.md, Dependabot and an adoption-report issue template.
• Add a fresh-agent recovery walkthrough linked from README.
• Post the primary launch: https://news.ycombinator.com/item?id=48479619
• Post the first regular HN comment with the maintainer context after action-time confirmation.
• Track 6-hour and 24-hour metrics, then update copy from real feedback before posting elsewhere.

Evidence to collect

• npm download trend after publish.
• Stars/forks after each launch venue.
• Issues or comments showing real fresh-agent recovery value.
• Confusion points that require README/FAQ updates.

Current baseline after Show HN submission and issue #5 cleanup:

• GitHub stars: 0
• GitHub forks: 0
• GitHub open issues/PRs: 7
• Renamed npm latest: 0.2.41
• Renamed npm downloads last week: TODO while npm downloads API still returns 404 for the new package window
• Legacy npm downloads last week: 3573

Boundary: do not claim benchmark-proven delivery speed until fresh Minimal Context benchmark runs exist.

[Seven128]

Launch outreach planning is now tracked in-repo at docs/launch/outreach-targets.md on main (af31d24). It updates the post-publish public state, prioritizes Show HN/Product Hunt/curated-list/award targets, and keeps awards gated behind demo plus real feedback.

Current next action remains #5: record the 60-90 second recovery demo, then use docs/launch/outreach-targets.md to choose one primary launch venue before cross-posting.

[Seven128]

Launch execution packets are now on main in 6731b34.

Added:

• docs/launch/primary-launch.md with copy-ready Show HN text, Product Hunt follow-up packet, response playbook, claims boundary, and adoption issue link.
• docs/launch/awesome-list-submissions.md with PR-ready copy for Transcenda/awesome-agentic-coding and jordimas/awesome-agentic-engineering, plus deferred gates for broader lists.
• launch_readiness_check.mjs now checks both packets so the launch surface cannot drift silently.

Validation passed:

• node --test tests/sdlc-harness/launch-readiness-script.test.mjs
• npm run launch:check
• node tools/launch_readiness_check.mjs --strict-external
• make validate-context
• git diff --check

Current external baseline from strict check remains: GitHub stars 0, forks 0; npm latest 0.2.39; npm downloads last week 3573.

Next execution order:

1. Record/upload the demo from [launch] Record the 60-90s recovery demo #5.
2. Post Show HN using docs/launch/primary-launch.md.
3. Submit the two P0 agentic-coding awesome-list PRs using docs/launch/awesome-list-submissions.md.
4. Defer Product Hunt until there is a public demo GIF/video and two gallery images.
5. Defer awards until there is first external feedback/adoption evidence, except a low-cost The Commits docs/design nomination if timing becomes urgent.

[Seven128]

Launch media packet is now ready on main in 65770bb.

What changed:

• Root README and package README embed a short demo GIF.
• docs/launch/demo.md now points to repo-hosted demo media instead of a placeholder-only state.
• Product Hunt prep now has two 1270x760 gallery images and a 240x240 thumbnail.
• launch_readiness_check.mjs validates the media files, dimensions and README references.

Current next execution order:

1. Post Show HN using docs/launch/primary-launch.md; use the GIF if useful.
2. Submit the two P0 agentic-coding awesome-list PRs from docs/launch/awesome-list-submissions.md.
3. Track stars/forks/npm downloads/comments for 24h.
4. Patch README/FAQ from repeated confusion.
5. Use Product Hunt only after the first feedback loop or with a deliberate scheduling decision.

Strict external baseline remains: GitHub stars 0, forks 0; npm latest 0.2.39; npm downloads last week 3573.

[Seven128]

Launch execution update (2026-06-10)

Completed in 3c619e6:

• Added exact external PR packets under docs/launch/external-prs/ for:
  • Transcenda/awesome-agentic-coding
  • jordimas/awesome-agentic-engineering
• Updated docs/launch/awesome-list-submissions.md and docs/launch/outreach-targets.md to point to the exact patches, PR titles, PR bodies and manual gh commands.
• Extended tools/launch_readiness_check.mjs and its test so launch readiness now verifies these external PR packets.

Validated:

• node --test tests/sdlc-harness/launch-readiness-script.test.mjs
• npm run launch:check
• node tools/launch_readiness_check.mjs --strict-external
• git diff --check
• make validate-context
• node packages/sdlc-harness/dist/cli.js package check-source
• npm test --workspace agent-project-sdlc

External PRs were not opened automatically because gh is not installed locally, the GitHub connector has pull-only permission on both upstream repositories, and no Seven128 fork exists for either upstream. The packet is ready for a maintainer-authenticated PR submission.

Current public metrics from strict readiness remain: GitHub stars 0, forks 0, npm latest 0.2.39, npm downloads last week 3573.