Kit profiles, runner selection from the stage's profile, definition validation #236
Notifications
Due Date
No due date set.
Reference: sam/archie#236
Reference in new issue
Block a user
Stage then profile then builtin; unknown or unused harnesses are validation errors. See docs/prds/external-agent-harness.md.
Notes
A harness is an agent profile naming a Kit composition; no separate harness resource (docs/prds/external-agent-harness.md, Selection).
Also carries the Kit task orchestration moved from egkf.9: register the egress session (SessionOptions with Run, Network, Credentials) and create the sandbox network (egress.Networks.Create); container.StartKit with InstallDone calling Session.EnterRuntime; worker env with NATS_URL and STATE_STORE_URL pointed at the relay alias ports (egress.RelayNATSPort, RelayStateStorePort); mounts for the archie-agent binary, CA (egress CA CertPEM) and worktree at kit.WorkspaceDir; hand kit.Launch.Harness to the worker as Request.Harness; RemoveKitVolumes when the execution ends; relay started with egress.RelayArgs.
Progress 2026-09-26: landed worker side (HarnessSpec.Adapter, claude-code adapter registry, HarnessStages runs every stage of a Kit task on its harness, review stage parks in a Kit task, gate retry without resume/continue refused before invocation) and config side ([containers.profiles.X] kit = digest-pinned workload+mixins, adapter; exclusive with image). Decision (maintainer): the workflow's profile picks the container; mixing Kit and image profiles in one workflow is invalid, so no per-stage profile field.
Remaining: daemon Kit orchestration (fetch+kit.Compose+Assemble, proxy session, sandbox network, StartKit via the pool's lifecycle, relay-port worker env, archie-agent/CA/worktree mounts, taskrun.Request.Harness, RemoveKitVolumes) and archied egress boot wiring (CA dir, proxy listener on the host gateway, relay). Blocker for authenticated runs: no production egress.Resolver exists; run credentials carrying org secrets are not implemented. Also open: rejecting a Kit profile no workflow names (profiles live in config, workflows in the State Store).
2026-09-26 daemon side landed (
70df8d11): kitrun.Launcher (fetch.Assemble + kit.FromMerge, proxy session, sandbox network, Pool.AcquireKit with the pool's slots/uptime/exit watch, archie-agent + CA + worktree binds), daemon.runKitTask (worker env through relay ports, no provider keys; Harness in taskrun.Request; volumes removed unless parked), archied setupKitLauncher (CA under state_dir/egress, proxy on the pool's host gateway, relay started on first Kit launch, disabled with a log line when no host gateway). Harness runner gives the worktree (not .git) to the Kit user. Not yet: end-to-end run against a real Kit (needs egkf.11 for credentials), agent-skills store mount, staging agent-context sources, rejecting unused Kit profiles.2026-09-28: pushed
b8672757(profile kit is one workload or published Kit set ref; mixin layers were silently dropped before),70f9b1b8(agent-skills@1 mounts skills_dir store read-only),525dbb14(agent-context profile beside workspace, workspace now /archie/workspace). Remaining: reject a Kit profile no workflow names; end-to-end run waits on egkf.11.Close reason
Landed:
7aa01c7con main — agent profiles are a live, org-scoped control-plane resource (AgentProfileKind, ApplyMode live, verified in-tree during this sweep's earlier review), a stage needing a different profile runs via workflow.call with its own profile, and dispatch refuses a harness that cannot meet its declared needs.Imported from beads
archie-core-egkf.6· GitHub #1207 · type task · priority P1 · created 2026-09-25 · closed 2026-09-29