event-logginglisted

# Event logging Event logging is optional and disabled by default. It writes local workflow-gate events to `.agenticloop/logs/<TASK-ID>.jsonl` through the Node CLI. `agenticloop/AGENTIC_LOOP.md` owns why event logging exists, the event taxonomy, and which lifecycle gates emit which events. This skill owns the operational procedure: resolving the command, honoring the disabled and non-blocking rules, and keeping entries concise. ## When event logging is off Read `.agenticloop/project.md` before writing any event. Agents must not attempt CLI event logging unless it says `event_logging: enabled`. When event logging is disabled, do nothing: writing events is a no-op, and skipping them is not a process gap. ## Resolving the command When `event_logging: enabled`, resolve the event logging command once per host session before the first event write: 1. If `event_logging_command` is non-empty, use that command. 2. If `event_logging_command` is blank or omitted, run `npx agenticloop --help` once. If it succeeds, use `npx agenticloop`. 3. If no working event logging command is available, do not repeatedly retry and do not block the workflow. Record a truthful process gap in the task record, review, or closeout marker note, then continue. After resolution, event writes use: ```text <resolved-command> event-logging <event_type> --task <TASK-ID> --role <role> --summary "<short fact>" ``` `agenticloop event` remains a compatibility alias, but new instructions should use `e