[codex] Fix Genesis publish auth and bounded PawFS lookups

[rita-aga]

Summary

• add TDD coverage for authenticated, noninteractive Genesis git publish/update and bounded PawFS single-entity lookups
• send the configured Genesis GitToken as an Authorization: Bearer ... git extraHeader for temper.publish_app and temper.update_app, with GENESIS_GIT_TOKEN then GENESIS_TOKEN defaults
• set GIT_TERMINAL_PROMPT=0, bound PawFS lookup filters with $top=1, and document the auth contract in ADR/deployment/agent skills

Verification

• cargo test -p temperpaw --test paw_fs_hot_path — 15 passed
• git diff --check — passed
• cargo build --target wasm32-wasip1 --release in os-apps/paw-agent/wasm/monty_repl — passed earlier with pre-existing warnings
• ./build.sh in os-apps/paw-fs/wasm/artifact_batch_apply — passed earlier
• live production proof recorded in docs/proofs/2026-06-18-katagami-publish-e2e.md

Live Status

• temperpaw/paw-fs@8cc9c1a0c3959ba0555a6eac5446db76de747817 was published and installed in production.
• The paw-agent fix is implemented and locally verified, but live install is blocked because Genesis clone/fetch for temperpaw/paw-agent reproducibly stalls around 77-78% of received objects. Authenticated ls-remote with the existing GENESIS_TOKEN works, shallow/partial clone is unsupported, force publish is denied by policy, and low-level fast-forward push without the parent object is rejected.