Files
skillshare/wiki
Willie b80224f501 fix(ui): check agents on the Updates tab (#966)
* fix(ui): check agents on the Updates tab

Pressing Check on the Agents Updates tab marked every agent "Check
failed". The page marks the items of both kinds as checking and turns
the ones without a result into failures, but the check stream only ever
looked at the skills source, so no agent got a result.

The stream now reports agents as well, using the checks the CLI runs for
`skillshare check agents`, and counts their remotes in the progress
total. A check limited by names still covers tracked repos and skills
only.

A locally edited agent can now show "Modified locally". The link that
lists local changes reads skills only, so it is left out for agents.

* fix(ui): apply skill check results to skills only

A mixed repository installed with --track for both kinds gives the skills
source and the agents source a checkout with the same folder name. The
check reports a tracked repo of the skills source under tracked_repos, but
the Updates tab copied that status to every item whose repo folder matched,
whatever its kind. A full check hid this because the agents' own results
are applied afterwards. "Check N selected" returns no agent results, so
checking the skills repo replaced an agents repo's "Update available" or
"Modified locally" with "Up to date".

The per-skill results had the same gap: a skill result could land on an
agent of the same name. Both loops now match skills only, as the update
results already do.
2026-11-20 17:15:55 +08:00
..

skillshare Wiki Router

The wiki stores development background, procedures, references, and history, but no task needs all of it at once. Rules that apply to every task live in the root AGENTS.md. wiki/ai-context.json is the only source of truth for topic-to-source mappings.

python3 scripts/ai-context.py list
python3 scripts/ai-context.py <topic>

Task Routing

Topic Use when Main sources
architecture Tracing repository structure, data flow, or CLI/Web API boundaries architecture.md
cli-development Adding or changing Go CLI commands, flags, handlers, TUIs, or mutating behavior cli-development.md
testing Building, testing, reproducing bugs, or using the devcontainer/ssenv testing.md, CONTRIBUTING.md
e2e-runbooks Writing or running ai_docs/tests E2E runbooks, or verifying on a Windows guest e2e-runbooks.md
frontend Changing React, CSS, layout, or visual behavior in the dashboard or website frontend.md, website/AGENTS.md
herdr Changing the native Herdr panel, gallery packages, or layout integration herdr.md, herdr/AGENTS.md
documentation Updating README files, website docs, flags, translations, or the built-in skill documentation.md, CONTRIBUTING.md
release Writing changelogs or release notes, bumping versions, tagging, or releasing release.md
audit Running read-only consistency audits audit.md
pull-requests Opening a pull request or handling its review comments, including Codex review pull-requests.md
ai-context Maintaining router topics, budgets, and orphan checks ai-context.md

Run python3 scripts/ai-context.py check after changing topics. This table is the human entry point; the JSON configuration controls what the loader renders.

History (Milestone Logs; Read on Demand)

Completed milestones are recorded here and read only when relevant.

File Contents
OMP native support Native MCP/Hooks, safe Extension selection, bounded Plugin support and shared-cache blocker
Shared memory notes Shared Markdown source, CLI/API/dashboard, recent notes, trial/organization prompts, versioned edits and native memory boundaries
Git hooks management Config-mode destinations, includes, ownership, native verification and execution limits
Native hooks management Native formats, CLI/dashboard scope, ownership and verification evidence
MCP: Pi built-in only and tool policy 0.23.0 Pi migration, per-Agent tool policy translation, evidence and limits