Repository navigation
docs: document Attention API and shared chat policy for Host 1.0.62 - #43
Draft
AndrewKirkovski wants to merge 6 commits into
Draft
AndrewKirkovski wants to merge 6 commits into
AndrewKirkovski wants to merge 6 commits into
Conversation
…very - Action tools take a `targets` array whose items are the `action_ref` or `target_ref` objects copied verbatim; list all nine read tools, `attention_context_set` and the four action tools with their arguments, including the visual capture options. - State that `attention_inspect` was removed. - Document every terminal action status, the envelope limits for wippy.attention v1 to v4 and wippy.attention.visual v1, and the GET /api/v1/sessions/capabilities descriptor. - Describe plain-message delivery with the tab binding, read withdrawal, guard refusals, per-Session automatic context, upload listing, approved image delivery, composer exclusion, turn errors, and the PNG/WebP upload type requirement for visual capture. - Replace the debugging note with checks for Host config, Session capabilities and the agent trait, and remove internal process text.
- check-attention-context-docs.mjs now requires the `targets` array wording, the removed `attention_inspect` wording, the complete tool list, every terminal status, per-version envelope limits and the capability descriptor fields, and rejects the old `target_ref` wording and internal process text. - Add a Documentation checks workflow that runs the frontend, Attention and Markdown link checkers on pull requests and pushes to main. - Document the Attention checker in the README.
The pages said the agent can turn automatic pointing context on or off without asking the user. That is true of the tool, but the Attention trait tells the model to use it only when the user asks. State both, so readers do not assume the agent changes the setting on its own initiative.
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What was changed
Document the Attention API, agent tools, browser action targets, delivery and lifecycle rules, and debugging. Add the V1 quickstart in English and seven locales. Update shared chat policy guidance for Host 1.0.62 across bootstrap, proxy, managed layout, casing, and chat web component guides. The policy remains compatible with existing host overrides and child package overrides. Documentation checks run in CI.
Verification
All three documentation checks pass, including 6,696 Markdown links across 1,459 pages. The release 62 config update changes 48 guides; this PR also includes the existing Attention documentation commits, for 74 files in total.
Release status
Host 1.0.62 and all 14 public npm packages at 0.0.62 are released. The facade integration remains in draft at wippyai/framework#168. Published Session 0.6.6 lacks the Attention capability/context endpoints; the local Session receiver implementation passes the local matrix, but the published backend smoke is blocked. Keep the coordinated release documentation in draft until the backend prerequisite and downstream release gates are complete.