docs(args): fix stale cap literals missed by #1056

[ChaoZheng109]

What

Fixes two stale cap literals left behind by #1056 (which raised
CORE_MAX_TENSOR_ARGS 16→32 and lowered CORE_MAX_SCALAR_ARGS 32→16).
#1056 updated the scalar-limit error strings but missed:

• pto_types.h (a2a3 + a5): the tensor-limit error string still read
  "exceeds MAX_TENSOR_ARGS=16". The cap is now 32 — a user who hits
  the tensor-arg cap would otherwise get a misleading message.
• pto_runtime2_types.h (a2a3 + a5): the PTO2TaskPayload::init
  memcpy comment said "Both arrays are 1024B" (dates from an old
  128-scalar cap). The scalar arrays are now MAX_SCALAR_ARGS * 8 =
  128B.

Comment/string only — no ABI or behavior change.

⚠️ Stacked on #1056

These literals are only correct on top of #1056's cap change. On
main, CORE_MAX_TENSOR_ARGS is still 16 and the scalar arrays are 256B,
so the current text is correct there. This branch is stacked on #1056:

• Do not merge before Update: raise CORE_MAX_TENSOR_ARGS to 32, lower scalars to 16 #1056.
• Until Update: raise CORE_MAX_TENSOR_ARGS to 32, lower scalars to 16 #1056 merges, this PR's diff also includes Update: raise CORE_MAX_TENSOR_ARGS to 32, lower scalars to 16 #1056's commit; after
  Update: raise CORE_MAX_TENSOR_ARGS to 32, lower scalars to 16 #1056 lands, rebasing reduces it to the 4-line doc fix here.

[gemini-code-assist]

Warning

You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again!

[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: ff0bf71c-c912-4b84-9198-bbd83b1477ed

📥 Commits

Reviewing files that changed from the base of the PR and between e549000 and 1795a8e.

📒 Files selected for processing (4)

• src/a2a3/runtime/tensormap_and_ringbuffer/runtime/pto_runtime2_types.h
• src/a2a3/runtime/tensormap_and_ringbuffer/runtime/pto_types.h
• src/a5/runtime/tensormap_and_ringbuffer/runtime/pto_runtime2_types.h
• src/a5/runtime/tensormap_and_ringbuffer/runtime/pto_types.h

---

📝 Walkthrough

Walkthrough

Four single-line fixes across two pairs of mirrored header files in the a2a3 and a5 runtime paths: the cache-line rounding comment in PTO2TaskPayload::init is corrected from 1024B to 128B, and the set_error string for exceeding tensor argument limits is updated from MAX_TENSOR_ARGS=16 to MAX_TENSOR_ARGS=32. No executable logic, data layout, or public declarations are changed.

Changes

Comment and Error String Corrections

Layer / File(s)	Summary
Cache-line comment correction src/a2a3/runtime/tensormap_and_ringbuffer/runtime/pto_runtime2_types.h, src/a5/runtime/tensormap_and_ringbuffer/runtime/pto_runtime2_types.h	The inline comment in PTO2TaskPayload::init describing tensor/scalar array sizes for cache-line rounding is corrected from 1024B to 128B in both the a2a3 and a5 copies.
MAX_TENSOR_ARGS error string correction src/a2a3/runtime/tensormap_and_ringbuffer/runtime/pto_types.h, src/a5/runtime/tensormap_and_ringbuffer/runtime/pto_types.h	The set_error message reporting the tensor argument limit is updated from MAX_TENSOR_ARGS=16 to MAX_TENSOR_ARGS=32 in both the a2a3 and a5 copies.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• hw-native-sys/simpler#1056: Updates PTO2TaskPayload cache-line layout with static_assert changes tightening tensor/scalar region sizing to 128B, directly establishing the correct value this PR now documents in comments.

Poem

🐇 A comment once said "one-oh-two-four bytes wide,"
But the truth was one-twenty-eight, it lied!
And sixteen for tensor args? No, thirty-two's right,
So I hopped through the headers and set them aright.
Now the docs match the code—what a glorious sight! ✨

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 75.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the changeset: fixing stale documentation literals (cap values in comments and error strings) that were missed in a previous change.
Description check	✅ Passed	The description is directly related to the changeset, clearly explaining what stale literals were fixed, why they matter, and their impact.
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.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

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 and usage tips.}