Reset Falsiflow core for v0.2.0

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -6,53 +6,53 @@ body:
   - type: markdown
     attributes:
       value: |
-        Thanks for reporting a concrete failure. Please include commands and generated artifacts when you can.
+        Thanks for reporting a concrete failure. Please include the command and generated artifacts when you can.
   - type: textarea
     id: command
     attributes:
       label: Command or workflow
-      description: Paste the exact command, Make target, CI job, or browser workflow that failed.
-      placeholder: falsiflow release-check --out-dir data/falsiflow/release_check --force
+      description: Paste the exact command or CI job that failed.
+      placeholder: falsiflow check --config project.json --evidence evidence.csv --strict
     validations:
       required: true
   - type: textarea
     id: expected
     attributes:
       label: Expected result
       description: What status, artifact, report, or behavior did you expect?
-      placeholder: release_ready with package_ready, dist_ready, and release_validation_ready.
+      placeholder: claim_ready with claim_check.json, claim_check.md, and evidence_bundle.zip.
     validations:
       required: true
   - type: textarea
     id: actual
     attributes:
       label: Actual result
       description: Include the first failing status, traceback, report excerpt, or CI link.
-      placeholder: release_blocked because sdist_required_files failed.
+      placeholder: claim_blocked because acceptance_rules failed.
     validations:
       required: true
   - type: textarea
     id: environment
     attributes:
       label: Environment
       description: Include OS, Python version, install method, and whether this was local, pipx, or CI.
-      placeholder: macOS 15, Python 3.12, editable install with python3 -m pip install -e .
+      placeholder: macOS 15, Python 3.12, pipx install falsiflow
     validations:
       required: true
   - type: textarea
     id: artifacts
     attributes:
       label: Relevant artifacts
-      description: Link or paste paths for release_check.json, adoption_check.json, claim_check.json, bundle verification, or template verification reports.
-      placeholder: data/falsiflow/release_check/release_check.json
+      description: Link or paste paths for claim_check.json, claim_check.md, or evidence_bundle.zip.
+      placeholder: falsiflow_out/claim_check.json
     validations:
       required: false
   - type: checkboxes
     id: boundaries
     attributes:
       label: Checks before filing
       options:
-        - label: I checked that this is not a claim that Falsiflow should treat as scientific proof, safety proof, regulatory approval, or clinical validation.
+        - label: I checked that this is a claim-readiness issue, not a request for Falsiflow to prove model quality, scientific truth, safety, or regulatory approval.
           required: true
         - label: I removed secrets, private raw data, and credentials from shared logs or artifacts.
           required: true

.github/ISSUE_TEMPLATE/config.yml

@@ -1,8 +1,8 @@
 blank_issues_enabled: false
 contact_links:
-  - name: Responsible-use boundary
-    url: https://github.com/AzurLiu/falsiflow/blob/main/RESPONSIBLE_USE.md
-    about: Read how to interpret Falsiflow readiness before relying on a claim.
+  - name: Claim-readiness boundary
+    url: https://github.com/AzurLiu/falsiflow#what-it-is--is-not
+    about: Read what Falsiflow does and does not prove before relying on a claim.
   - name: Security and integrity reports
     url: https://github.com/AzurLiu/falsiflow/blob/main/SECURITY.md
-    about: Report provenance, bundle verification, path handling, or supply-chain issues privately.
+    about: Report provenance, bundle verification, path handling, or packaging issues privately.

.github/ISSUE_TEMPLATE/feature_request.yml

@@ -1,34 +1,34 @@
 name: Feature request
-description: Propose a CLI, template, documentation, or workflow improvement.
+description: Propose a focused improvement to the core claim gate.
 title: "[Feature]: "
 labels: ["enhancement", "needs-triage"]
 body:
   - type: textarea
     id: problem
     attributes:
       label: Problem
-      description: What adoption, review, template-authoring, or evidence-gate problem should this solve?
-      placeholder: New users can run the quickstart, but template authors need a clearer install verification path.
+      description: What numeric-claim review or CI-gate problem should this solve?
+      placeholder: Reviewers need a clearer blocker when a metric row is missing baseline evidence.
     validations:
       required: true
   - type: textarea
     id: proposal
     attributes:
       label: Proposed change
-      description: Describe the command, report, template, documentation, or CI behavior you want.
-      placeholder: Add a command that verifies a template release bundle and writes a Markdown review card.
+      description: Describe the CLI, report, Action, schema, or packaging behavior you want.
+      placeholder: Add a concise blocker reason for missing source_file references in claim_check.md.
     validations:
       required: true
   - type: dropdown
     id: area
     attributes:
       label: Area
       options:
-        - First-run experience
-        - Audit reports
-        - Starter templates
-        - Release and packaging
-        - Local browser app
+        - Core claim gate
+        - Evidence schema
+        - GitHub Action
+        - Reports and bundle
+        - Packaging
         - Documentation
         - Security or provenance
     validations:
@@ -38,15 +38,15 @@ body:
     attributes:
       label: Success criteria
       description: What command, artifact, status, or documentation would show the feature is complete?
-      placeholder: adoption-check reports adoption_ready and release-check still reports release_ready.
+      placeholder: falsiflow check blocks the bad evidence row and reports the missing source_file reason.
     validations:
       required: true
   - type: checkboxes
     id: contribution
     attributes:
       label: Contribution path
       options:
-        - label: I can help test this with `falsiflow quickstart`, `falsiflow doctor`, `falsiflow adoption-check`, or `falsiflow release-check`.
+        - label: I can test this with `falsiflow check` on a small config and evidence CSV.
           required: false
         - label: I can open a pull request using `.github/PULL_REQUEST_TEMPLATE.md`.
           required: false

.github/PULL_REQUEST_TEMPLATE.md

@@ -1,27 +1,26 @@
 ## What Changed
 
-Describe the user-visible behavior, command, report, template, packaging, or documentation change.
+Describe the user-visible change to `falsiflow check`, the GitHub Action, reports, packaging, or docs.
 
 ## Verification
 
 Paste the commands you ran and the final status:
 
 ```bash
-python3 -m py_compile falsiflow/core.py falsiflow/cli.py falsiflow/adapters.py falsiflow/api.py falsiflow/mcp_server.py falsiflow/casebook_check.py scripts/falsiflow.py scripts/falsiflow_tests/regress_falsiflow_core.py
+python3 -m py_compile falsiflow/core.py falsiflow/bundle.py falsiflow/claim_check.py falsiflow/cli.py scripts/falsiflow.py scripts/falsiflow_tests/regress_falsiflow_core.py
 python3 scripts/falsiflow_tests/regress_falsiflow_core.py
-falsiflow adoption-check --out-dir data/falsiflow/adoption_check --force
-falsiflow release-check --out-dir data/falsiflow/release_check --force
+python3 -m build
+python3 -m twine check dist/*
 ```
 
 ## Evidence Boundary
 
-- [ ] This change does not make `claim_ready` bypass missing provenance, placeholder evidence, malformed configuration, or failed gates.
-- [ ] New public commands or JSON fields are documented and covered by tests or release-check expectations.
-- [ ] Template distribution changes were checked with `template-check`, `template-pack`, `verify-template-pack`, `template-release`, `verify-template-release`, and `template-install` where applicable.
-- [ ] Security-sensitive changes preserve bundle verification, SHA-256 integrity, path handling, and source-file provenance.
-- [ ] Responsible use remains clear: Falsiflow readiness is not proof of safety, efficacy, regulatory compliance, or experimental truth.
+- [ ] This change does not let `claim_ready` bypass missing provenance, placeholder evidence, malformed config, failed thresholds, or bundle verification.
+- [ ] New public CLI or Action behavior is covered by a regression test or smoke check.
+- [ ] The public surface remains limited to `check` and `schema`; compatibility aliases stay hidden.
+- [ ] Shared artifacts and logs do not include secrets, credentials, or private raw data.
 
 ## Release Impact
 
-- [ ] `CHANGELOG.md`, `README.md`, `RELEASE.md`, `SECURITY.md`, or `RESPONSIBLE_USE.md` were updated when relevant.
-- [ ] `adoption-check` and `release-check` pass, or this PR explains why they cannot run in the current environment.
+- [ ] `README.md`, `CHANGELOG.md`, `SECURITY.md`, or `CONTRIBUTING.md` were updated when relevant.
+- [ ] This PR does not reintroduce launch, demo, discovery, MCP, template marketplace, or release/adoption automation systems.