Skip to content

docs(questions): guest input on runtime.wasm (#1800) + overnight truth-pass - #189

Merged
enricopiovesan merged 1 commit into
mainfrom
ceo/guest-input-qa-1800
Nov 6, 2026
Merged

enricopiovesan merged 1 commit into
mainfrom
ceo/guest-input-qa-1800

Conversation

@enricopiovesan

Copy link
Copy Markdown
Collaborator

Summary

Friday morning CEO ship (not a blog day).

  • New SEO Q&A: What input does a runtime.wasm guest receive?
    • Published v0.16.2 still hands Swift/Kotlin/.NET guests the whole {target_id, input} envelope.
    • On main, traverse#1800 (closing #1794) unwraps it: guest gets only canonical input (Spec 1722); wrong target_id → target_not_found; extra members → ambiguous_submit.
    • Carefully labeled not yet in a tagged release.
    • Notes related web raw-submit kind:app_command fix on main (#1802 via #1806).
  • Truth-pass: host-connector Q&A no longer says #1791 is open (closed on main by #1796, unreleased); published model.execute Q&A + llms.txt note #1785 fixed on main by #1809 (unreleased).
  • Wired into questions hub + public/llms.txt.

No product claims invented. No Callweave. No em dashes / title arrows.

Validation

  • npm test: 11 pass, 2 skipped
  • npm run build: 236 pages, includes the new Q&A

…h-pass

New SEO Q&A: what input a runtime.wasm guest receives. Published v0.16.2
still hands native guests the {target_id, input} envelope; main unwraps
it (#1800 / #1794, not released). Also notes the related web raw-submit
app_command fix on main (#1802 / #1806).

Truth-pass: #1791 closed on main via #1796 in the host-connector Q&A;
#1785 closed on main via #1809 in the published model.execute Q&A and
llms.txt. Wired into the questions hub and llms.txt.
@enricopiovesan
enricopiovesan merged commit 876ebff into main Nov 6, 2026
5 checks passed
@enricopiovesan
enricopiovesan deleted the ceo/guest-input-qa-1800 branch November 6, 2026 16:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant