# Implementation Plan: Test Release Mechanism

## Phase 1: Local Dry Run and Documentation Setup

- [x] Task: Create the initial `TESTING_GUIDE.md` file.
  - [x] Add an overview section explaining the purpose of test releases.
- [x] Task: Develop the local packaging script.
  - [x] Write a failing test that checks for the creation of a `.tgz` file.
  - [x] Implement the script (e.g., using `npm pack`) to generate the local tarball.
  - [x] Ensure the script names the output file correctly.
- [x] Task: Document the Local "Dry Run" process.
  - [x] Add a section to `TESTING_GUIDE.md` titled "Local Dry Run Testing".
  - [x] Write step-by-step instructions on how to run the new script.
  - [x] Explain how a developer can use the generated `.tgz` file in another project for testing (e.g., `npm install /path/to/package.tgz`).
- [~] Task: Conductor - User Manual Verification 'Phase 1: Local Dry Run and Documentation Setup' (Protocol in workflow.md)

## Phase 2: Scoped Test Package Publishing

- [x] Task: Configure the project for the test package.
  - [x] Create a separate `package.json` or a script to temporarily modify the existing one to change the package name to `test-uniswap-position-quoter`.
  - [x] Ensure this change does not affect the main build or get committed.
- [x] Task: Create the manual publishing script.
  - [x] Write a script that allows a developer to manually specify a version and publish to npm.
  - [x] The script should handle the name change, version bump, and `npm publish` command.
- [x] Task: Document the Scoped Test Package process.
  - [x] Add a section to `TESTING_GUIDE.md` titled "Remote Scoped Testing".
  - [x] Document the commands needed to publish the test package.
  - [x] Include warnings about manual versioning and the risk of overwriting.
- [~] Task: Conductor - User Manual Verification 'Phase 2: Scoped Test Package Publishing' (Protocol in workflow.md)

## Phase 3: Finalization and Review

- [x] Task: Review and refine all documentation.
  - [x] Proofread `TESTING_GUIDE.md` for clarity, correctness, and completeness.
  - [x] Add a section to the main `README.md` that links to `TESTING_GUIDE.md`.
- [x] Task: Clean up and ensure no interference with production releases.
  - [x] Verify that the standard `semantic-release` process is entirely unaffected.
  - [x] Add any new script files to `.gitignore` if they are not meant to be committed.
- [~] Task: Conductor - User Manual Verification 'Phase 3: Finalization and Review' (Protocol in workflow.md)