chore(release): prepare v0.0.2

[Teingi]

Which issue or RFC does this PR close?

No linked issue or RFC.

Rationale for this change

Prepare the repository for the PowerContext 0.0.2 release with consistent package, API, integration, workflow, and documentation versions.

What changes are included in this PR?

• Bump the Python package, OpenAPI contract, generated HTTP metadata, tests, and lockfiles to 0.0.2.
• Accept powercontext-vX.Y.Z release tags in the verification and publishing workflows while retaining the existing tag formats.
• Synchronize the root OpenAPI contract with the DeepSeek Harness plugin snapshot.
• Include both the Claude Code and Codex plugin paths in static type checking.
• Rewrite the English README and add aligned Chinese and Japanese READMEs with current installation commands, core capabilities, benchmark results, and official plugin guidance.

Are there any user-facing changes?

Yes. Installation examples now pin 0.0.2, the published API metadata reports 0.0.2, release workflows accept the powercontext-vX.Y.Z tag form, and project documentation is available in English, Chinese, and Japanese. No persisted-format or breaking API change is introduced.

How was this change tested?

• Sensitive-information scan across all staged files and added lines: no credentials, private keys, tokens, absolute user paths, or non-loopback host IPs found.
• make check
• make test (551 passed, 12 skipped)
• make contract-test (28 passed)
• make docs-test
• uv run --project e2e/bub --frozen pytest e2e/bub/tests (5 passed)
• uv build
• uvx --from 'twine>=6.2' twine check dist/powercontext-0.0.2.tar.gz dist/powercontext-0.0.2-py3-none-any.whl

AI usage statement

OpenAI Codex using GPT-5.6-Sol was used to review the release changes, synchronize the multilingual READMEs, run validation, and prepare this pull request.

[PsiACE]

totally lgtm