Skip to content

Missing icons on Agent, Provider, and Skill partition roots — blank cards in search results on every distributed portal #132

Closed

Description

@sierragolflima

Problem

The Agent, Provider, and Skill partition space roots have no Icon set in their IStaticRepoSource.PartitionRoot definitions. On any distributed (Orleans/PG) portal, these nodes appear as blank cards in search results and catalogs wherever a space root is displayed. The issue affects every deployment running Memex.Portal.Distributed with the default Features:StaticRepoSync:Partitions list — it is not specific to any single deployment.

A secondary issue: the Doc partition root has had Icon = "/static/NodeTypeIcons/organization.svg" since 0cb624cd0 (2026-06-10), but any deployment whose Doc partition was last imported before that date will show a blank Documentation card until the import re-runs with the updated fingerprint.

Root cause

The three PartitionRoot definitions in src/MeshWeaver.AI/ do not set an Icon field:

File Partition Current Icon
src/MeshWeaver.AI/AgentStaticRepoSource.cs Agent not set
src/MeshWeaver.AI/ModelStaticRepoSource.cs Provider not set
src/MeshWeaver.AI/SkillStaticRepoSource.cs Skill not set
src/MeshWeaver.Documentation/DocumentationStaticRepoSource.cs Doc /static/NodeTypeIcons/organization.svg ✓
src/MeshWeaver.AI/HarnessStaticRepoSource.cs Harness /static/NodeTypeIcons/bot.svg ✓

All icon files referenced below exist in src/MeshWeaver.Graph/Icons/ and are served under /static/NodeTypeIcons/. There are no broken file references — the problem is purely that the three sources never set an Icon on their PartitionRoot.

Fix

Add Icon = to each of the three PartitionRoot definitions, following the same pattern as DocumentationStaticRepoSource and HarnessStaticRepoSource:

AgentStaticRepoSource.cs — PartitionRoot:

Icon = "/static/NodeTypeIcons/sparkle.svg",

ModelStaticRepoSource.cs — PartitionRoot:

Icon = "/static/NodeTypeIcons/database.svg",

SkillStaticRepoSource.cs — PartitionRoot:

Icon = "/static/NodeTypeIcons/sparkle.svg",

Adding the Icon field changes the partition root's content, which changes the source fingerprint. On the next portal startup, StaticRepoImporter detects the new fingerprint, runs a fresh import, and upserts the partition root with the icon — no manual SQL, no data loss, no restart beyond the normal rolling update.

Scope

Every partition root emitted by an IStaticRepoSource should set a meaningful Icon. The pattern to enforce: when adding a new DB-synced partition, its PartitionRoot must include both Icon and NodeType (as DocumentationStaticRepoSource and HarnessStaticRepoSource already do).

Activity

  1. rbuergi commented on Jun 30, 2026

    @rbuergi
    Contributor

    Fixed in #135 (folded in with the AI-content-source bundling — same files). Set Icon on the three PartitionRoots: Agent → sparkle.svg, Provider → database.svg, Skill → sparkle.svg (matching Doc = organization, Harness = bot). The content change bumps the source fingerprint, so the next portal boot re-imports each root with the icon — no manual SQL.

    To verify: on a distributed portal, the Agent / Provider / Skill space roots show icons (not blank cards) in search results and catalogs.

    Note on the secondary finding (a Doc partition imported before 0cb624cd0 shows a blank Documentation card): that's data-state on old deployments — it self-heals on the next import since the fingerprint already changed; no code change needed.

  2. rbuergi commented on Jun 30, 2026

    @rbuergi
    Contributor

    Fixed in #135 (merged 2026-06-30). The built-in AI content sources (Agent / Provider / Skill) are now bundled via AddBuiltInAiContentSources(), and each PartitionRoot carries an Icon (Agent → sparkle, Provider → database, Skill → sparkle), so the partition-root cards render an icon instead of a blank card in search results. Closing as completed.

  3. sierragolflima commented on Jul 7, 2026

    @sierragolflima
    CollaboratorAuthor

    Tested, works - Agent / Provider (=ModelProvider) / Skill have icons.

    Removed 'to be tested' label.

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

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions