Files
skillshare/wiki
Willie 84bbd40785 fix(windows): run in a hidden console when started without one (#341)
* chore(scripts): install UI deps from the store in utm.sh build

pnpm 12 refuses a symlinked node_modules ("workspace hoist directory is
not a real directory"), so the pinned UTM build stopped at the UI step.
An offline, frozen install from the shared store keeps the build pinned
to the archived lockfile and takes a few seconds.

* fix(windows): run in a hidden console when started without one

Started without a console (a scheduled task wrapper, pythonw), every
console program skillshare spawns gets its own console, so a single
`pull` flashed about ten Windows Terminal windows. skillshare now reruns
itself once with CREATE_NO_WINDOW in that case; all children inherit the
windowless console. Doing it at the entry point covers the 130+ exec
sites instead of patching each one. Runs with a console never relaunch,
and stdio and the exit code pass through.

The UTM runbook and probe script record descendants and new windows for
each console state, so the behavior can be rechecked on a real guest.

Closes #339

* chore(scripts): ask pnpm for the UI store and derive the guest profile

utm.sh build hard-coded /workspace/.pnpm-store, which only matches
pnpm's per-filesystem default by coincidence; it now asks pnpm which
store the workspace UI uses. The console e2e script checked a fixed
user's AppData, so another GUEST_USER could pass while its own profile
changed; it now records the real APPDATA before isolating.

* docs(tests): make the console runbook build step runnable as written

The push step read $OUT, which only exists inside utm.sh, so a fresh
shell pushed /ss.exe; the example also hard-coded arm64 next to a note
about x64 guests. Export utm.sh's default OUT and take the arch from the
probe instead.

* fix(windows): stop the relaunched run when its launcher is killed

A caller that terminates the PID it started (a wrapper timing out) only
killed the waiting wrapper; the relaunched skillshare kept running and
could keep mutating state. The relaunched process now sits in a
kill-on-close job. Its own children break away silently, so git, the
background UI server, browsers and editors behave as they did without
the relaunch. A wait failure after a successful start now exits 1
instead of running the command a second time in the wrapper.

The console e2e script gains a cancel check and a `ui start` survival
check; on the UTM guest the baseline left the inner process serving
after the kill, the fix stops it, and the background server still
outlives its launcher.
2026-10-03 00:14:28 +08:00
..
2026-09-25 02:32:37 +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, using the devcontainer/ssenv, or running E2E runbooks testing.md, CONTRIBUTING.md
frontend Changing React, CSS, layout, or visual behavior in the dashboard or website frontend.md, website/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
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
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