Skip to content

Release command-center-ai 0.0.17: agent icons that come with an agent read - #23

Merged
MainSequenceDev merged 8 commits into
mainfrom
development
Oct 22, 2026
Merged

MainSequenceDev merged 8 commits into
mainfrom
development

Conversation

@MainSequenceDev

Copy link
Copy Markdown
Contributor

Releases command-center-ai 0.0.17: AgentIcon draws agent icons that come with an agent read.

The platform's agent list, detail and semantic search now accept include_icons; each agent then carries command_center_icon, the agent icon projection's object plus idle, the idle sprite inline ({mime, bytes}, base64). A list can draw every icon with the list itself instead of waiting for the projection and loading one sprite per agent.

  • normalizeCommandCenterAgentIcon(agentUid, value) reads one icon in either shape and keeps a usable idle.
  • primeAgentIcon({url, idle}) seeds the byte cache entry of the delivery URL without a request (APNG still included); a fresh entry is kept, an older one replaced only when the bytes differ.
  • The cache compares a platform ETag without its quotes, so a seeded icon and a later revalidation of the same bytes keep one object URL.
  • AgentIcon takes an optional icon; given (even null) it skips the projection and draws the inline sprite without a request, also outside the engine. With idle null it loads url as before.
  • ADR 090 amended (section 8), READMEs, conversation contract and changelog updated.

Compatibility: additive npm API only. No stylesheet class, storage key, skill, installer, SDK peer range or called-route change. An application that passes no icon renders exactly as before.

Commits: 1a01dba (feature), 2683193 (chore(release): prepare command-center-ai 0.0.17).

Verification (Node 22.22.0): npm run check, npm run ai:check, npm run ai:test (429 passed, 1 todo; 10 new tests), npm run ai:build, command-center-ai test:browser (6 passed), npm run direction:check, scripts/verify-packed-consumer.mjs; npm pack --dry-run shows 0.0.17.

🤖 Generated with Claude Code

MainSequenceDev and others added 8 commits October 18, 2026 10:18
Show failed or refused sign-off messages without changing the signed-in card.
Keep provider details open when Escape belongs to a host dialog, and respect
already-handled Escape events. Cover both fixes with regression tests.

Align the model-provider skill, guide, and READMEs with per-record user,
editor, and owner policies while preserving the credential disclosure.

Fixes #18
Fixes #19
Fixes #20

Co-authored-by: Codex <codex@openai.com>
Pull request #21 was merged with "Rebase and merge", so main received
76b7246, a copy of development's 21c127e under a new hash (same patch-id,
same tree). development was then no longer an ancestor of main: the next
pull request from development would carry the commit a second time, and
pushing development to main would be refused as a non-fast-forward.

This merge records 76b7246 as merged, with the "ours" strategy. No file
changes: its tree equals the tree of both parents.

Evidence:
  git patch-id --stable on 21c127e and on 76b7246 -> both 0b387bd472de
  origin/main^{tree} == origin/development^{tree}
  after: git merge-base --is-ancestor origin/main development -> yes
         git diff --stat origin/development development -> empty

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

Proposed, requirements only. The composer and thread gain attachments
under a versioned runtime contract owned by MS Tau SDK ADR 0024. Answer
source references are left to a follow-up decision. No compatibility
axis changes.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
npm audit fix, without --force. The root lockfile moves undici,
fast-uri and source-map-js (development only) to patched versions and
now reports no vulnerabilities. The docs-site lockfile takes Docusaurus
3.10.2 and its patched transitive dependencies (63 -> 46 alerts); the
rest need `--force`, which would downgrade Docusaurus to 3.7.0. No
published package's runtime dependencies change.

Verification (Node 22.22.0): npm run check, npm test, both packages'
test:browser, test:package-smoke, verify-packed-consumer and
npm run docs:build pass.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Releases the Unreleased fixes: sign-off error reporting (#18), the
model-provider skill's per-record access policies (#19), and dialog
Escape handling (#20), with the SDK ADR 018 attachment requirements as
documentation only. Packaged skill content changes; no npm API,
stylesheet class, storage key, skill name or path, installer or route
change. The SDK peer range stays ^0.5.3, and the SDK stays 0.5.18. The
compatibility table's Chat row now names 0.0.16.

Verification (Node 22.22.0): npm run check, npm test (SDK 347 + 137,
AI 419 + 15), both test:browser suites, test:package-smoke,
verify-packed-consumer and docs:build pass; npm pack --dry-run shows
@dev-mainsequence/command-center-ai 0.0.16.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The platform's agent list, detail and semantic search now accept
include_icons (Main-Sequence-Server-Side/tdag-django#1146): each agent
carries command_center_icon, the projection's icon object plus idle,
the idle sprite inline as {mime, bytes}. A list can then draw every
icon with the list itself instead of waiting for the agent icon
projection and loading one sprite per agent.

- normalizeCommandCenterAgentIcon(agentUid, value) reads one icon in
  either shape and keeps a usable idle (image/png or image/svg+xml);
  normalizeCommandCenterAgentIcons uses it. CommandCenterAgentIcon gets
  an optional idle, with the new CommandCenterAgentIconImage type.
- primeAgentIcon({url, idle}) seeds the byte cache entry of the
  delivery URL without a request, with the APNG still. The entry is
  loading at once, so a load started meanwhile waits for it; a fresh
  entry is kept, an older one refreshed and replaced only when the
  bytes differ.
- The cache compares a platform ETag without its quotes: the platform's
  ETag is the quoted SHA-256 of the bytes, so a seeded icon and a later
  revalidation of the same bytes keep one object URL.
- AgentIcon takes an optional icon. Given (even null), the projection
  is not consulted and the inline sprite is seeded before the idle
  image's own load, so it draws without a request, also outside the
  engine; with idle null it loads url as before.
- ADR 090 amended (section 8); module READMEs, the conversation
  contract and the changelog's Unreleased entry updated.

Compatibility axes: additive npm API and the read of the platform's
additive command_center_icon. No stylesheet class, storage key, skill
name or path, installer behaviour, SDK peer range or called route
changes. The packaged skills name AgentIcon without its props, so their
content is unchanged.

Verification (Node 22.22.0): npm run check, npm run ai:check,
npm run ai:test (56 files, 429 passed, 1 todo; 10 new tests),
npm run ai:build, command-center-ai test:browser (6 passed),
npm run direction:check and scripts/verify-packed-consumer.mjs pass.
docs:build was not run: it fails in a scratch worktree with symlinked
node_modules; the Deploy SDK Docs workflow builds it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Releases the Unreleased change: AgentIcon draws icons that come with an
agent read (include_icons, Main-Sequence-Server-Side/tdag-django#1146),
with normalizeCommandCenterAgentIcon and primeAgentIcon (ADR 090,
section 8). Additive npm API; no stylesheet class, storage key, skill
name or path, installer or route change. The SDK peer range stays
^0.5.3, and the SDK stays 0.5.18. The compatibility table's Chat row now
names 0.0.17.

Verification (Node 22.22.0): npm run check, npm run ai:check,
npm run ai:test (429 passed, 1 todo), npm run ai:build,
command-center-ai test:browser (6 passed), npm run direction:check and
scripts/verify-packed-consumer.mjs pass; npm pack --dry-run shows
@dev-mainsequence/command-center-ai 0.0.17.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@MainSequenceDev
MainSequenceDev merged commit bfd77f8 into main Oct 22, 2026
1 check 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.

1 participant