docs: add v0.2 packaging dry-run report

docs/V0.2-PACKAGING-DRY-RUN.md

@@ -0,0 +1,154 @@
+# v0.2 Packaging Dry-Run Report
+
+Status: packaging path verified for current main; final v0.2.0 artifacts still pending.
+
+Date: 2026-06-15.
+
+Base commit reviewed: d47e79874a2a0b2d035fa3f751bf076749f95059.
+
+CI run reviewed before dry-run: 27547533879.
+
+This report records a packaging and install dry-run for the current `main` state before any v0.2.0 version bump, tag, GitHub Release, or artifact upload.
+
+It is not a v0.2.0 release approval.
+
+## Scope
+
+This phase verifies that the current package build and installation path works from clean temporary environments.
+
+It does not approve:
+
+- changing `pyproject.toml`;
+- changing package version metadata;
+- cutting CHANGELOG.md;
+- creating a tag;
+- creating a GitHub Release;
+- uploading artifacts;
+- publishing to PyPI;
+- changing code, tests, fixtures, or CI.
+
+## Version caveat
+
+The current package version is still:
+
+- `0.1.0`.
+
+Therefore the dry-run artifacts built in this phase are named:
+
+- `agent_rules_kit-0.1.0-py3-none-any.whl`;
+- `agent_rules_kit-0.1.0.tar.gz`.
+
+This proves that the packaging path works for the current source tree.
+
+It does not replace the required final v0.2.0 artifact build after the dedicated version-cut phase.
+
+## Commands verified
+
+The dry-run used a temporary directory outside the repository.
+
+The dry-run verified:
+
+- `python -m build --sdist --wheel`;
+- wheel artifact generation;
+- sdist artifact generation;
+- SHA256 checksum generation;
+- clean virtual environment install from wheel;
+- `pip check` after wheel install;
+- installed `agent-rules-kit --help` after wheel install;
+- installed `agent-rules-kit check ... --format json` after wheel install;
+- installed `python -m agent_rules_kit.cli check ... --format markdown` after wheel install;
+- clean virtual environment install from sdist;
+- `pip check` after sdist install;
+- installed `agent-rules-kit --help` after sdist install;
+- installed `agent-rules-kit check ... --format console` after sdist install;
+- installed `python -m agent_rules_kit.cli check ... --format json` after sdist install;
+- cleanup of the temporary build directory;
+- clean repository state after the dry-run.
+
+## Artifacts generated during dry-run
+
+The dry-run generated these temporary artifacts outside the repository:
+
+- `agent_rules_kit-0.1.0-py3-none-any.whl`;
+- `agent_rules_kit-0.1.0.tar.gz`.
+
+The temporary artifacts were not committed, uploaded, tagged, or released.
+
+## Checksums observed during dry-run
+
+The temporary wheel checksum was:
+
+- `5cd549b2d22e8ea7dc1e54409d8c0ed38d66ebe42e79ab04cb9475914ee387ef`.
+
+The temporary sdist checksum was:
+
+- `f0fd23b61b1fbce2713ada5d7f29b985bdc0afc824c2edea084eaca8c16e7c90`.
+
+These checksums are evidence for this local dry-run only.
+
+They must not be reused as final v0.2.0 release checksums.
+
+## Install result
+
+Wheel installation result:
+
+- installed successfully in a clean virtual environment;
+- `pip check` reported no broken requirements;
+- console script executed;
+- module execution executed;
+- governance output worked.
+
+Sdist installation result:
+
+- built a wheel from the sdist in a clean virtual environment;
+- installed successfully;
+- `pip check` reported no broken requirements;
+- console script executed;
+- module execution executed;
+- governance output worked.
+
+## Warnings observed
+
+The dry-run emitted pip cache warnings:
+
+- `WARNING: Cache entry deserialization failed, entry ignored`.
+
+These warnings did not block installation, `pip check`, console-script execution, module execution, or governance output smoke tests.
+
+They are treated as non-blocking local pip cache noise for this dry-run.
+
+## Repository mutation result
+
+After the temporary directory was removed, the repository remained clean.
+
+No generated build artifacts were left in the repository.
+
+No files were modified by the packaging dry-run before this report was created.
+
+## Release impact
+
+This phase reduces packaging risk for v0.2.0 release preparation.
+
+It partially addresses the packaging blocker from `docs/V0.2-RELEASE-READINESS.md` by proving the packaging path works on current `main`.
+
+It does not fully close the final v0.2.0 artifact blocker because final artifacts must be rebuilt after:
+
+- version metadata is changed to `0.2.0`;
+- CHANGELOG.md is cut for `0.2.0`;
+- release notes are prepared;
+- the final release SHA is verified.
+
+## Decision
+
+Packaging path status:
+
+- current main packaging: verified;
+- wheel install path: verified;
+- sdist install path: verified;
+- installed CLI smoke behavior: verified;
+- final v0.2.0 artifacts: pending;
+- final v0.2.0 release decision: still blocked.
+
+Recommended next phase:
+
+- verify branch protection, required status checks, and private vulnerability reporting evidence, or document explicit limitations if API evidence is unavailable.