fix(settings): keep machine-only capabilities out of Goal editor

[huangruiteng]

Problem and result

Opening Goal capabilities with the shared capability catalog showed machine-only settings such as Steward executor and Manager runtime as read-only Goal rows. The Goal editor now selects and navigates only capabilities declaring Goal scope. Goal-scoped read-only entries remain visible; machine-only settings remain in the Steward or machine settings that own them. No API or persisted configuration contract changes.

The browser fixture now supplies the same mixed catalog shape as the real Goal inspection endpoint, and the design guide records the ownership rule.

Visual review

• Before: the Goal catalog included a machine-badged Steward executor row whose detail only said it could be configured at machine scope.
• After: the Goal catalog contains Goal-scoped rows only; Steward executor remains available in the first-level Steward settings. The packaged browser view was inspected at desktop size.

Validation

• npm run build (TypeScript, dashboard, packaged Chat bundle): passed.
• LOOPX_PERSONAL_WORKSPACE_SCENARIO=typed-actions node examples/personal-workspace-browser-smoke.mjs: passed.
• The same scenario with LOOPX_PERSONAL_WORKSPACE_PACKAGED=1: passed after rebasing onto current main.
• loopx check on all four changed public paths: 0 errors; two unrelated existing Goal-state projection warnings.
• git diff --check origin/main...HEAD: passed.
• Exact-scope change-quality receipt: cqr_9c2acc4517c9ac583ba4, verified valid.

Future-facing pass: reused the existing available_scopes descriptor and catalog components; no new scope state or backend duplicate was needed.