Skip to content

feat(crm-client-workspace): v5 -- the widgets follow the specialist, and the agent sees them - #5782

Merged
gHashTag merged 1 commit into
masterfrom
spec/crm-client-workspace-v5
Oct 3, 2026
Merged

gHashTag merged 1 commit into
masterfrom
spec/crm-client-workspace-v5

Conversation

@gHashTag

@gHashTag gHashTag commented Oct 3, 2026

Copy link
Copy Markdown
Owner

Closes #5779

v5 of specs/automation/crm-client-workspace.t27. The host is the client chat in gHashTag/999-multibots-telegraf. The 999 PR, which binds every test below to the host, follows and will link back here.

The widgets follow the specialist

  • Who sees a widget: widget_shown(belongs_to_specialist, owner_is_chosen). A client widget shows under anybody; a specialist's widget shows only while that specialist is chosen.
  • Content belongs to the Blogger: the content widget (portrait gift plus story reel) has CONTENT_WIDGET_AGENT = "blogger". It had been on the card "always" since 2026-09-29.
  • The registry: WIDGET_IDS lists the eight widgets; CLIENT_WIDGETS = 6 of them are the client's.
  • One menu on the left: WIDGETS_IN_ONE_MENU, WIDGET_MENU_SIDE = "left", OPEN_WIDGETS = 1.
    • The waiting drafts are pinned above the menu (DRAFTS_PINNED_ABOVE_MENU).
    • The Queen is not a widget (QUEEN_IS_NOT_A_WIDGET).
  • Switching specialists: open_after_switch(chosen_has_widgets, open_still_shown) returns one of:
    • OPEN_SPECIALISTS_FIRST
    • OPEN_KEEPS
    • OPEN_FALLS_TO_CLIENT

The agent sees the widgets

  • The request field: WIDGET_CONTEXT_PARAM = "widgets" on a client thread's chat request carries the ids shown, the open one, and their state.
  • Caps: capped(length, cap) with WIDGET_TEXT_MAX_CHARS = 600 per value, WIDGET_LIST_MAX = 8, and WIDGET_CONTEXT_MAX_CHARS = 4000 for the whole block.
  • Context, not instruction: CONTEXT_INJECTED gains +widgets.
  • Who hears it: widget_reported(shown, client_thread), HIDDEN_WIDGET_NOT_REPORTED, WIDGET_CONTEXT_ONLY_IN_CLIENT_THREAD.

Gate
From the 999 checkout, tri spec-check reported:

== spec-check green -- crm-client-workspace.t27: 15/15, 0 of 15 vacuous, 17/17 controls, sealed
  • There are 14 new controls, one per new rule. They live in 999 apps/vibee-editor/render/src/spec/crm-client-workspace.controls.json.
  • PANELS = 7 is unchanged.
  • The seal is updated, and there is a NOW entry.

phi^2 + 1/phi^2 = 3 | TRINITY

🤖 Generated with Claude Code

…and the agent sees them

A widget is the client's (shown under anybody) or one specialist's (shown
only while chosen): the content widget is the Blogger's, templates are each
specialist's. One menu in the left column, one open, the drafts pinned above
it, the Queen not a widget (widget_shown, open_after_switch). A client
thread's request carries `widgets` -- ids shown, the open one, their state --
capped per value and as a whole and put beside the client's brief as
context; a hidden widget is not reported and the self thread ignores it
(widget_reported, capped). 15/15, 0 vacuous, 17/17 controls.

Closes #5779

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

phi^2 + 1/phi^2 = 3 | TRINITY
@github-actions

github-actions Bot commented Oct 3, 2026

Copy link
Copy Markdown
Contributor

📓 NotebookLM Notebook linked to this PR

This notebook contains session context, decisions, and artifacts for this work.

@github-actions

github-actions Bot commented Oct 3, 2026

Copy link
Copy Markdown
Contributor

PR Dashboard

Generated at: 2026-10-03 16:51:25 UTC

Summary

Status Count
Total Open PRs 46
PRs with Failing Checks 43
PRs with All Checks Green 3
READY 1
FAILING 43
PENDING 0
NO CHECKS YET 0

These columns do not partition: 1 + 43 + 0 + 0 = 44, and there are 46 open PRs. A PR is being counted twice or not at all.

Seal Status

  • ⚠️ STALE -- sha256(compiler.rs)=b45a356c2eb6 != manifest seal=87e5cbd3ad94.
    The committed NMSE numbers were certified against an older compiler.rs.
    Run scripts/reseal-check.sh locally for the two-step reseal command (advisory; not a merge gate).

This was referenced Oct 3, 2026
@gHashTag
gHashTag merged commit d995a31 into master Oct 3, 2026
31 of 32 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.

crm-client-workspace v5: the widgets follow the specialist, in one menu on the left, and the agent sees them

1 participant