01Run it
Straight from the command's own help.
p202 forecast-event update <id from p202 forecast-event list> --event-name <new value> --json02What you get
Pick the shape you need. People get a table. Add
--json, --csv or --ndjson for scripts, or -q for ids only. An AI agent gets compact JSON without asking. All output formats03Build your command
Pick values and the command line writes itself, quoted and ready to paste.
p202 forecast-event updateSet flags below; the command updates as you type.
04Flags
10 flags, plus the global flags every command takes.
| Flag | What it does |
|---|---|
| --end-datestring | End date for multi-day events (YYYY-MM-DD) ("" clears it) |
| --event-datestring | Event date (YYYY-MM-DD) |
| --event-namestring | Event name (e.g. 'Black Friday', 'Server Outage') |
| --expected-impact-pctstring | Expected impact percentage (e.g. +200 for 3x boost, -50 for half) |
| --impact-typestring | Impact type: boost, suppress, neutralboostsuppressneutral |
| --lag-daysstring | Days after event that impact decays |
| --lead-daysstring | Days before event that impact ramps up |
| --notesstring | Freeform notes ("" clears it) |
| --recurrencestring | Recurrence: none, monthly, yearly, customnonemonthlyyearlycustom |
| --tagsstring | Comma-separated tags (e.g. 'us-holidays,retail') ("" clears it) |
05For agents
Running this from an agent
- Read the same facts as JSON:
p202 commands forecast-event update --json. - With
AI_AGENT,CLAUDECODEor another agent variable set, output is compact JSON and errors arrive on stderr as a JSON envelope with ahint. - Exit codes: 0 ok, 1 bad input, 2 auth, 3 network, 4 server error, 5 partial failure.
- This command writes. Add
--stagedto record it as a proposal a person applies withp202 change apply.
{
"path": "p202 forecast-event update",
"use": "update <id>",
"short": "Update a forecast-event",
"runnable": true,
"example": "p202 forecast-event update <id from p202 forecast-event list> --event-name <new value> --json\n (only the flags given are sent; the rest of the forecast-event is unchanged)",
"flags": [
{
"name": "end-date",
"type": "string",
"default": "",
"usage": "End date for multi-day events (YYYY-MM-DD) (\"\" clears it)",
"required": false
},
{
"name": "event-date",
"type": "string",
"default": "",
"usage": "Event date (YYYY-MM-DD)",
"required": false
},
{
"name": "event-name",
"type": "string",
"default": "",
"usage": "Event name (e.g. 'Black Friday', 'Server Outage')",
"required": false
},
{
"name": "expected-impact-pct",
"type": "string",
"default": "",
"usage": "Expected impact percentage (e.g. +200 for 3x boost, -50 for half)",
"required": false
},
{
"name": "impact-type",
"type": "string",
"default": "",
"usage": "Impact type: boost, suppress, neutral",
"allowed_values": [
"boost",
"suppress",
"neutral"
],
"required": false
},
{
"name": "lag-days",
"type": "string",
"default": "",
"usage": "Days after event that impact decays",
"required": false
},
{
"name": "lead-days",
"type": "string",
"default": "",
"usage": "Days before event that impact ramps up",
"required": false
},
{
"name": "notes",
"type": "string",
"default": "",
"usage": "Freeform notes (\"\" clears it)",
"required": false
},
{
"name": "recurrence",
"type": "string",
"default": "",
"usage": "Recurrence: none, monthly, yearly, custom",
"allowed_values": [
"none",
"monthly",
"yearly",
"custom"
],
"required": false
},
{
"name": "tags",
"type": "string",
"default": "",
"usage": "Comma-separated tags (e.g. 'us-holidays,retail') (\"\" clears it)",
"required": false
}
]
}