starintel-actor-createlisted

# Create a StarIntel actor ## Goal Create an actor in the runtime that actually owns the requested execution boundary. Requires current `lost-rob0t/star-lang` and StarIntel server repositories plus `starintel-spec-version` when the actor consumes or emits StarIntel documents/manifests. ## Input The actor's purpose, inputs, outputs, effects, deployment target, state/lifecycle requirements, and failure semantics. ## Output An executable actor plus contract tests, registration/startup wiring, and a matching manifest or canonical record when required. ## Choose the runtime 1. Use final `starlang-runtime` for deterministic local Common Lisp actors. 2. Use a `starintel-server` Common Lisp plugin actor when it must run inside the production Sento actor system or consume the current RabbitMQ target flow. 3. Use `create-external-actor` only to register an external boundary; current final Star-Lang does not yet dispatch it. 4. An Auto-Dig `actor-manifest` document describes an actor. It does not instantiate or deploy one. Read [references/runtime-boundaries.md](references/runtime-boundaries.md) for the current implementation split. ## Workflow 1. Inspect the current runtime's repository instructions, exported packages, tests, and one maintained actor with the same deployment model. 2. Before defining any StarIntel document, message field derived from the document contract, or `actor-manifest`, use `starintel-spec-version` to resolve the consumer lock's active `release_versi