Skip to content

Tracer: Set the local Human default name and resolve current mention labels #621

New issue
New issue
Closed
#628
Closed
Tracer: Set the local Human default name and resolve current mention labels#621
#628
Labels
area:fullstackEnd-to-end Host and Client implementationarea:ui-uxInteraction and visual experience; may accompany a code-layer areafeature:channelChannel chat, timeline, composer, and navigationfeature:identityPersonaBot identity, lifecycle, and deletionfeature:inboxBot Inbox and Human Inbox attentionready-for-agentFully specified, ready for an AFK agentscope:tracerHuman-testable implementation slice
Milestone
v1.1

Description

@DoodleBears
DoodleBears
opened on Oct 1, 2026

Parent

Spec #619, a native child of Human Inbox #126. Design authority: ADR-0103, delivered in PR #618.

What to build

The local Human can save or clear a default name in BotHarness plugin settings and immediately see that name across current Channel authors, Human member/receipt details, Human Inbox context and Bot-facing current Channel discovery/queries. Typed Human and PersonaBot mentions display the target's current name even in historical messages; changing either name preserves message content and all attention facts. This is the complete default-name path before Channel-specific overrides.

Acceptance criteria

  • Settings can save/change/unset the default Human name; unset resolves to Human and does not block first use.
  • Host owns the value under the existing Messaging authority; the authorized command derives the existing local Human ID, and names persist across Host restart.
  • Existing generated Human member labels inherit the new default; current members, author labels, receipts, Human Inbox source context and Bot-facing current queries use the same resolved name.
  • Existing Tracer: Trusted Bot @Human reaches personal Inbox mentions #549 trusted Human targets remain unchanged; Human and PersonaBot historical mention blocks resolve current names by typed ID, including different-length and Unicode renames.
  • Duplicate Human/Bot names remain allowed and type-disambiguated; plain same-name text is untouched; unavailable targets may use saved presentation fallback without name-based retargeting.
  • Source Event content and persisted mention spans remain unchanged, with no new Source Revision, unread changes, personal item duplication, action settlement, Admission or wake caused by naming.
  • Two browser windows converge on the committed name; native Session history and already assembled model input stay intact.
  • Focused observable Host/Bridge/Client coverage and a genuine DSH scene demonstrate settings save, real trusted @, Human and Bot renaming, historical Channel/Inbox labels and restart.
  • One implementation PR includes screenshots or video evidence and pauses for Human QA before the next issue.

Blocked by

Activity

  1. DoodleBears
    added this to the v1.1 milestone on Oct 1, 2026
  2. DoodleBears
    added
    ready-for-agentFully specified, ready for an AFK agent
    area:ui-uxInteraction and visual experience; may accompany a code-layer area
    area:fullstackEnd-to-end Host and Client implementation
    feature:channelChannel chat, timeline, composer, and navigation
    feature:inboxBot Inbox and Human Inbox attention
    scope:tracerHuman-testable implementation slice
    feature:identityPersonaBot identity, lifecycle, and deletion
    on Oct 1, 2026
  3. DoodleBears
    added a parent issue on Oct 1, 2026
  4. DoodleBears
    marked this as blocked on Oct 1, 2026
  5. github-project-automation
    added this to Roadmapon Oct 1, 2026
  6. DoodleBears
    marked this as blocking on Oct 1, 2026

  7. DoodleBears commented on Oct 1, 2026

    @DoodleBears
    DoodleBears
    on Oct 1, 2026
    ContributorAuthor

    Agent work claim

  8. DoodleBears
    added
    agent:activeOne or more coding-agent tasks currently claim this issue; see claim comments for task IDs
    on Oct 1, 2026
  9. DoodleBears
    added 9 commits that reference this issue on Oct 1, 2026

    test: cover Human name endpoints and live receipt names

    c867d08

    test: align new RPC claims with service declaration order

    df0770e

    fix: save Human names through explicit settings actions

    4265257

    docs: capture genuine Human name settings and Inbox E2E evidence

    69ff985

    merge: integrate current main and sequence Human names after usage re…

    d12a3e4

    fix: reuse active roster stream for Human name settings

    4997762

    docs: refresh Human name E2E evidence on current main

    d9b5e2d

    test: default the name verifier to the current main QA scene

    78b10ac

    fix(qa): preserve Human name E2E failures

    e17ad71

  10. DoodleBears commented on Oct 1, 2026

    @DoodleBears
    DoodleBears
    on Oct 1, 2026
    ContributorAuthor

    Agent work outcome

    • Agent: Codex
    • Task: codex/local/01a0f083-4337-71d2-8639-dec84699b8d9 (not a DSH Session)
    • State: paused — awaiting Human QA
    • PR: feat: local Human default names and current mention labels (#621) #628
    • Head: e17ad71
    • Scope delivered: optional local Human default name in plugin settings, stable Human identity, current Human/Bot labels in Channel and Inbox trusted mentions, current Bot query/context, persistence and reset.
    • Verification: genuine DSH settings and live-model mention flow, two-window convergence, light/dark and narrow layouts, clear default, cold restart; committed screenshots and results are linked in the PR. Final CI passed (1,610 tests plus lint/format/typecheck/build/docs). Spec and Standards reviews passed; Existing CodeRabbit findings were checked and addressed, and the bot confirmed the diagnostic fix. Its final incremental review is still running; check it before merge.
    • Remaining: Human QA and merge approval for this PR. Channel nickname overrides remain Tracer: Set and reset Human Channel nicknames in DM and Group headers #622, which starts only after Human QA approval of Tracer: Set the local Human default name and resolve current mention labels #621.
  11. DoodleBears
    removed
    agent:activeOne or more coding-agent tasks currently claim this issue; see claim comments for task IDs
    on Oct 1, 2026
  12. DoodleBears
    added a commit that references this issue on Oct 1, 2026

    feat: local Human default names and current mention labels (#621) (#628)

    f0f34fc
  13. DoodleBears
    closed this as completedin #628on Oct 1, 2026

  14. DoodleBears commented on Oct 1, 2026

    @DoodleBears
    DoodleBears
    on Oct 1, 2026
    ContributorAuthor

    Agent work outcome

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    area:fullstackEnd-to-end Host and Client implementationarea:ui-uxInteraction and visual experience; may accompany a code-layer areafeature:channelChannel chat, timeline, composer, and navigationfeature:identityPersonaBot identity, lifecycle, and deletionfeature:inboxBot Inbox and Human Inbox attentionready-for-agentFully specified, ready for an AFK agentscope:tracerHuman-testable implementation slice

    Type

    No type

    Projects

    • Roadmap
      Status
      Done

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions