chore: remove deployment-path references from OSS docs (#114)

Move PRODUCT.md to the hq product hub (it described hq layout from inside
OSS, which made no sense for OSS readers), and strip the K8s deploy
subsection from apps/scanner/CLAUDE.md and README.md.

OSS docs should serve OSS readers. Internal deployment details live in hq.

Co-authored-by: Mathew Goldsborough <1759329+mgoldsborough@users.noreply.github.com>

Author: mgoldsborough

PRODUCT.md

@@ -181,17 +181,6 @@ Releases are automated via GitHub Actions and PyPI trusted publishing. Pushing a
 
 CI handles PyPI publish and Docker build/push to `ghcr.io/nimblebraininc/mpak-scanner`. See `.github/workflows/scanner-publish.yml`.
 
-### Production Deployment (ECR/K8s)
-
-After the PyPI release, deploy the scanner to production K8s (from `hq/deployments/mpak/`):
-
-```bash
-make deploy-scanner ENV=production
-make apply-scanner-infra ENV=production  # only if RBAC/secrets changed
-```
-
-The Makefile builds from the Dockerfile which pulls the version from PyPI.
-
 ### Schemas and Rules
 
 - **Schemas** (JSON Schema for manifest validation): Fetched at runtime from `mpaktrust.org`. Minimal fallbacks are hardcoded in `schemas.py`. Not bundled in the wheel.

apps/scanner/CLAUDE.md

@@ -174,8 +174,6 @@ docker pull ghcr.io/nimblebraininc/mpak-scanner:latest
 docker run --rm -v /path/to/bundle.mcpb:/bundle.mcpb ghcr.io/nimblebraininc/mpak-scanner scan /bundle.mcpb
 ```
 
-For production deployment to ECR/K8s, see `deployments/mpak/`.
-
 ## Related Projects
 
 - [mpak registry](https://mpak.dev) - Search, download, and publish MCP bundles