You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
-Update Workspace loader/runtime to consume the corrected strict Workspace manifest shape where tool payloads live under `tools`.
10
-
-Build available tool list from `Object.keys(manifest.tools)` filtered/validated against tool registry.
11
-
-Ensure valid tools are not silently dropped.
12
-
- Map singular `tools.palette` to the Palette Browser UI if that is the schema decision, but do not let it become the only visible tool.
13
-
- Stop relying on old top-level `palettes`, `activeWorkspaceTools`, `games[].tools`, top-level `config`, top-level `payload`, or sample tool-payload wrappers for sample 1902.
14
-
-Validate sample 1902 opens Workspace with all valid tools, not only Palette.
9
+
-Fix Workspace Manager/tool presence detection so tools are marked present from `manifest.tools[toolId]`.
10
+
-Use strict manifest.tools keys as the source for presence.
11
+
-Validate keys against tool registry and tool schemas.
12
+
- Map singular `tools.palette` to Palette Browser UI/presence without suppressing other tools.
13
+
- Stop using old presence sources for sample 1902: top-level palettes, games[].tools, activeWorkspaceTools, config, top-level payload, sample tool-payload wrappers.
14
+
-Add evidence/report listing raw loaded tool keys, normalized keys, valid present keys, invalid keys, and visible Workspace Manager tools.
15
15
- Do not loosen schemas.
16
-
- Do not add fallback/default/hidden data.
17
16
- Do not modify other samples.
17
+
- Do not add fallback/default/hidden data.
18
18
- Do not modify start_of_day folders.
19
-
- Add validation report at docs/dev/reports/PR_11_20_WORKSPACE_LOADER_SCHEMA_V2_TOOLS_PAYLOAD_SUPPORT_report.md.
20
-
- Return ZIP artifact at tmp/PR_11_20_WORKSPACE_LOADER_SCHEMA_V2_TOOLS_PAYLOAD_SUPPORT_delta.zip.
19
+
- Add validation report at docs/dev/reports/PR_11_21_WORKSPACE_MANAGER_TOOL_PRESENT_DETECTION_FIX_report.md.
20
+
- Return ZIP artifact at tmp/PR_11_21_WORKSPACE_MANAGER_TOOL_PRESENT_DETECTION_FIX_delta.zip.
- raw `manifest.tools` key -> mapped tool id (palette alias)
14
+
- registry match
15
+
-`tool` field id match
16
+
- It did not enforce explicit tool-schema validation for each `manifest.tools` entry.
17
+
- When a workspace filter was present, game-level `toolsUsed` filtering could still influence visible tool list.
18
+
19
+
## New Presence Check
20
+
- Presence source is strict `manifest.tools` keys from the loaded workspace manifest.
21
+
- Classification now records and validates, per key:
22
+
- raw key
23
+
- normalized key
24
+
- palette alias mapping (`tools.palette` -> `palette-browser`)
25
+
- registry match
26
+
- workspace-schema allowed key
27
+
- tool-schema validity
28
+
- payload `tool` id match
29
+
- Workspace schema contract is loaded from:
30
+
-`tools/schemas/workspace.manifest.schema.json`
31
+
- referenced tool schemas under `tools/schemas/tools/*.schema.json`
32
+
- If schema contract cannot be loaded, entries are rejected as not schema-validated.
33
+
- Required workspace tool keys from schema (including `palette`) are enforced in diagnostics.
34
+
- Visible Workspace Manager tools are now derived from accepted `manifest.tools` presence and no longer intersected with game `toolsUsed` when workspace manifest keys are available.
- No old presence sources were used for sample 1902 presence classification (`palettes`, `games[].tools`, `activeWorkspaceTools`, top-level `config`, top-level `payload`, wrapper payloads).
0 commit comments