Extract commands into a dedicated package

[waynemwashuma]

Objective

Introduces a dedicated @wimaengine/commands package for high-level engine commands and moves command execution out of @wimaengine/core.

Solution

The command architecture is split into three responsibilities:

• @wimaengine/command provides the command infrastructure, including CommandQueue and command execution.
• @wimaengine/commands provides high-level commands and APIs such as EntityCommands and ResourceCommands.
• @wimaengine/core retains core engine functionality without depending on the command package.

Command execution is now registered by CommandsPlugin during both Startup and Update, in the CoreSystems.End group.

Why This Approach

This solution was chosen because:

• It separates the low-level command infrastructure from the high-level engine commands that depend on it.
• It removes high-level command functionality from @wimaengine/core, reducing the responsibility of the core package.
• Command execution now belongs to the command package that provides the command infrastructure.
• Consumers that need high-level commands can depend directly on @wimaengine/commands instead of importing them from @wimaengine/core.

Showcase

Before

High-level commands and command execution were part of @wimaengine/core:

import { EntityCommands } from '@wimaengine/core'

Command execution was also registered by CorePlugin.

After

High-level commands are provided by the dedicated commands package:

import { EntityCommands } from '@wimaengine/commands'

Command execution is provided by @wimaengine/command and registered through CommandsPlugin

Migration Guide

No migration is required.

Checklist

• I have updated the documentation accordingly.
• I have added tests to cover my changes.