chore(packaging): version-control the orro name-claim/wrapper sources

[moonweave]

The public orro distributions on PyPI (0.0.2) and npm were authored in an untracked local directory. This adds their sources under packaging/name-claim/{pypi,npm}/ with a README covering the delegation contract (orro delegates to the witnessd runtime; witnessd is a runtime-not-install dependency because it ships via GitHub releases, not PyPI) and publish steps. Build artifacts are gitignored.

No code/behavior change to ORRO, witnessd, or Depone — packaging sources only.

🤖 Generated with Claude Code

[moonweave]

Closing — wrong approach. Two findings from trying this:

1. ORRO repo contract forbids it. scripts/check_orro_repo_contract.py (line ~803) rejects any .py/.sh outside scripts/ and src/orro_wrapper/ — the CI 'contract' job failed on packaging/name-claim/pypi/src/orro/__init__.py. Dropping the name-claim Python source into packaging/ violates ORRO's 'no executable source outside the wrapper' invariant, so it shouldn't be forced in (and the contract shouldn't be weakened just to host it).

2. Redundancy with the existing product wrapper. ORRO already ships orro-product-wrapper (src/orro_wrapper/cli.py, console orro = orro_wrapper.cli:main, DEFAULT_ENGINE_COMMAND = 'python -m orro', with a delegate subcommand). The standalone PyPI orro package (published 0.0.2) is a second orro wrapper. These overlap and need to be reconciled — deciding which one is the published orro — before their source is version-controlled.

This is a design decision, not a mechanical file move. Superseded by that reconciliation.