chore(harbor): docs pin harbor==0.15.0 but upstream is 0.21.0 with a changed dataset interface

[reacher-z]

Every Harbor invocation in our docs pins harbor==0.15.0:

• README.md:470, :492, :507, :834
• src/README.md:29
• (and the adapter docs generated from these)

Upstream is now 0.21.0 (harbor-framework/harbor, PyPI harbor). Between those versions the dataset interface changed: 0.15's local-path form harbor run -p ./harbor-datasets/clawbench-v2 has given way to hub-published datasets addressed as harbor run -d org/dataset@version, and the hub publish flow (harbor auth login → harbor dataset init → harbor add → harbor publish --public) is now the documented path.

Impact:

1. Users following our docs install a six-versions-stale Harbor; anyone who already has current Harbor finds our commands don't match their CLI.
2. It blocks the more valuable thing: publishing ClawBench to the Harbor hub as tiger-ai-lab/clawbench, which makes the benchmark runnable by anyone with harbor run -d tiger-ai-lab/clawbench@v1 and gets hub-side leaderboard/analytics for free. That publish flow requires ≥0.16-era CLI.

Ask:

1. Smoke-test clawbench-harbor-adapt output against Harbor 0.21 and note the supported range in the docs (or bump the pin).
2. Decide whether to publish the V2 dataset to the Harbor hub (separate issue if yes).

[reacher-z]

@Perry2004 — filed from a read-only audit of main; every claim is cited to file:line and was re-verified by hand before filing. Flagging for your triage: happy to send a PR for any of these you want picked up, or to close it if you judge the behaviour intentional.