Introduces a code-level concept of "Organization", that packages can belong to (applicable only to Action Packages inside Agent Packages for now)
Adds "Agent Packages" section to the extension sidebar, that lists Agent Packages present in the workspace (based on directories with agent-spec.yaml file) and organisations present in each Agent Package (in actions directory)
Adds "Create Agent Package" command (available from Command Palette and extension sidebar)
Adds "Refresh" action to the "Agent Packages" sidebar section
makes "Task/Action Packages" section dependant on the organisation selection in "Agent Packages" sidebar section (if no organisation is selected, "Task/Action Packages" will look for the packages at root level)
Decouples listing of Agent and Task/Action packages in the commands layer (adds new localListAgentPackages .internal command that lists Agent Packages present in the workspace)
separates views selection handling into a separate file
renames "Package Content" and "Package Resources" sidebar sections to "Task/Action Package Content" and "Task/Action Package Resources" respectively
adds new WorkspaceManager class on the Python backend side, to centralise workspace-related operation (like directories traversal and packages listings) and relief some responsibilities from the main command handler
agent-spec.yamlfile) and organisations present in each Agent Package (inactionsdirectory)localListAgentPackages .internalcommand that lists Agent Packages present in the workspace)WorkspaceManagerclass on the Python backend side, to centralise workspace-related operation (like directories traversal and packages listings) and relief some responsibilities from the main command handler