/system groups crew:<name> processes as the crew kind #2814

/system now treats crew:<name> as its own kind, listed right after forge. I couldn't run the type check: bun x tsc --noEmit and bun install both fail here with "unable to write files to tempdir". bun test test/system-btop.test.ts test/cgroup.test.ts passes (19 pass, 3 skipped for the cgroup limits of this sandbox, 0 fail). The branch is pushed.

• Kind: kindOf in src/system/view.ts maps crew:<name> to a new crew kind.
• Hiding: forAgent handles crew groups the way it handles checks and apps. When visible says no, the label becomes crew:private-N and the processes and test files are dropped. A crew label is visible only if the visible callback says so, and the live callback publicLabel has no crew case and returns false for crew: labels. So agent views hide every crew group, not just other agents'. Showing an agent its own crew group would need forAgent to know who is asking. I didn't add that.
• Kind order: src/web/pages/system.ts and src/web/system-live.ts now order kinds forge, crew, check, app, host, so the client-side sort matches.
• Test: test/system-btop.test.ts has a synthetic table with forge, check:RUN1, app:other/production and crew:atlas rows. It gives four groups in page order (forge, crew, check, app). The issue's "in that order" reads two ways, and I followed the instruction to put crew after forge. The test also checks that forAgent hides atlas and that a visible that accepts it shows it.

Closes #2811

/system now treats crew:<name> as its own kind, listed right after forge. I couldn't run the type check: bun x tsc --noEmit and bun install both fail here with "unable to write files to tempdir". bun test test/system-btop.test.ts test/cgroup.test.ts passes (19 pass, 3 skipped for the cgroup limits of this sandbox, 0 fail). The branch is pushed.

• Kind: kindOf in src/system/view.ts maps crew:<name> to a new crew kind.
• Hiding: forAgent handles crew groups the way it handles checks and apps. When visible says no, the label becomes crew:private-N and the processes and test files are dropped. A crew label is visible only if the visible callback says so, and the live callback publicLabel has no crew case and returns false for crew: labels. So agent views hide every crew group, not just other agents'. Showing an agent its own crew group would need forAgent to know who is asking. I didn't add that.
• Kind order: src/web/pages/system.ts and src/web/system-live.ts now order kinds forge, crew, check, app, host, so the client-side sort matches.
• Test: test/system-btop.test.ts has a synthetic table with forge, check:RUN1, app:other/production and crew:atlas rows. It gives four groups in page order (forge, crew, check, app). The issue's "in that order" reads two ways, and I followed the instruction to put crew after forge. The test also checks that forAgent hides atlas and that a visible that accepts it shows it.

I merged main into the branch and pushed it. The only conflict was the header comment in src/system/view.ts.

main had already added crew:<name> to that comment, in the same sentence I had edited. I kept main's wording, so view.ts now matches main exactly.

My other changes are unchanged:

• Page order: the /system page and src/web/system-live.ts list kinds as forge, crew, check, app, host.
• Test: the crew grouping and hiding test is still in test/system-btop.test.ts.

bun test test/system-btop.test.ts test/cgroup.test.ts passes after the merge (19 pass, 3 skipped for the sandbox's cgroup limits, 0 fail). I did not run the type check, because bun x tsc still fails in this sandbox with a read-only tempdir error.