docs: correct rtk gh api to intentional 0% passthrough

[AshSgDe29071999]

Summary

rtk init wrote rtk gh api # Compact API responses (26%) into agent instruction files, but run_api is an intentional 0% passthrough so values are not destroyed.

Changes

• Update the GitHub section emitted by rtk init (src/hooks/init.rs): drop the false 26% claim, note passthrough, and point at --jq / compressed gh repo view.
• Align docs/usage/FEATURES.md savings table with 0% passthrough.

Closes #3448

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[aeppling]

already explicit above, just don't list it in covered cmds

[AshSgDe29071999]

Good call — removed gh api from the covered commands list in the rtk init GitHub section. The section header still notes that gh api is intentional 0% passthrough.

[AshSgDe29071999]

@aeppling — confirmed: gh api is not listed in the covered commands block under the GitHub section of rtk init (only pr / run / issue / repo view). The section header still notes that gh api is intentional 0% passthrough, consistent with docs/usage/FEATURES.md.

The only remaining blocker on this PR is the CLA check (pending at https://cla-assistant.io/rtk-ai/rtk?pullRequest=3450). That needs a browser sign-in from the contributor account; once signed, CLA Assistant should flip green and this should be ready to merge.