The Clean style read flat next to the Apple-style design: menus, the
shortcut HUD and the stuck toolbar were opaque slabs, and most layers
vanished the instant they closed. Pages, cards and the sidebar stay
solid; only layers that float over content become translucent, and
prefers-reduced-transparency turns them solid again.
Menus now fade out instead of unmounting at once (usePresence), the
segmented-control pill slides between segments, and switches, the pill
and the tree divider move on critically damped or lightly bouncing
spring curves. Dialogs and the floating selection bar are often
unmounted by their callers, so exitGhost plays their exit on a frozen,
inert copy; no copy plays when the page goes with them, and reduced
motion gets a short fade. Toast, collapse and row-exit timings follow
the motion spec, and the toast countdown pauses in place on hover.
* chore(main): release 0.30.2
* chore(release): synchronize release metadata
* docs(changelog): describe 0.30.2 for users
Replace the generated commit list with user-facing entries for the three
fixes users can notice: the Python docstring audit severity, the dashboard
restart on Homebrew, and the root-scope nested repo check. Dashboard-only
UI polish and the test-only CI fix are left out.
---------
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Willie <egg358358@gmail.com>
With git_root: root, commit and push aborted on every tracked skill repo
because NestedRepos flagged any directory with its own .git. Tracked repos
are listed in the managed .gitignore block, so git add -A never stages
them, and the suggested remedy (renaming .git to .git.disabled) breaks
skillshare update for those repos.
NestedRepos now asks git check-ignore about each nested repo and leaves
out the ones git ignores and does not track. A repo already committed as
a gitlink is still reported, since staging would update it. Paths are
checked one at a time because git refuses a whole batch when one path
lies inside a gitlink, and any git error keeps the warning.
Closes#820
docker-sandbox-online failed whenever a commit landed on main while
TestUpdate_TrackedRepo was cloning runkids/skillshare (about 45 seconds).
The update then pulled that commit and the audit rejected the candidate:
.devcontainer/bin/dev-servers was an absolute symlink to
/workspace/.devcontainer/dev-servers.sh, which escapes the checkout. The
same block hits anyone who tracks this repository and updates it.
Point the symlink at ../dev-servers.sh, which resolves to the same file in
the devcontainer. The test no longer expects "up to date", because a
concurrent push is outside its control; it checks that the update
succeeds and passes --force for the same reason the install does: the
repository carries audit fixtures, and the test covers track and update
mechanics, not audit policy. The token-auth variant gets the same --force.
The severity counts are filter toggles but had no hover, press or
selected look, so an active filter showed only as a blue number. The
scanning note and the LOW/INFO rows popped in and out, shoving the
results around; they now grow in and shrink away. The note waits 400ms
before growing, so a quick rescan after a threshold change no longer
bobs the list down and back up. The scan progress bar eases forward like
the other bars, and Playful's hover lift is limited to fine pointers so
a tap does not leave a control stuck out of place.
The filter's label sat above the select, so in a row centred on the
whole field the "showing 5, hiding 13" counts floated between the label
and the box. The name now goes inside the trigger as a prefix, as on
the audit rules page, so the select and the counts share one line. The
control keeps its accessible name.
Every page faded in over 200ms while sliding up 8px. Moving between
pages in the sidebar is the most frequent action in the dashboard, so
the slide made each click feel slow and shifted the content the user
was comparing. Pages now use animate-page-in, a 120ms opacity-only
fade, which softens the swap without delaying it or moving anything.
The shared fade, dropdown and dialog entrances also ignored
prefers-reduced-motion and kept sliding or scaling. Under reduced
motion they now keep only their fade; a dialog changing step still
swaps without animation, as before.
The frontend wiki and the UI style skill told contributors to put
animate-fade-in on page roots; they now name animate-page-in and keep
animate-fade-in for in-page reveals.
Release-As: 0.30.2
The switch knob now slides by transform, but the mixed state still
centred it with justify-content. Going from on to mixed moved the knob
to the centre at once while its 14px transform eased back to zero, so
for a few frames it stuck out past the track's right edge. A folder
switch in the skill tree hits this when one child is turned off.
Mixed now centres the knob by transform too, so every change between
off, on and mixed is a single slide that stays inside the track.
Several controls changed state with no motion, which made them feel
unresponsive: a button gave no sign it was pressed, a switch knob jumped
to the other end, the bulk-selection bar popped in, and the copy menu on
the memory page appeared at once. Toasts also left sideways although
they come in from below.
Buttons now scale down slightly while pressed; playful buttons sink
onto their hard shadow instead. Switch knobs slide across the track,
the bulk bar rises from the bottom edge, the memory copy menu uses the
existing dropdown entrance, and toasts leave the way they came in, in
200ms. Reduced-motion settings keep the bulk bar and toasts to a fade.
The skill detail page kept two fixed columns at every width: the
SKILL.md view beside a 330px info card, and a 240px file tree beside
the file viewer. On a phone the info card covered the content and the
content column shrank to a few characters. Below 1024px the columns
now stack.
The tab bar's preview/raw toggle squeezed the tabs onto two lines at
phone width; controls that do not fit now wrap above the tabs and stay
right-aligned, so the tabs keep their underline. The project Hooks tab
already wrapped this bar with its own flex-wrap, which the shared rule
now covers.
The page header kept the title and its action buttons on one row, and
the buttons do not shrink. At phone width the buttons took most of the
row, so the subtitle was squeezed to one character per line (the Skills
page at 390px). The title now keeps at least 280px and the actions wrap
below it when they do not fit; desktop layout is unchanged. The Hooks
page's own flex-wrap override is no longer needed.
After an install, the warnings dialog put lines like "audit findings
at/above block threshold (CRITICAL); proceeding due to --force" and
"recorded 1 accepted finding(s)" in the findings list as rows with an
info icon, in untranslated English. They read like findings without a
severity, and a forced install showed each skill's status twice among
its findings.
Status lines now sit in a note above the list, grouped by skill, and
the four audit status lines the installer writes are translated. The
list holds only findings.
Credential-access rules match whole lines, so a Python docstring that
named ~/.aws/credentials in a `cat` example counted as a CRITICAL read and
blocked the mcp-sentinel skill at the default threshold (#817).
In .py files, a built-in CRITICAL credential-access match on a comment-only
line, or inside a string that is a whole statement such as a docstring, is
now HIGH: it still shows, and still blocks under a HIGH threshold. A small
tokenizer decides this and keeps CRITICAL wherever it cannot be sure the
line never runs: argument, assigned and bracketed strings, f-strings and
their replacement fields, code before a trailing comment, files that read
__doc__ or use bare CR line breaks, and explicit severity overrides.
A lowered finding carries severityContext "python-inert" (JSON, SARIF,
`audit rules --format json`), and the dashboard, CLI text output, both
audit TUIs, install/update warnings and the markdown report say it was
lowered from CRITICAL, so it is not mistaken for a changed rule.
Closes#817
On a Homebrew install the dashboard runs from a versioned keg that `brew upgrade` removes, so the restart after "Update now" exec'd a deleted path. It now restarts through <prefix>/bin/skillshare, which Homebrew keeps linked to the installed version.
Fixes#815
* chore(main): release 0.30.1
* chore(release): synchronize release metadata
* docs(changelog): describe 0.30.1 for users
The generated entry listed the Release-As commit as a change and used
commit subjects. Replace it with what users see: the Hubs refresh button
and the parallel plugin update check.
---------
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Willie <egg358358@gmail.com>
The pending range adds one small dashboard button (#814) and a plugin
check speed-up (#812). The maintainer wants it shipped as 0.30.1 rather
than the 0.31.0 a feat commit would select.
Release-As: 0.30.1
The Hubs page keeps a hub's skill list for two minutes and does not
refetch on window focus. The server reads the index fresh on every
request (git hubs are re-cloned), so after someone pushes an updated
skillshare-hub.json the only way to see it was to wait or reload the
whole page.
A refresh icon button next to the filter refetches the list on demand.
It spins and is disabled while loading; the current list stays on screen,
and a failed fetch shows the existing error note above it. Your own
(draft) Hubs are local and do not get the button.
* perf(plugin): check every plugin at once and skip sources that did not move
The Plugins page's update check read every Agent CLI, cloned and hashed
every source, and asked npm about every package one after another, so it
grew with each plugin added. A single Agent CLI that stopped answering
held the whole page at "Checking for updates" with no way to tell which
plugin was stuck.
The check now asks every Agent and checks every plugin at the same time.
Plugins share one read of each Agent and each source, so an Agent with
many plugins is still asked once, and a plugin waits only on its own
Agents, including when proving its own leftover installs. Before downloading a remote source with no pinned ref, the
check asks the remote which commit its default branch points at with
`git ls-remote` and reports no update when that is the installed commit.
A check of three unchanged GitHub plugins on two Agents went from 4.3s
with three clones to 0.6s with none.
The dashboard reads the check from a new stream, GET
/api/plugins/check/stream, that sends each plugin as soon as it is
checked. The page marks rows as they arrive and counts progress in the
header. The stream stops waiting after 60 seconds: a plugin bound to an
Agent that has not answered by then shows "Check failed" with the
reason, and plugins on other Agents are unaffected. There is no limit on
how many plugins run together, because plugins waiting on a hung Agent
would otherwise hold every slot and starve the rest.
A cancelled command did not return when the Agent CLI was a shim that
starts the real client, such as an npm, mise or volta wrapper: killing
the shim left the child holding its output, so the command waited until
the child exited and no timeout took effect. Commands now stop waiting
for output two seconds after they are cancelled; a command that exits on
its own while a helper keeps its output open still counts as answered.
* fix(ui): offer every update the Plugins page shows in the update dialog
The header counted updates from the per-plugin marks, but the update
dialog offered only the targets in the last completed check's plan. Two
cases left the header saying Update N with nothing to tick in the dialog:
a first check that broke off after finding an update never set the plan,
and a recheck that could not reach an Agent kept that Agent's earlier
update while the plan said blocked.
The dialog's plan is now derived from each plugin's last answer together
with the kept updates, so a kept update stands in for the blocked or
missing answer and both always agree. A broken-off check also keeps the
answers it did receive.
* chore(main): release 0.30.0
* chore(release): synchronize release metadata
* docs(changelog): describe 0.30.0 for users
The generated entry listed commit subjects. Users need the migration step for the new host rule and what each fix changes for them.
---------
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Willie <egg358358@gmail.com>
0.30.0 changes which addresses the dashboard answers at, which matters
to anyone who opens it by a domain name, so the Latest callout leads
with that and points to --trusted-origin. Also credits the contributors
of #805, #806 and #809.
DNS rebinding lets a page point its own domain at the user's machine,
which makes its requests same-origin to the dashboard, so the CSRF
guard cannot refuse them. Only the MCP, Hooks and Plugins routes
required a localhost or IP Host, so such a page could still install,
sync and push. That rule also blocked those three pages for people who
run the dashboard behind their own reverse proxy (#809).
The dashboard now answers every route only at localhost, an IP address,
the --host name, and origins given with --trusted-origin or
SKILLSHARE_UI_TRUSTED_ORIGINS. Configuration stays outside config.yaml
so the dashboard cannot widen its own trust through its config API. A
trusted origin must match the Host with its scheme, and an Origin
header, when sent, must be that origin. A refused browser gets a page
with the exact setting to copy, the API gets it in the error, and the
server log names each refused Host once.
BREAKING CHANGE: a dashboard opened by a domain name, such as a reverse
proxy, a Tailscale or mDNS name, or a Docker service name, now returns
403 on every page until that address is trusted, for example with
`skillshare ui start --trusted-origin https://skills.example.com`.
Release-As: 0.30.0
A web page can submit a form or a no-cors fetch to the local dashboard
without a CORS preflight, and the handlers accept a text/plain or empty
body. Only the MCP, Hooks and Plugins routes checked where a request
came from, so any site the user visited could add targets, install,
sync, commit, push or upgrade, whenever the browser let the request
reach localhost.
Every POST, PUT, PATCH and DELETE now needs Fetch Metadata, when sent,
to say same-origin, and Origin, when sent, to match the Host. A client
that sends neither, such as curl, is unchanged, because a page cannot
make a browser omit both on a cross-origin request. The update stream
runs updates over GET, as EventSource only opens GET, so it gets the
same check.
The nginx example now forwards $http_host, which keeps the port, since
a proxy that drops it would now fail every change, not only MCP.
The Hooks page uses the same DNS rebinding guard as the MCP page
(requireLocalHooks), so through a domain name or a reverse proxy its
requests return 403. The reverse proxy note only mentioned MCP, so a
user behind a proxy had no warning that Hooks would fail too.
The Claude manifest fallback from #806 offered Codex more than it can
install:
- A Claude package whose only parts are ones Codex does not read, such
as agents, was offered to Codex with no components, so Codex would
install an empty plugin.
- When Codex's own catalog pointed at a folder it rejects, the whole
candidate could be replaced by the Claude catalog's folder, which now
carries a Codex fallback. Codex reads only its own catalog, so it
would never install from that folder.
#806 also stopped every Agent from using a later catalog's folder when
the first one was rejected. Only Codex needs that, since only Codex
reads one catalog exclusively, so other Agents get the old behaviour
back.
Codex accepts Claude plugin manifests natively, but discovery omitted
Codex for packages such as Matt Pocock's skills. Select that supported
fallback without rewriting package resources or invocation policies.
Match native root and manifest precedence, retain rejected own-catalog
packages, and add discovery and snapshot regression coverage.
Refs #805
* chore(main): release 0.29.2
* chore(release): synchronize release metadata
* docs(changelog): write user-facing notes for 0.29.2
The generated entry listed commit subjects, including a docs-only
commit, without saying what users can now do or what the audit fix
prevents.
---------
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Willie <egg358358@gmail.com>
The dashboard reference walked through each Targets page control but
not the search box #799 added above the include/exclude preview, which
is also shared by project pages and the Extras Edit target dialog.
Release-As: 0.29.2
* feat(ui): search the include/exclude preview list
With dozens of skills, finding one row in the filter preview meant
scrolling the whole list before a click could include or exclude it.
A search box above the preview narrows the rows by name, ignoring case,
and marks the matching text. It only narrows what is shown; the filters
and the summary still cover every row.
The preview is shared, so the search appears on the project page, the
target page, and the Extras edit-target dialog. Switching between skills
and agents clears it, since a skill name rarely means anything as an
agent search.
Closes#798
* fix(ui): hide the stray scrollbar on the skills tab bar
The tab bar scrolls sideways at phone width, and overflow-x: auto makes
the other axis auto too. In the Clean style each tab hangs 1px below the
bar to cover its underline, so the bar overflowed by 1px and Chrome drew
the app's 8px custom scrollbar as a small dark pill at its right end.
Clipping the vertical axis keeps the sideways scroll and the underline.
The #796 wording attached "including direct-file and agent audits" to the
special-target error, so the sentence read as a repeated list and no longer
said that links to ordinary files keep text scanning in those audits. The
translations had dropped that scope entirely. Split it into two sentences
and restore the scope in every locale.
A named pipe can block collection, integrity hashing or uncached skill
metadata reads indefinitely. Require resolved regular files at each read
boundary while preserving symlink accounting and integrity evidence.
Cover the paths with bounded FIFO regressions and generated filesystem
cases, and update the Nix vendor hash and integrity-rule documentation.
* chore(main): release 0.29.1
* chore(release): synchronize release metadata
* docs(changelog): describe 0.29.1 for users
The generated entry only listed commit subjects; spell out what changed for people who share config.yaml, how to keep a project machine-local, and the branch picker fix.
---------
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: sim <sim@example.invalid>
* fix(projects): save new projects in config.yaml again
v0.29.0 wrote every project add, edit and remove to a machine-local
registry, so a project added on one machine never reached config.yaml
or the other machines that share it (#792). Most people share one
config.yaml and expect a new project to follow it.
config.yaml is the default again. Machine-local storage stays as an
explicit choice: --machine-local on add, or projects_storage:
machine-local for every new project, with --shared to override it.
The new share command moves a local project into config.yaml, and
localize still copies one to this machine. Edits and removals stay in
the layer that owns the project; removing a local copy of a
config.yaml project keeps config.yaml's version unless --shared asks
to remove both, so one machine cannot silently drop a project for
the others. Exclusions written by v0.29.0 are left as they are.
The dashboard picks storage once, in the Add project dialog, and
offers the two removal choices only where both copies exist. Moving a
project between layers stays a CLI command, so the detail page keeps
one job.
Closes#792
* fix(projects): recheck both layers after a confirmation, sync the saved key
remove and share ask before taking the config lock, then compared only
the merged entry after locking. A share or localize from another
terminal moves a project between layers without changing that entry, so
a remove confirmed for this machine's copy could then delete config.yaml's
declaration for every machine, and a confirmed share could overwrite
config.yaml settings changed meanwhile. The recheck now compares the
owning layer and config.yaml's declaration too (ProjectLayerState).
Re-adding a project that v0.29.0 hid restores config.yaml's own key,
which can be spelled differently from the folder given to add (~/app
versus an absolute path). add --sync looked the project up by the given
spelling and failed with "project not found" after saving it; it now
syncs the key that was saved.
* test(projects): make the layer tests hold on Windows
The mutation-sequence test looked the shared project up by
filepath.Join, but the fixture spells config.yaml's key $ROOT/app;
on Windows the two spellings differ, so the lookup found nothing.
It now asks the config for the key it uses.
The remove save-failure test blocked the local registry, but removing a
config.yaml project now writes config.yaml. On Linux the registry check
still failed with ENOTDIR first, which hid the mismatch; on Windows that
reads as a missing file and the save went through. The test now blocks
config.yaml, as the edit save-failure test does, and its hook no longer
shadows the config path with the target path.
---------
Co-authored-by: sim <sim@example.invalid>
A skill installed from a non-default branch of an SSH or other-host
remote (git@host:o/r.git, Gitea, self-hosted HTTPS) could not switch
back to main: the Branch picker was greyed out with "This source can
only use its default branch" (#787). The picker reused /api/hub/refs,
which only lists refs for GitHub, GitLab and Bitbucket web URLs because
a hub entry pins its ref in the URL. Reinstalling from a branch does
not need that; the update endpoint already accepts any git source.
/api/hub/refs now takes anyGit, which lists a non-pinnable git source's
refs while still reporting pinnable=false. The detail page asks for it
under its own query key; the hub editors keep the old request, so they
run no extra ls-remote for sources they cannot pin.
Closes#787
Co-authored-by: sim <sim@example.invalid>
* chore(main): release 0.29.0
* chore(release): synchronize release metadata
* docs(changelog): describe 0.29.0 for users
The generated entry listed PR titles. It now says what each change
does for a user, with examples, folds the #785 follow-up into the
unreleased --min-severity feature it fixed, and credits the
contributors. Both changelog copies match.
---------
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: sim <sim@example.invalid>
Co-authored-by: Willie <egg358358@gmail.com>
Checking every user-visible change since v0.28.4 against the docs
found these gaps:
- ui.md: GET /api/audit now returns warnings and incomplete; an
incomplete scan warns instead of reporting all clear and appears
under Needs attention; a project branch switch records the branch in
.skillshare/config.yaml. Also fixes a lowercase sentence start.
- audit-engine.md: Markdown and SARIF carry the per-resource coverage
counts added in #756.
- audit-rules.md: the files row pointed at a "File Scoping" section
that does not exist; it now links to File Applicability.
- log.md: project localize logs a localize action.
- built-in skill: how an unreadable followed source link is reported.
Translations are updated to match.
The Latest callout still described v0.28.4. It now leads with the new
audit checks, the display-only --min-severity, incomplete-scan
reporting and dashboard branch switching, in every translated README.
Both contributors in this range are already listed.
* feat(audit): show unfollowed source links in Markdown and the TUI
When a followed source link could not be read, only text output (and
JSON's warnings/incomplete fields) said so. A Markdown report looked
like a full scan, and the TUI covered the warnings printed before it
opened, so a partial scan read as complete there. Item 25 of #746 asks
for incomplete status to stay visible in human reports, including
under --min-severity.
Markdown now ends its summary with a "Source links not followed"
section, led by an "Incomplete scan" line when a link could not be
read. The TUI summary line starts with the count in the warning
colour. JSON and SARIF are unchanged.
* feat(ui): mark a partial audit scan on the dashboard
The audit API dropped the source-link warnings the scan collected, so
the dashboard showed a scan that skipped an unreadable followed link as
complete. Item 25 of #746 asks for incomplete status to stay visible in
every human report, the dashboard included.
GET /api/audit and the stream's done event now carry warnings and
incomplete with the same meaning as `audit --format json`, and the
Audit page shows the count beside the Skills/Agents tabs.
* feat(ui): stop calling an incomplete audit scan all clear
After a scan that skipped an unreadable followed source link, the
Audit page still toasted "no dangerous content" and the Dashboard's
Quick Scan toasted "All clear", while the home page showed nothing,
so a partial scan still read as a clean one there.
Both toasts now warn that the scan is incomplete, and the home page's
"Needs attention" list gets a row linking to the Audit page. One
helper words the note for the Audit page label, both toasts and the
row.
---------
Co-authored-by: sim <sim@example.invalid>
With --min-severity set, the TUI dropped every result without visible
findings, so clean skills disappeared from the list and the tab count
shrank, while text and Markdown output kept them. The rule now lives in
audit.HiddenByFloor and both the TUI and text output use it: a floor
hides only a result whose findings all fall below it and that is not
blocked.
The dashboard severity buttons label themselves with the English
severity, matching the badge they show, so the six translated label
keys added for them are gone. AuditPage.test.tsx again asserts the
exact coverage line and count instead of any three digits, and drops a
rendered test that only checked translated labels. The audit-engine
paragraph about --min-severity now appears in all four translations.
Co-authored-by: sim <sim@example.invalid>
Reduce audit report noise without changing full findings, risk scores, severity gates or machine output. Reuse existing severity ordering and dashboard selection, and keep visible/hidden counts and incomplete-scan status explicit in human reports.
Co-authored-by: GPT-6.1 Sol <noreply@openai.com>
Co-authored-by: Willie <egg358358@gmail.com>
* feat(audit): inspect bundled hooks and settings
Bundled declarations can schedule commands and broaden permissions outside SKILL.md, while ordinary scanning skips hidden settings. Inspect the four explicit paths with bounded root-confined reads and structured findings so existing audit policy can review their potential execution.
Keep activation conditional and redact arbitrary arguments before reports. Register rule metadata through the existing structure analyzer and cover benign twins, parse gaps, source links, policy overrides, CLI/API output and a synthetic E2E runbook.
Co-Authored-By: GPT-6.1 Sol <noreply@openai.com>
* refactor(audit): parse bundled hook commands with a shell parser
The hand-written lexer for hook commands grew six similar quote and
paren scanners, and each review round found another shell form it
missed (comments after line continuations, nested backticks, `time -p`).
Parsing with mvdan.cc/sh/v3/syntax follows quoting, comments,
substitutions, loops, functions and heredocs the way bash does, so the
analyzer walks every call in the syntax tree instead. The wrapper table
(sudo, env, timeout, xargs, bash -c, git) and the POST and destination
rules are unchanged, now applied to unquoted argv words. A script fed to
a shell on stdin (`bash <<'EOF'`, `bash <<<`) is parsed like `bash -c`.
Statements before a syntax error are still inspected. bash runs some
forms the parser rejects (an array element assigned before a command),
so a rejected command also gets a word-level network check next to its
coverage gap, rather than dropping to MEDIUM.
The dependency adds about 0.26 MB to the release binary; vendorHash
follows the new go.sum.
* fix(audit): bound nested shell parsing and skip stdin data
A script nested in a substitution was inspected twice, once by reparsing
the outer shell's argument and once by walking the outer syntax tree, so
each `bash <<< "$(...)"` or `bash -c "$(...)"` level doubled the work and
a hook under 1 KB could stall an audit. Results are now remembered per
script text and depth, and one hook command may parse at most 1 MiB of
source in total, since deep nesting still costs quadratic time with the
cache alone. Past the budget the command is classified word by word and
gets a coverage gap, as a rejected command does.
Stdin was also treated as a script whenever a shell had a heredoc or
here-string, but `bash -c 'cat' <<<` or `bash ./script.sh <<<` hands it
to something else as data, which turned a lifecycle hook into a false
HIGH. Stdin is now parsed only for `-s`, or when there is neither `-c`
nor a script file operand. Option values (`-euo pipefail`, `-O extglob`,
`--rcfile f`) are not mistaken for a script file.
---------
Co-authored-by: GPT-6.1 Sol <noreply@openai.com>
Co-authored-by: sim <sim@example.invalid>
Two causes kept turning main red without any code change:
- docker-sandbox-offline failed when proxy.golang.org dropped a module
download mid-stream during the image build. The sandbox Dockerfile now
retries `go mod download` up to three times.
- Hosted macOS arm64 runners are often short, and the required
integration-test (macos-latest) job then fails with "The job was not
acquired by Runner of type hosted", which blocks merges. A workflow_run
follow-up re-runs such a job once, on the first attempt of a run from this
repository. It uses the single-job re-run endpoint because the job ends as
cancelled, and the docs do not say whether re-running failed jobs covers
that. Jobs that failed for other reasons are left alone.
Hosted macOS arm64 runners often fail to pick up the job ("The job was not
acquired by Runner of type hosted even after multiple attempts"), so the Nix
run turned red on most pushes while the Linux flake check passed. Go code on
macOS is already covered by the required integration-test (macos-latest); the
darwin package build mainly guards the flake and vendorHash, which only change
with flake.nix, flake.lock, nix/, go.mod or go.sum. Run it for those paths and
on manual dispatch.
* feat(ui): show a skill's branch and switch it from the detail page
A skill installed with --branch looked the same in the dashboard as one
from the default branch, and moving it to another branch meant a manual
reinstall from the CLI (#783).
The list, tiles, tree pane and Updates tab now tag the branch a skill was
installed from. The detail page lists the source's branches; picking one
confirms, then reinstalls through POST /api/update with a new `branch`
field, so the audit gate and the local-changes check still apply and a
branch without the skill leaves the install in place.
In project mode, reconciling config.yaml only added missing skills, so a
reinstall from another branch (the switch, or install --branch --force)
left config.yaml naming the old branch while the lock pinned the new
commit. Reconcile now moves the declared branch with the record.
Closes#783
* fix(update): make branch switches install the requested branch safely
Codex review of #784 found four ways a switch could misreport or lose work:
- A root skill installed as a full clone took the pull fast path on later
switches, pulling its current branch instead of the requested one. The fast
path now applies only when the checkout is already on that branch.
- A branch whose skill folder lacks SKILL.md replaced the skill with a plain
folder. A staged update now refuses a candidate without SKILL.md when the
installed copy has one, and keeps the install.
- Reconciling config.yaml from local metadata could rewrite a teammate's
newer branch declaration back to a stale one on an unrelated install. The
generic reconcile change is reverted; the switch updates only the switched
skill's declaration.
- The config editor cache kept the old branch after a switch, so a later save
could undo it. A successful switch now invalidates the config query.
---------
Co-authored-by: sim <sim@example.invalid>
Keep machine-specific project changes out of shared configuration while preserving shared registrations and making their origin visible. Handle missing replicated roots and preserve startup maintenance for mutating commands.
Extension and size filters could hide native executables and Python bytecode
inside document, image and cache paths. Classify bounded headers before those
filters, retain source boundaries, and report opaque and oversized file counts
separately from auditable text.
Keep archive signatures and uncertain headers informational rather than claiming
runtime analysis. Honor analyzer selection for file and dashboard scans, and
cover renamed payloads and benign twins with synthetic fixtures and fuzzing.
Implements item 7 of #746.
Co-authored-by: GPT-6.1 Sol <noreply@openai.com>
Co-authored-by: sim <sim@example.invalid>
Existing URL and code-execution signatures miss cloud metadata access and
language-specific deserializers. Add scoped static evidence and inspect safe
YAML and torch options within each call so safe siblings cannot hide risks.
Validate and preserve file applicability across overrides, scans and rule
listings. Collect PHP scripts and propagate rule-load errors so malformed
filters cannot silently disable global scanning. Document the policy and
limits with paired regressions, fuzzing and an isolated CLI runbook.
Co-authored-by: GPT-6.1 Sol <noreply@openai.com>
Co-authored-by: sim <sim@example.invalid>
Co-authored-by: Willie <egg358358@gmail.com>
Required local references can currently escape a skill bundle or fail silently
when written as images and explicit code paths. Resolve them within the declared
root without reading external targets, retain dangling-link compatibility, and
share the findings and rule controls with doctor. Keep metadata and integrity
fallback reads within the same root so they cannot reopen skipped symlinks.
Co-authored-by: GPT-6.1 Sol <noreply@openai.com>
Co-authored-by: Willie <egg358358@gmail.com>
Long blank spans and repeated filler can move meaningful instructions out
of view during skill review. Add four padding signals under the static
analyzer with Markdown exemptions and original-source line mapping.
Reuse rule overlays so global and project toggles and severity/confidence
overrides also govern this file-level detector. Cover threshold boundaries,
benign examples, optimized scans, reports and CLI rule controls.
Implements item 17 of #746.
Co-authored-by: GPT-6.1 Sol <noreply@openai.com>
Co-authored-by: Willie <egg358358@gmail.com>
* feat(herdr): hide disabled rows and group In sync by source
A source with many disabled skills buries the few rows that need
attention, and a long In sync list gives no sense of where skills
came from.
- Disabled rows are hidden by default; "Show disabled · n" lists them
again and the choice is kept. A disabled hook with pending changes
stays visible because it still needs a sync.
- In sync skills and agents can be grouped by their source repository
(By source) or shown flat (List); a source with one row stays a
plain row, and a filter opens every group.
- Opened plugin and MCP rows show their source, version and targets
instead of an empty detail area.
* refactor(herdr): move the panel's logic out of main.js into testable modules
The bugs fixed in #773, #774 and #775 sat in main.js code that imports
Herdr, so node could not test it: the detached-job polling, the busy
state, and perform's op chain. Only model.js's parsing had tests.
Each concern now lives in a module that takes Herdr's functions as
arguments, so herdr/tests runs it:
- jobs.js runs skillshare: short reads as one exec, longer work
detached and polled, with the sweep of old job folders and one
JOB_MINUTES limit shared with SWEEP.
- channel.js carries requests, notices and one lock per machine
through shared values. The install dialog used to check only a
global busy string and then run without the lock; it now takes
that machine's lock. Holders refresh the lock before each command
and an untouched lock expires after a minute, because a dialog's
task ends without cleanup when it closes.
- operations.js holds what each request runs and the conflict
handling of a pull; perform only takes the lock and shows progress
and the result.
- loader.js reads the Resources data and the Machines cards, and runs
status alongside the snapshots.
The skillshare layout is now published at herdr.dev/layouts, where one
agent prompt installs it without copying files by hand. Offer that path
first in the Herdr guide (all locales) and the panel README, and keep
the manual steps for anyone who wants to merge blocks into their own
layout.