First-run onboarding

This is the first thing a new user runs after installing the plugin. Init asks for the bucket name in chat (the only piece of customer data the plugin needs that isn't already on disk), walks the user through aws configure for their AWS credentials, verifies, and persists the runtime config to bucket.json.

The plugin gives the user direct access to their Parse.ly Data Pipeline (DPL) so they can ask questions of their raw event firehose in chat. More data sources land in future versions; v1 is DPL only.

Output discipline

This is a customer-facing first-run flow. Keep it quiet and on-script.

• Verbatim where shown. Blockquoted text (> like this) prescribes the exact words you say to the user. Output those words and nothing else for that step.
• Silent steps stay silent. Steps tagged (silent on success) produce no chat output when they succeed. Run the shell command, move on. Don't summarize results, don't announce upcoming actions, don't recap state.
• No task lists. Don't surface this flow as a todo/task list.
• Off-script questions get short answers, then resume. If the customer interrupts with a question, answer briefly and pick up at the next step.
• Bucket name lives in bucket.json. If it's already there from a previous run, reuse it silently. Only ask the customer for it if it isn't.
• AWS credentials live in ~/.aws/credentials. They're set up by the user via aws configure --profile agentic-analytics in step 5. Subsequent aws invocations pick them up via --profile agentic-analytics. Never ask for them in chat.

Tone