docs(coding-style): document orch output direction (pl.Out / pl.InOut)

[YunjiQin]

What

Documents the orchestration-output direction convention applied in #659, so the rule lives in the canonical coding-style guide.

Adds a subsection "Output parameter direction: pl.Out / pl.InOut" to §1 of docs/pypto-coding-style.md:

• Every golden-compared output must declare a direction on the orchestration entry — a plain pl.Tensor is In, so its device→host copy-back is skipped and the tensor reads back as all-zeros on the host (golden silently fails).
• Direction is decided by the TensorSpec:
  • is_output=True, no init_value → pure output → pl.Out[...]
  • is_output=True + init_value → inout (read-modify-write cache/state) → pl.InOut[...]
• Annotate the entry only; @pl.jit.inline sub-kernels keep bare pl.Tensor (direction is stripped at splice and warns). Entry pl.InOut + bare-pl.Tensor inline is the correct pairing.

Docs-only; includes a short attention_csa_test example.

🤖 Generated with Claude Code

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 16c38758-4b2b-45bc-9c9e-77c913c5608c

📥 Commits

Reviewing files that changed from the base of the PR and between 8104075 and 045a221.

📒 Files selected for processing (1)

• docs/pypto-coding-style.md

---

📝 Walkthrough

Walkthrough

This change adds a new documentation subsection to docs/pypto-coding-style.md describing required tensor output direction annotations (pl.Out/pl.InOut) on orchestration entries, the failure mode for bare pl.Tensor parameters, inline sub-kernel behavior, and an example.

Changes

Documentation update

Layer / File(s)	Summary
Output parameter direction documentation docs/pypto-coding-style.md	Adds a subsection explaining pl.Out/pl.InOut requirements, the all-zeros failure mode for bare pl.Tensor, inline sub-kernel handling, and an attention_csa_test example.

Estimated code review effort: 1 (Trivial) | ~5 minutes

Poem

A rabbit hops through docs anew,
Marking In, Out, and InOut too,
No more zeros hiding in the night,
Each tensor's path now clear and bright,
Hop hop, hooray, the guide's in sight! 🐇📘

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly summarizes the docs update about orchestration output directions.
Description check	✅ Passed	The description matches the documented change and explains the new coding-style guidance.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[gemini-code-assist]

Code Review

This pull request updates the docs/pypto-coding-style.md documentation by adding a new section on output parameter direction using pl.Out and pl.InOut. It explains when to use these annotations based on TensorSpec properties, clarifies that they should only be applied to orchestration entries (and not inline sub-kernels), and provides a code example illustrating the correct usage. There are no review comments, so we have no feedback to provide.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.