Invokta 0.3.0

Added

• Added create-invokta-capability and
  create-invokta-capability-library, with deterministic private ESM starters
  that prove atomic and library composition through engine.invoke.
• Generated engine and capability-library projects now include one AGENTS.md
  instruction source and a relative CLAUDE.md symbolic-link alias.
• Every generated engine, atomic capability, and capability-library project now
  includes a valid develop-invokta-project skill tailored to its architecture
  and test-first workflow.
• Generated engines now include a build-free mcp:uninstall command that
  removes the same managed engine identity from every configured MCP client
  through one confirmed, ownership-safe operation.
• Added the pure @invokta/deploy/scaffold planner so development-time
  generators can reuse the fail-closed MCP HTTP templates without copying them
  or invoking another CLI.

Changed

• create-invokta-engine now guides terminal users through a project directory,
  one of the complete, mcp-stdio, mcp-http, or cli profiles, and a final
  confirmation. Terminal automation must pass --yes.

• The default complete starter now includes MCP HTTP and the matching
  @invokta/deploy development dependency. Focused profiles include and
  document only their selected adapter.

• Non-terminal positional creation remains compatible. Automation that requires
  the former syntax and new deterministic default maps as follows:

  create-invokta-engine my-engine --no-install
  create-invokta-engine my-engine --profile complete --no-install --yes