Skip to content

docs(FI-609): clarify signals deletion help for agent and inference - #2035

Merged
RohithSangati merged 3 commits into
digitalocean:mainfrom
aupadhyay-shark:fi609-deletion-docs-sync
Oct 11, 2026
Merged

RohithSangati merged 3 commits into
digitalocean:mainfrom
aupadhyay-shark:fi609-deletion-docs-sync

Conversation

@aupadhyay-shark

@aupadhyay-shark aupadhyay-shark commented Oct 11, 2026 •

Copy link
Copy Markdown
Contributor

Summary

Docs-only sync for doctl signals deletion help text with live product behavior (FI-609).

  • Cover both Harness Runtime --type agent and Serverless Inference --type inference (parent help previously mentioned only “managed agent”).
  • State clearly: on create → collection off for that scope + in-scope data hidden from Signals reads immediately; purge is async.
  • Failed jobs: data stays hidden / collection stays off; create again to retry; transient retries may happen while still active.
  • Note: aggregated Insights/metrics may still show historical summaries (not recoverable session/dialogue content).
  • Wording polish: “Harness Runtime agent” instead of “managed agent” in customer-facing help.

No business logic, flag, or API wire changes.

Sync set

Surface PR
doctl this PR (#2035)
godo digitalocean/godo#1161
openapi digitalocean/openapi#1263

Related prior art: #2021, digitalocean/openapi#1260, digitalocean/godo#1152.

Tracking: FI-609

Testing

  • go test ./commands -run SignalsDeletion -count=1 ✅
  • Built binary: signals deletion -h / create -h wording check ✅

Sync CLI help with product behavior: hide + collection-off on create for
both Harness Runtime agent and Serverless Inference, failed-job retry,
and a note that aggregated Insights/metrics may still remain.

No command or API behavior changes.

Co-authored-by: Cursor <cursoragent@cursor.com>
aupadhyay-shark and others added 2 commits October 11, 2026 21:44
…nv id

Use customer-facing "conversations" instead of sessions/dialogues, state
that inference deletion is team-wide, and spell out that --agent-id is the
Harness Runtime Environment Config ID.

Co-authored-by: Cursor <cursoragent@cursor.com>
Use conversation-scoped claims, plain-language team-wide inference
(at or before the deletion request), wait-before-re-enable and export
retention on the parent help, and drop markdown bold that rendered in CLI.

Co-authored-by: Cursor <cursoragent@cursor.com>
@RohithSangati
RohithSangati merged commit 76c46ff into digitalocean:main Oct 11, 2026
9 checks passed
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