Skip to content

docs(user-docs): sync with dev since the 09-15 review + 0.9.5 What's New + DigitalOcean install guide - #2869

Merged
vybe merged 2 commits into
devfrom
docs/user-docs-0.9.5-delta
Sep 17, 2026
Merged

vybe merged 2 commits into
devfrom
docs/user-docs-0.9.5-delta

Conversation

@trinity-ability

@trinity-ability trinity-ability commented Sep 17, 2026

Copy link
Copy Markdown
Contributor

Description

Brings docs/user-docs/ up to date with the 38 commits merged to dev since the last full user-docs review (#2803), and adds the user-facing What's New in v0.9.5 page.

Documented

  • Workspace
    • The Work card's one-line "what the agent is doing" status, and the chat scrolls to the card when you send.
    • The theme switch, and sign-in that stays in sync across tabs.
    • A new Dictation section: the mic only shows when speech-to-text can work, and a failure names its cause.
    • Room turns can be stopped, and 1:1 attachments travel with an @mention.
  • GitHub & skills
    • Git now asks a credential helper for the token, so it is out of remote URLs, .git/config and process listings. The agent can still read GITHUB_PAT, and the docs say so.
    • A token-cleanup section in the upgrade guide, linking the runbook.
    • The sync-health poll no longer takes the git index lock, and SYNC_HEALTH_POLL_INTERVAL_SECONDS is documented.
    • Comma-separated allowed-tools works.
  • MCP & automation
    • Fan-out async_mode, and the batch deadline now limits only the wait, not the tasks.
    • Loop tools check agent-to-agent permission, and refused MCP calls are audited as refusals.
    • An unknown model value gets a 422.
    • Only people can switch on "wake on answer".
    • Post-run validation, which was undocumented until now.
    • Subscription usage above 100%, and the retry after a subscription switch keeps the rest of the timeout.
  • Onboarding & deploy
    • New guides/deploying/digitalocean.md, converted from the docs site and checked against trinity-do-create.sh.
    • The Getting started checklist now lives in the Systems sidebar.
    • New Public URL labels.
    • The ops agent's /update now handles hosted installs.
  • Release page: whats-new/v0.9.5.md, linked from both indexes. Its "Full technical record" link points to docs/releases/0.9.5.md, which arrives with the release-prep PR.

No managed hosting. Ability.ai does not currently offer managed Trinity hosting. The "Cloud Hosted (ability.ai)" comparison and walkthrough are removed from guides/deploying-trinity.md, and the self-hosted options are re-lettered A–D. The FAQ answer that pointed users at a hosted sign-up is rewritten.

Corrections found against the code

  • The troubleshooting FAQ pointed at the target agent's Permissions tab; grants are made on the caller's tab.
  • Schedule retries default to 0 in the UI and REST API. Only the MCP create tool defaults to 1.
  • Workspace clients do see the live card.
  • voice-replies.md: the Settings location and the speech-to-text fields.
  • The sync-poll interval is a default, not fixed.
  • Two heading anchors and a leftover issue link.

The FAQ grows from 474 to 499 questions. faq/README.md is regenerated from the page headings, which also fixes two underscore anchors that never resolved.

Related Issue

No issue. This is a periodic /generate-user-docs sync.

Journey Impact

Journey Impact: none: documentation-only change under docs/user-docs; no product code or user journey is modified

Type of Change

  • Bug fix (non-breaking change that fixes an issue)
  • New feature (non-breaking change that adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Documentation update

Testing

  • Relative link and anchor check: 0 broken across 110 pages
  • Issue-number / internal-codename grep: 0 hits in added lines
  • Deploy public-safety greps and the enterprise-docs-guard pattern: 0 hits
  • Every factual claim in the new text was checked against the code (commit diffs, routers, Vue components, deploy scripts)

Mutation: n/a — not a fix

Checklist

  • I have updated the documentation (if applicable)
  • I have not committed any sensitive data (API keys, credentials, etc.)

🤖 Generated with Claude Code

…k line and room stop, token-free git remotes, fan-out async mode, DigitalOcean install guide, 0.9.5 What's New

Covers the 38 commits merged to dev after the last full review (dbc9698),
plus the 0.9.5 user-facing release page.

Documented:
- Workspace: the Work card's one-line activity status and scroll-to-card on
  send, the theme switch, cross-tab sign-in sync, a Dictation section (the mic
  shows only when speech-to-text can work; failures name their cause), room
  turns can be stopped, and 1:1 attachments travel with an @mention.
- GitHub: git asks a credential helper, so the token is out of remote URLs,
  .git/config and process listings (the agent can still read GITHUB_PAT);
  upgrade section + runbook link; sync-health polling takes no index lock and
  SYNC_HEALTH_POLL_INTERVAL_SECONDS; comma-separated allowed-tools.
- MCP / automation: fan-out async_mode, and the batch deadline bounds the wait
  rather than the tasks; loop tools check the agent permission edge; refused
  calls are audited as refusals; unknown model ids get 422; wake-on-answer is
  human-only; post-run validation (previously undocumented); utilization over
  100%; the post-switch retry keeps the remaining timeout.
- Onboarding / deploy: new guides/deploying/digitalocean.md converted from the
  docs site and checked against trinity-do-create.sh; the Getting started
  checklist now lives in the Systems sidebar; Public URL labels; ops-agent
  /update on hosted installs.
- whats-new/v0.9.5.md, linked from both indexes.

Corrections found against code: the troubleshooting FAQ pointed at the target
agent's Permissions tab (grants live on the caller's); schedule retries
default to 0 in the UI and REST (only the MCP create tool defaults to 1);
Workspace clients do see the live card; voice-replies' settings location and
STT fields; the sync-poll interval is a default; two heading anchors and a
leftover issue link.

FAQ 474 -> 499 questions; index regenerated from headings (two underscore
anchors that never resolved are fixed).

Verification: relative link + anchor check 0 broken over 110 pages;
issue-number / codename grep 0 hits in added lines; deploy public-safety greps
and the enterprise-docs-guard pattern 0 hits.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

@vybe vybe left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reviewed: docs-only sync; links, anchors, codename and public-safety greps verified clean.

@vybe
vybe enabled auto-merge (squash) September 17, 2026 15:31
@vybe
vybe disabled auto-merge September 17, 2026 15:33
…sted only for now

Ability.ai does not currently offer managed Trinity hosting. Remove the
"Cloud Hosted (ability.ai)" comparison and Option A walkthrough from the
deploying hub (install paths become the section; the self-hosted options are
re-lettered A–D), and rewrite the FAQ answer that pointed users at a hosted
sign-up. The licence answer no longer mentions "a managed instance".

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@vybe
vybe enabled auto-merge (squash) September 17, 2026 15:34
@vybe
vybe merged commit 2899e28 into dev Sep 17, 2026
26 of 27 checks passed
@vybe
vybe deleted the docs/user-docs-0.9.5-delta branch September 17, 2026 15:40
vybe pushed a commit that referenced this pull request Sep 17, 2026
…an install (#2883)

Ability.ai does not offer managed Trinity hosting, and docs PR #2869 already
removed it from the user docs. The README still offered it in three places.

- "Deploy an instance" and the self-host aside now point at the guided
  DigitalOcean install as the least-work path to a server.
- The licence line drops "or a managed instance".
- The deployment-questions contact stays.

Co-authored-by: sim <sim@example.com>
Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
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.

2 participants