Hide launch kit from public surface

CHANGELOG.md

@@ -2,6 +2,11 @@
 
 ## Unreleased
 
+- Hid maintainer launch-material generation from the public CLI reference and
+  Makefile so Falsiflow's visible surface stays focused on claim gates,
+  evidence import, release checks, and reusable CI workflows.
+- Removed launch-kit generation from `release-check`; public launch copy,
+  social posts, and launch metrics are no longer release readiness gates.
 - Reduced public issue queue and launch execution docs so GitHub issues remain
   the source of truth instead of mirroring every closed seed issue.
 - Relaxed release-check coverage for narrative launch docs while keeping the

Makefile

@@ -1,4 +1,4 @@
-.PHONY: install-local pipx-install pipx-start start start-check onboard-check static-demo demo-package publish-kit launch-kit external-evidence external-check release-proof cli-reference casebook-check test release-check clean
+.PHONY: install-local pipx-install pipx-start start start-check onboard-check static-demo demo-package publish-kit external-evidence external-check release-proof cli-reference casebook-check test release-check clean
 
 PYTHON ?= python3
 FALSIFLOW_OUT ?= falsiflow_start
@@ -30,9 +30,6 @@ demo-package: install-local
 publish-kit: install-local
 	falsiflow publish-kit --out-dir falsiflow_publish_kit --force
 
-launch-kit: install-local
-	falsiflow launch-kit --out-dir falsiflow_launch_kit --force
-
 external-evidence: install-local
 	falsiflow external-evidence --out falsiflow_external_evidence.json --force
 

RELEASE.md

@@ -87,7 +87,6 @@ python3 scripts/falsiflow.py onboard --out-dir /tmp/falsiflow_onboard_check --ch
 python3 scripts/falsiflow.py static-demo --out-dir /tmp/falsiflow_static_demo_check --force --json
 python3 scripts/falsiflow.py demo-package --out-dir /tmp/falsiflow_public_demo_check --force --json
 python3 scripts/falsiflow.py publish-kit --out-dir /tmp/falsiflow_publish_kit_check --force --json
-python3 scripts/falsiflow.py launch-kit --out-dir /tmp/falsiflow_launch_kit_check --force --json
 python3 scripts/falsiflow.py external-evidence --out /tmp/falsiflow_external_evidence.json --force --json
 python3 scripts/falsiflow.py external-check --out-dir /tmp/falsiflow_external_check --force
 python3 scripts/falsiflow.py evidence import --profile local-llm-eval --input examples/local_llm_eval_import/falsiflow_local_llm_eval/source_files/local_eval_results.jsonl --manifest examples/local_llm_eval_import/falsiflow_local_llm_eval/local_model_manifest.json --out /tmp/falsiflow_local_llm_evidence.csv --summary-out /tmp/falsiflow_local_llm_import_summary.json --config examples/local_llm_eval_import/falsiflow_local_llm_eval/project.json --coverage-out /tmp/falsiflow_local_llm_import_coverage.json --source-file source_files/local_eval_results.jsonl --strict --json
@@ -105,8 +104,6 @@ The final `release-check` must report:
 - `dist_ready`
 - `demo_package_ready`
 - `publish_kit_ready` for the generated release handoff kit
-- `launch_kit_ready` for public copy, proof card, demo script, launch metrics,
-  and maintainer checklist
 - `downstream_smoke_replay_ready`, proving the maintained downstream AI eval,
   product metric, and RAG eval fixtures replay as placeholder
   `claim_check_blocked` and source-backed `claim_check_ready` with
@@ -228,20 +225,6 @@ Inspect these generated files before publishing:
 - `data/falsiflow/release_check/publish_kit/release_rehearsal.md`
   for the public release rehearsal commands, expected artifacts, success
   signals, and strict external stop conditions
-- `data/falsiflow/release_check/launch_kit/launch_summary.json`
-- `data/falsiflow/release_check/launch_kit/proof_card.md`
-- `data/falsiflow/release_check/launch_kit/announcement.md`
-- `data/falsiflow/release_check/launch_kit/demo_script.md`
-- `data/falsiflow/release_check/launch_kit/readme_proof_strip.svg`
-- `data/falsiflow/release_check/launch_kit/social_preview.png`
-- `data/falsiflow/release_check/launch_kit/social_preview.svg`
-- `data/falsiflow/release_check/launch_kit/github_repo_profile.md`
-- `data/falsiflow/release_check/launch_kit/launch_posts.md`
-- `data/falsiflow/release_check/launch_kit/launch_metrics.json`
-- `data/falsiflow/release_check/launch_kit/launch_metrics.md`
-- `data/falsiflow/release_check/launch_kit/maintainer_checklist.md`
-- `data/falsiflow/release_check/launch_kit/publish_kit/public_release_evidence.md`
-- `data/falsiflow/release_check/launch_kit/publish_kit/release_rehearsal.md`
 - `data/falsiflow/release_check/publish_kit/external_evidence_template.json`
 - `data/falsiflow/release_check/external_readiness/external_readiness.json`
 - `data/falsiflow/release_check/external_readiness/external_readiness.md`

docs/falsiflow_adoption_priorities.md

@@ -70,9 +70,6 @@ The current track is adoption readiness:
 - A public release rehearsal generated by `publish-kit` that records the ordered
   preflight commands, expected artifacts, success signals, and stop conditions
   before any announcement can claim external readiness.
-- A `launch-kit` command that writes public copy, a demo script, proof card,
-  launch metrics tracker, maintainer checklist, and nested publish handoff for
-  pre-launch review.
 - A structured `external-evidence` file and `external-check --evidence` path so
   hosted demo, public PyPI package, PyPI JSON API response, pipx, and Windows
   validation are auditable instead of only environment-variable declarations.

docs/falsiflow_architecture.md

@@ -54,8 +54,8 @@ release artifacts all agree.
   verified installs.
 - `falsiflow.adoption` and `falsiflow.release`: adoption priority checks,
   distribution checks, package surface checks, and release report rendering.
-- `falsiflow.public_release`: static demo, publish kit, launch kit, and
-  external evidence/readiness handoff artifacts.
+- `falsiflow.public_release`: static demo, publish handoff, and external
+  evidence/readiness artifacts.
 
 ## Release Invariants
 

docs/falsiflow_cli_reference.md

@@ -3,7 +3,7 @@
 This reference is generated from the active `argparse` command tree.
 
 - Status: `cli_reference_ready`
-- Commands: 58
+- Commands: 57
 
 Regenerate it with:
 
@@ -17,7 +17,7 @@ falsiflow cli-reference --out docs/falsiflow_cli_reference.md
 - Discovery and evidence import: `falsiflow discover`, `falsiflow agent`, `falsiflow agent discover`, `falsiflow mcp`, `falsiflow candidate`, `falsiflow candidate rank`, `falsiflow assay-plan`, `falsiflow evidence`, `falsiflow evidence import`, `falsiflow ingest-limina-source-values`, `falsiflow ingest-wide-csv`
 - First-run and browser workflows: `falsiflow start`, `falsiflow onboard`, `falsiflow try`, `falsiflow wizard`, `falsiflow serve`, `falsiflow quickstart`, `falsiflow doctor`
 - Project setup: `falsiflow init`, `falsiflow scaffold`
-- Release and public adoption: `falsiflow static-demo`, `falsiflow demo-package`, `falsiflow publish-kit`, `falsiflow launch-kit`, `falsiflow external-evidence`, `falsiflow external-check`, `falsiflow release-proof`, `falsiflow casebook-check`, `falsiflow cli-reference`, `falsiflow schema`, `falsiflow selftest`, `falsiflow adoption-check`, `falsiflow release-check`
+- Release and public adoption: `falsiflow static-demo`, `falsiflow demo-package`, `falsiflow publish-kit`, `falsiflow external-evidence`, `falsiflow external-check`, `falsiflow release-proof`, `falsiflow casebook-check`, `falsiflow cli-reference`, `falsiflow schema`, `falsiflow selftest`, `falsiflow adoption-check`, `falsiflow release-check`
 - Template supply chain: `falsiflow template-scaffold`, `falsiflow templates`, `falsiflow template-gallery`, `falsiflow template-check`, `falsiflow template-pack`, `falsiflow verify-template-pack`, `falsiflow template-registry`, `falsiflow template-lock`, `falsiflow template-attest`, `falsiflow verify-template-attestation`, `falsiflow template-policy`, `falsiflow verify-template-policy`, `falsiflow template-release`, `falsiflow verify-template-release`, `falsiflow template-install`
 
 ## Command Index
@@ -30,7 +30,6 @@ falsiflow cli-reference --out docs/falsiflow_cli_reference.md
 | `falsiflow static-demo` | Export a hostable static demo site for zero-install visitors. |
 | `falsiflow demo-package` | Prepare a GitHub Pages/Netlify-ready static demo package. |
 | `falsiflow publish-kit` | Generate a local handoff kit for GitHub Pages, external readiness, and PyPI release steps. |
-| `falsiflow launch-kit` | Generate public launch copy, demo script, proof card, and maintainer checklist. |
 | `falsiflow external-evidence` | Write a structured JSON template for hosted demo, PyPI, pipx, and Windows validation evidence. |
 | `falsiflow external-check` | Check public release dependencies such as hosted demo URL, repo URL, PyPI package URL, pipx, and Windows validation. |
 | `falsiflow release-proof` | Generate a copy-paste release proof snippet from External Evidence artifacts. |
@@ -207,29 +206,6 @@ falsiflow publish-kit [-h] [--template TEMPLATE]
 | `--force` | `` | `no` | `False` | Allow replacing an existing publish-kit directory. |
 | `--json` | `` | `no` | `False` | Print machine-readable publish handoff summary. |
 
-### `falsiflow launch-kit`
-
-Generate public launch copy, demo script, proof card, and maintainer checklist.
-
-```text
-falsiflow launch-kit [-h] [--template TEMPLATE]
-                            [--template-root TEMPLATE_ROOT]
-                            [--out-dir OUT_DIR] [--repo-slug REPO_SLUG]
-                            [--public-demo-url PUBLIC_DEMO_URL] [--tag TAG]
-                            [--force] [--json]
-```
-
-| Argument | Value | Required | Default | Help |
-| --- | --- | --- | --- | --- |
-| `--template` | `TEMPLATE` | `no` | `biointerface_coatings` | Starter template to use in the nested public demo package. |
-| `--template-root` | `TEMPLATE_ROOT` | `no` | `[]` | Extra template root to search before bundled templates. Repeatable. |
-| `--out-dir` | `OUT_DIR` | `no` | `falsiflow_launch_kit` | Directory for public launch materials. |
-| `--repo-slug` | `REPO_SLUG` | `no` | `` | Optional GitHub repo slug such as OWNER/falsiflow. |
-| `--public-demo-url` | `PUBLIC_DEMO_URL` | `no` | `` | Optional hosted public demo URL. |
-| `--tag` | `TAG` | `no` | `v0.1.1` | Release tag to include in launch materials. |
-| `--force` | `` | `no` | `False` | Allow replacing an existing launch-kit directory. |
-| `--json` | `` | `no` | `False` | Print machine-readable launch kit summary. |
-
 ### `falsiflow external-evidence`
 
 Write a structured JSON template for hosted demo, PyPI, pipx, and Windows validation evidence.
@@ -459,6 +435,7 @@ falsiflow evidence import [-h] --input INPUT --out OUT
 | `--instrument-id-column` | `INSTRUMENT_ID_COLUMN` | `no` | `` |  |
 | `--notes` | `NOTES` | `no` | `` |  |
 | `--notes-column` | `NOTES_COLUMN` | `no` | `` |  |
+
 ### `falsiflow try`
 
 Run a 30-second starter demo and write a local browser launchpad.

docs/falsiflow_launch_execution.md

@@ -40,9 +40,9 @@ follow-up checks. Use it after the current public release evidence is green.
 - Live PR demo: <https://github.com/AzurLiu/falsiflow/pull/17>
 - Blocked PR run: <https://github.com/AzurLiu/falsiflow/actions/runs/26708459093>
 - Ready PR run: <https://github.com/AzurLiu/falsiflow/actions/runs/26708472653>
-- Social preview source: run
-  `falsiflow launch-kit --out-dir falsiflow_launch_kit --force`, then review
-  and upload `social_preview.png` in GitHub repository settings.
+- Social preview source: use the checked-in proof-strip assets under
+  `docs/assets/`, then review and upload the chosen PNG in GitHub repository
+  settings.
 - Pre-public-post baseline recorded on 2026-06-01 05:49 CST after the
   upload-ready social preview release:
   0 stars, 2 forks, 0 watchers, 8 total views, 1 unique view, 466 total clones,

docs/falsiflow_mvp.md

@@ -121,9 +121,6 @@ python3 scripts/falsiflow.py demo-package \
 python3 scripts/falsiflow.py publish-kit \
   --out-dir data/falsiflow/publish_kit \
   --force
-python3 scripts/falsiflow.py launch-kit \
-  --out-dir data/falsiflow/launch_kit \
-  --force
 python3 scripts/falsiflow.py external-evidence \
   --out data/falsiflow/external_evidence.json \
   --force
@@ -141,17 +138,7 @@ and `publish_checklist.md`. `publish-kit` writes `publish_handoff.json`,
 package so account-bound GitHub/Pages/PyPI steps have a reviewable handoff
 artifact, a one-page final evidence ledger, and a public release rehearsal with
 ordered commands, expected artifacts, success signals, and stop conditions.
-`launch-kit` adds
-`launch_summary.json`,
-`proof_card.md`, `announcement.md`, `demo_script.md`,
-`readme_proof_strip.svg`, `social_preview.png`, `social_preview.svg`,
-`github_repo_profile.md`,
-`launch_posts.md`, `launch_metrics.json`, `launch_metrics.md`, and
-`maintainer_checklist.md` so public launch copy, GitHub repository profile
-settings, social preview imagery, proof points, and 1k-star launch tracking are
-reviewed before account-bound publishing. The nested publish handoff also
-includes `release_rehearsal.md` so launch reviewers can rehearse the final
-public release path before announcements. `external-evidence` writes a fillable JSON
+`external-evidence` writes a fillable JSON
 template for hosted demo, public PyPI package URL plus PyPI JSON API proof,
 checkout-based pipx smoke, public-package pipx smoke, and Windows/PowerShell
 smoke evidence.

docs/falsiflow_positioning.md

@@ -171,22 +171,19 @@ falsiflow release-check --out-dir data/falsiflow/release_check --force
 
 ### Public Launch
 
-Use Falsiflow when the repository needs a public demo, launch copy, proof card,
-release rehearsal, and external validation evidence before calling a release
-externally ready.
+Use Falsiflow when the repository needs a public demo, release rehearsal, and
+external validation evidence before calling a release externally ready.
 
 Proof path:
 
 ```bash
-falsiflow launch-kit --out-dir falsiflow_launch_kit --force
 falsiflow external-evidence --out falsiflow_external_evidence.json --force
 falsiflow external-check --out-dir falsiflow_external_check --evidence falsiflow_external_evidence.json --force
 ```
 
 The generated `release_rehearsal.md` keeps the last-mile sequence explicit:
-local regression, release-check, casebook replay, launch-kit review, external
-evidence capture, `external-check --strict`, and public announcement stop
-conditions.
+local regression, release-check, casebook replay, external evidence capture,
+`external-check --strict`, and public announcement stop conditions.
 
 ## Decision Rubric
 

docs/falsiflow_public_casebook.md

@@ -242,7 +242,6 @@ falsiflow template-gallery --out data/falsiflow/template_gallery.md --json-out d
 falsiflow casebook-check --out-dir data/falsiflow/casebook_check --force
 falsiflow quickstart --template biointerface_coatings --out public_case_demo --strict
 falsiflow claim-check --project-dir public_case_demo --strict --force
-falsiflow launch-kit --out-dir falsiflow_launch_kit --force
 ```
 
 End the demo by opening the local launchpad or hosted static demo, then show

docs/falsiflow_public_issue_queue.md

@@ -45,9 +45,8 @@ one higher-context `help wanted` issue while launch feedback is still small.
    `docs/assets/falsiflow_live_pr_story_reel.svg`, keep
    `claim_check_blocked`, `claim_check_ready`, and the evidence-package
    readiness boundary visible, then run `python3 scripts/falsiflow.py
-   launch-kit --out-dir /tmp/falsiflow_launch_gif_check --force --json` and
-   `python3 scripts/falsiflow.py release-check --out-dir
-   /tmp/falsiflow_launch_gif_release_check --force --skip-dist --json`.
+   release-check --out-dir /tmp/falsiflow_launch_gif_release_check --force
+   --skip-dist --json`.
 
 ## Completed Work