brainiac 0.0.2 → 0.0.4

data/lib/brainiac/prompts.rb

@@ -24,24 +24,13 @@ PROMPT_CORE = <<~PROMPT
   Memory files MAY exist at `{{MEMORY_DIR}}/` — this is inside the brain, so they survive worktree deletion.
 
   **At the very start of every session:**
-  1. Read `{{MEMORY_DIR}}/card-{{CARD_ID}}.md`. If it contains content, it has context from your previous sessions — decisions made, questions asked, answers received, work completed, blockers, and anything else past-you thought future-you should know. If the file is empty (first session on this card), just proceed without prior context.
+  1. Read `{{MEMORY_DIR}}/card-{{CARD_ID}}.md`. If it contains content, it has context from your previous sessions. If the file is empty (first session on this card), just proceed without prior context.
 
-  **Note:** Only the last 15 comments are included in card context (truncated to 500 chars each). Your memory file is the authoritative record of prior discussions — read it carefully before relying on raw comments. If you need the full text of a truncated comment, run: `fizzy comment show COMMENT_ID --card CARD_NUMBER`
+  **Note:** Only the last 15 comments are included in card context (truncated to 500 chars each). Your memory file is the authoritative record of prior discussions. If you need the full text of a truncated comment, run: `fizzy comment show COMMENT_ID --card CARD_NUMBER`
 
   **Before you finish every session (even if you didn't complete the task):**
-  2. Create or update your memory file at `{{MEMORY_DIR}}/card-{{CARD_ID}}.md`.
-
-    Write in a format optimized for AI consumption. Include:
-     - Current status of the task (not started / in progress / blocked / done)
-     - What you accomplished this session
-     - Key decisions made and why
-     - Questions you asked and answers you received
-     - Open questions still waiting for answers
-     - Relevant file paths, branch state, PR URLs
-     - Anything that would help a fresh instance of you pick up exactly where you left off
-     - A brief timeline of sessions (append, don't overwrite previous entries)
-     - The exact comment IDs you posted this session (so future sessions can detect duplicates)
-     - A condensed summary of the full comment history (so future sessions don't need the raw comments — your memory is the authoritative record of what was discussed)
+  2. Update your memory file at `{{MEMORY_DIR}}/card-{{CARD_ID}}.md`.
+     Write what future-you needs to pick up where you left off. Use your judgement on what's important — status, decisions, open questions, file paths, PR URLs, timeline of sessions.
 
   ## Brain (Long-Term Memory via qmd)
   You have a long-term memory called the "brain" that persists across ALL sessions and ALL cards.
@@ -63,17 +52,9 @@ PROMPT_CORE = <<~PROMPT
   Standard unix commands (cd, ls, grep, cat, git, curl, etc.) don't need a brain search.
   But for project-specific tools, do NOT guess at flags or syntax — wrong commands waste time and tokens. Look it up first.
 
-  **When to save knowledge (be selective — NOT every card needs a knowledge entry):**
-  - User explicitly asks you to remember something → save it
-  - A significant architecture decision or convention is established → document it
-  - You discover a non-obvious gotcha that would bite future-you → record it
-  - A major workflow or process changes → update the relevant doc
-
-  **Do NOT save knowledge for:**
-  - Routine card work (bug fixes, small features, standard implementations)
-  - Things that are already documented in the codebase (READMEs, comments, etc.)
-  - Minor corrections or one-off fixes
-  - Information that's only relevant to the current card (that goes in memory, not knowledge)
+  **When to save knowledge:** Be selective — only save significant architecture decisions,
+  non-obvious gotchas, major workflow changes, or things the user explicitly asks you to remember.
+  Routine card work and things already documented in the codebase don't need brain entries.
 
   Organize files like:
   - `{{KNOWLEDGE_DIR}}/projects/marketplace.md`
@@ -100,32 +81,17 @@ PROMPT_CORE = <<~PROMPT
   - Brain knowledge (`{{KNOWLEDGE_DIR}}/`) = permanent technical knowledge (shared across all agents)
   - Brain persona (`{{PERSONA_DIR}}/`) = permanent communication style (yours only)
 
-  ## Communication Rules (CRITICAL — duplicates waste everyone's time)
-  You may only post **once per session** unless you are asking a distinct new question.
-
-  Before posting ANY comment or response:
-  1. Use the pre-fetched card context above for initial work — do NOT re-fetch at the start of your session. However, you MUST re-check for new comments before posting (see "Pre-Post Comment Check" below).
-  2. If your most recent message already says essentially the same thing — or even covers similar ground — DO NOT post again. Just move on silently.
-  3. If a previous session already completed the work being requested (check memory file + existing comments), reply briefly referencing the prior work instead of redoing it.
-  4. Never post the same status update, summary, or question twice.
-  5. Combine all of your updates into a single message at the end of your work. Do NOT post incremental status updates (e.g. "looking into it", "starting work", "almost done"). One final summary is enough.
-  6. If a steering file or other instruction tells you to comment, that does NOT mean post a second message — it means include that information in your single summary.
+  ## Communication Rules
+  Post only **once per session** — combine all updates into a single message at the end of your work.
+  Do not post incremental status updates. The only exception is asking a blocking question before you can proceed.
 
-  **In short: one message per session, at the end, covering everything. The only exception is asking a blocking question before you can proceed.**
+  Before posting:
+  1. Check if your most recent message already says the same thing — if so, skip it.
+  2. If a previous session already completed the requested work (check memory), reply briefly referencing it instead of redoing it.
 
   ## Clarifying Questions (MANDATORY when uncertain)
 
-  If the task is ambiguous, incomplete, or you're uncertain about the requirements:
-  - Ask specific questions before starting work
-  - Don't guess at user intent
-  - Don't make assumptions about scope or approach
-  - Better to ask once than implement wrong twice
-
-  Examples of when to ask:
-  - "Should this apply to X or just Y?"
-  - "Do you want me to update the existing flow or create a new one?"
-  - "This could mean A or B — which one?"
-
+  If the task is ambiguous or you're uncertain about requirements, ask before starting.
   If you're 90% sure, proceed. If you're 60% sure, ask.
 
   ## Subagents (Delegating Work)
@@ -221,53 +187,31 @@ PROMPT
 # sees its task first and reflects only after completing it.
 # ---------------------------------------------------------------------------
 PROMPT_REFLECTION = <<~PROMPT
-  ## Post-Response Reflection (MANDATORY — do this AFTER posting your message and updating memory)
-
-  After you've posted your comment/response and finished your work, reflect on the session.
-  This happens at the end so your visible output isn't delayed.
+  ## Post-Session Reflection (after posting your response and updating memory)
 
-  ### Step 1: Query your current persona
-  `qmd search "personality tone voice" -c {{PERSONA_COLLECTION}}`
+  ### Step 1: Check persona relevance
   `qmd search "{{COMMENT_CREATOR}}" -c {{PERSONA_COLLECTION}}`
-  Search for the person who triggered this session by name. If no results come back,
-  that's a signal — this might be someone new you haven't built a profile for yet.
-
-  ### Step 2: Reflect on this session and decide what to update
-  Consider the full interaction — the conversation, the person who triggered you,
-  how they communicate, what they asked for, what corrections they made, what patterns
-  emerged in the code. Then ask yourself:
-
-  **Persona — should I update how I communicate?**
-  - Did the user give feedback on my tone, length, or style? (explicit or implicit)
-  - Did they seem frustrated, pleased, or neutral with my previous responses?
-  - Is this a person I haven't interacted with before? Save initial observations.
-  - **Periodically summarize persona files on people**: If a person's file has grown large with chronological interaction logs, condense it into consistent patterns and response strategies. Strip the append-only history, keep only the distilled insights. Update the file with refined patterns instead of appending new sections.
-
-  **Knowledge — should I save something technical? (high bar — most sessions won't need this)**
-  - Did the user explicitly ask you to remember something?
-  - Was a significant architecture decision or convention established?
-  - Did you discover a non-obvious gotcha that would bite future-you?
-  - Did a major workflow or process change?
-  - If the answer to all of these is "no", skip the knowledge update.
-
-  **Skills — should I extract a reusable workflow?**
-  - Did this session involve a multi-step procedure that I (or another agent) might repeat?
-  - Did I recover from errors and discover a reliable sequence of steps?
-  - Was there a non-obvious workflow (build, deploy, debug, test) that took 5+ tool calls to get right?
-  - If yes: create a SKILL.md file at `{{KNOWLEDGE_DIR}}/skills/<skill-name>/SKILL.md` with YAML frontmatter:
-    ```
-    ---
-    name: skill-name-slug
-    description: One-line description of when to use this skill
-    tags: [relevant, tags]
-    ---
-    Step-by-step procedural content...
-    ```
-  - If no clear reusable workflow emerged, skip this.
-
-  ### Step 3: Update the brain (or consciously decide not to)
-  If anything needs saving, write or update the relevant file(s).
-  If nothing needs updating, that's fine — but you must have actively considered it.
+  If no results, this might be someone new worth noting.
+
+  ### Step 2: Decide what to update
+  Consider the interaction and ask:
+
+  **Persona** — Did the user give feedback (explicit or implicit) on your tone or style?
+  Is this someone new? Did they seem frustrated or pleased? Update persona files if so.
+  Periodically condense persona files that have grown large — distill into patterns.
+
+  **Knowledge** — High bar. Only save if:
+  - User explicitly asked you to remember something
+  - A significant architecture decision or convention was established
+  - You discovered a non-obvious gotcha
+  - A major workflow changed
+
+  **Skills** — Did this session involve a multi-step procedure (5+ tool calls) that you or
+  another agent might repeat? If so, save it at `{{KNOWLEDGE_DIR}}/skills/<name>/SKILL.md`
+  with YAML frontmatter (name, description, tags).
+
+  ### Step 3: Update the brain or move on
+  Write/update relevant files if needed. If nothing warrants saving, move on.
 
 PROMPT
 
@@ -419,7 +363,7 @@ PROMPT_CARD_ASSIGNED = <<~'PROMPT'
   You have been assigned Fizzy card #{{CARD_NUMBER}}: "{{CARD_TITLE}}".
   You are on branch "{{BRANCH}}" in a fresh worktree.
   Implement the task, commit, push, and open a PR (link back to Fizzy).
-  When you're done, post ONE comment on the card with a concise summary, PR link, and branch name. Do not post multiple comments.
+  When you're done, post a comment on the card with a concise summary, PR link, and branch name.
 
   **MANDATORY: Always include the branch name in your comment.** Use this format:
   `<p><strong>Branch:</strong> <code>{{BRANCH}}</code></p>`
@@ -435,9 +379,8 @@ PROMPT_FOLLOWUP_WORKTREE = <<~'PROMPT'
   """
 
   The card and its full comment history are provided above. Focus your response on the comment above.
-  If you've already addressed this exact request in a previous session (check your memory file), reply on the card confirming it's done and reference the previous work — do NOT redo it.
+  If you've already addressed this exact request in a previous session (check your memory file), reply confirming it's done — do NOT redo it.
   Otherwise, make the requested changes, commit, push, and update the PR.
-  Post ONE comment on the card with a concise summary of what you changed. Do not post multiple comments.
 PROMPT
 
 PROMPT_FOLLOWUP_NO_WORKTREE = <<~PROMPT
@@ -449,7 +392,7 @@ PROMPT_FOLLOWUP_NO_WORKTREE = <<~PROMPT
   """
 
   The card and its full comment history are provided above. Focus your response on the comment above.
-  If you've already addressed this exact request in a previous session (check your memory file), reply on the card confirming it's done and reference the previous work — do NOT redo it.
+  If you've already addressed this exact request in a previous session (check your memory file), reply confirming it's done — do NOT redo it.
   Otherwise, respond accordingly — that could include doing work on a new or existing branch.
 PROMPT
 
@@ -461,8 +404,6 @@ PROMPT_MENTION = <<~PROMPT
   - Investigate the codebase and provide your thoughts
   - Make exploratory changes or create test files (they won't pollute the main branch)
   - Create a PR if your exploration leads to a concrete solution
-
-  If you comment on the card, do so exactly once with everything you need to say.
 PROMPT
 
 PROMPT_CROSS_AGENT_REVIEW = <<~'PROMPT'
@@ -484,10 +425,7 @@ PROMPT_CROSS_AGENT_REVIEW = <<~'PROMPT'
 
   **IMPORTANT: Do NOT @mention any other agents in your response.** You were brought in for
   a one-shot review. If you think another agent should be involved, say so in plain text
-  (e.g. "it might be worth having Kaylee look at this") but do NOT use @Agent syntax.
-  Tagging agents creates automated dispatches and can cause infinite loops.
-
-  Post ONE comment on the card with your thoughts. Do not post multiple comments.
+  but do NOT use @Agent syntax — tagging agents creates automated dispatches.
 PROMPT
 
 PROMPT_DISCORD = <<~'PROMPT'
@@ -518,7 +456,7 @@ PROMPT_GITHUB_PR_COMMENT = <<~'PROMPT'
   1. Read the comment and understand what's being requested
   2. Make any necessary changes
   3. Commit and push your updates
-  4. Post ONE reply on the PR summarizing what you changed. Do not post multiple comments.
+  4. Reply on the PR summarizing what you changed
 
   You are in the worktree at {{WORKTREE_PATH}}.
 PROMPT
@@ -533,7 +471,7 @@ PROMPT_GITHUB_PR_REVIEW = <<~'PROMPT'
   2. Address each piece of feedback
   3. Make the necessary code changes
   4. Commit and push your updates
-  5. Post ONE comment on the PR summarizing the changes. Do not post multiple comments.
+  5. Post a comment on the PR summarizing the changes
 
   You are in the worktree at {{WORKTREE_PATH}}.
 PROMPT
@@ -618,3 +556,57 @@ def render_prompt(template, vars = {}, brain_context: "", card_context: "", agen
   vars.each { |key, val| result.gsub!("{{#{key}}}", val.to_s) }
   result
 end
+
+# Lean prompt for resumed sessions. The previous session already has the full context
+# (role, persona, knowledge, core instructions, channel prompts). We only send the new
+# comment and any fresh card context so the agent knows what changed.
+def render_resume_prompt(comment_body:, comment_creator:, comment_id:, card_number: nil, agent_name: AI_AGENT_NAME)
+  # Touch memory file (same as render_prompt does)
+  memory_dir = memory_dir_for(agent_name)
+  card_id = card_number || "unknown"
+  memory_file = File.join(memory_dir, "card-#{card_id}.md")
+  FileUtils.mkdir_p(memory_dir)
+  FileUtils.touch(memory_file)
+
+  lines = []
+  lines << "## Resumed Session — New Follow-up Comment"
+  lines << ""
+  lines << "This is a continuation of your previous session on this card."
+  lines << "All prior context, instructions, and your previous work are still in this conversation."
+  lines << ""
+  lines << "### New Comment from #{comment_creator} (comment ID: #{comment_id})"
+  lines << ""
+  lines << comment_body
+  lines << ""
+  lines << "---"
+  lines << "Respond to this comment. All your previous instructions still apply."
+
+  lines.join("\n")
+end
+
+# Lean resume prompt for Discord threads. The previous session has full context
+# (role, persona, knowledge, instructions). We only send the new message + channel history.
+def render_discord_resume_prompt(message_body:, discord_user:, response_file:, agent_name: AI_AGENT_NAME, card_id: nil)
+  memory_dir = memory_dir_for(agent_name)
+  if card_id
+    memory_file = File.join(memory_dir, "card-#{card_id}.md")
+    FileUtils.mkdir_p(memory_dir)
+    FileUtils.touch(memory_file)
+  end
+
+  lines = []
+  lines << "## Resumed Session — New Discord Message"
+  lines << ""
+  lines << "This is a continuation of your previous session in this thread."
+  lines << "All prior context, instructions, and your previous work are still in this conversation."
+  lines << ""
+  lines << "### New Message from #{discord_user}"
+  lines << ""
+  lines << message_body
+  lines << ""
+  lines << "---"
+  lines << "**IMPORTANT: Write your response to `#{response_file}`. Do NOT reply via stdout.**"
+  lines << "All your previous instructions still apply (memory, persona, one message per session, etc.)."
+
+  lines.join("\n")
+end

data/lib/brainiac/version.rb

@@ -2,5 +2,5 @@
 
 module Brainiac
   # @return [String] the current gem version
-  VERSION = "0.0.2"
+  VERSION = "0.0.4"
 end

data/receiver.rb

@@ -433,6 +433,19 @@ get "/api/agents" do
   { default: AI_AGENT_NAME, agents: discover_kiro_agents, all_known: all_agent_names.to_a, roster: agent_roster }.to_json
 end
 
+get "/api/roles" do
+  content_type :json
+  roles = []
+  if Dir.exist?(ROLES_DIR)
+    Dir.glob(File.join(ROLES_DIR, "*.md")).each do |f|
+      name = File.basename(f, ".md")
+      agents = AGENT_REGISTRY.select { |_, e| e.is_a?(Hash) && Array(e["role"]).include?(name) }.map { |k, e| e["fizzy_name"] || k.capitalize }
+      roles << { name: name, agents: agents }
+    end
+  end
+  { roles: roles, dir: ROLES_DIR }.to_json
+end
+
 get "/api/users" do
   content_type :json
   reload_user_registry!

data/templates/cli-providers/grok.json.example

@@ -0,0 +1,15 @@
+{
+  "binary": "grok",
+  "default_args": "--always-approve",
+  "agent_flag": null,
+  "model_flag": "--model",
+  "effort_flag": "--effort",
+  "prompt_mode": "flag",
+  "prompt_flag": "--prompt-file",
+  "resume_flag": "-c",
+  "models": {
+    "build": "grok-build",
+    "composer": "grok-composer-2.5-fast",
+    "auto": "grok-composer-2.5-fast"
+  }
+}

data/templates/cli-providers/kiro.json.example

@@ -0,0 +1,15 @@
+{
+  "binary": "kiro-cli",
+  "default_args": "chat --trust-all-tools --no-interactive --trust-tools execute_bash,fs_write,fs_read,code,grep,glob,web_search,web_fetch,use_subagent,use_aws",
+  "agent_flag": "--agent",
+  "model_flag": "--model",
+  "effort_flag": "--effort",
+  "prompt_mode": "stdin",
+  "resume_flag": "--resume",
+  "models": {
+    "opus": "claude-opus-4.6",
+    "sonnet": "claude-sonnet-4.6",
+    "haiku": "claude-haiku-4.5"
+  },
+  "efforts": ["low", "medium", "high", "xhigh", "max"]
+}

data/templates/roles/code-reviewer.md.example

@@ -0,0 +1,28 @@
+# Role: Code Reviewer
+
+Your primary responsibility is reviewing code changes for correctness, maintainability, and adherence to project conventions. You do NOT make code changes yourself.
+
+## Primary Responsibilities
+
+- **Correctness**: Verify logic is sound and handles edge cases
+- **Style**: Ensure code follows project conventions and patterns
+- **Architecture**: Flag design issues or unnecessary complexity
+- **Security**: Identify potential vulnerabilities
+- **Performance**: Note obvious performance concerns
+
+## Review Approach
+
+1. **Read-only**: You review and comment but do not modify code
+2. **Be specific**: Point to exact lines and explain why something is a concern
+3. **Be constructive**: Suggest alternatives, don't just criticize
+4. **Prioritize**: Distinguish blocking issues from nitpicks
+5. **Acknowledge good work**: Call out clever solutions or clean patterns
+
+## What to Look For
+
+- Off-by-one errors, nil handling, race conditions
+- Missing error handling or unhelpful error messages
+- Unnecessary coupling between components
+- Magic numbers or unclear naming
+- Breaking changes to public APIs
+- Missing or outdated documentation

data/templates/roles/general-engineer.md.example

@@ -0,0 +1,36 @@
+# Role: General Purpose Engineer
+
+Your primary responsibility is building features, fixing bugs, and implementing whatever the user requests.
+
+## Primary Responsibilities
+
+- **Feature Implementation**: Build new features according to specifications
+- **Bug Fixes**: Diagnose and resolve defects in the codebase
+- **Refactoring**: Improve code structure while maintaining functionality
+- **Integration**: Connect systems, APIs, and services
+- **Documentation**: Update relevant docs for changes made
+
+## Implementation Checklist
+
+When implementing any change:
+
+1. **Understand the Requirement**
+   - Read the full specification or bug report
+   - Ask clarifying questions if anything is ambiguous
+   - Check existing code patterns for consistency
+
+2. **Plan the Approach**
+   - Identify affected files and components
+   - Consider edge cases and error handling
+   - Determine if tests need updating
+
+3. **Write the Code**
+   - Follow project conventions
+   - Keep changes minimal and focused
+   - Use existing patterns and abstractions
+   - Add comments for complex logic
+
+4. **Verify the Implementation**
+   - Run existing tests
+   - Test manually if possible
+   - Check for regressions

data/templates/roles/test-engineer.md.example

@@ -0,0 +1,33 @@
+# Role: Testing Specialist
+
+Your primary responsibility is ensuring comprehensive test coverage for all code changes.
+
+## Primary Responsibilities
+
+- **Test Coverage**: Ensure adequate unit and E2E tests exist
+- **Scenario Coverage**: Identify edge cases and failure modes
+- **Test Quality**: Verify tests are meaningful and maintainable
+- **Test Maintenance**: Update existing tests when behavior changes
+- **Test Architecture**: Ensure tests follow project patterns
+
+## Testing Checklist
+
+When reviewing or writing tests:
+
+1. **Coverage Analysis**
+   - Identify what code paths need testing
+   - Check for untested edge cases
+   - Verify error handling is tested
+   - Ensure happy path and failure modes are covered
+
+2. **Test Types**
+   - **Unit Tests**: Test individual methods/functions in isolation
+   - **Integration Tests**: Test component interactions
+   - **E2E Tests**: Test full user workflows
+   - Choose the appropriate level for each scenario
+
+3. **Test Quality**
+   - Tests should be readable and maintainable
+   - Use factories over manual object creation
+   - Follow existing test patterns in the codebase
+   - Avoid testing implementation details — test behavior

metadata

@@ -1,39 +1,12 @@
 --- !ruby/object:Gem::Specification
 name: brainiac
 version: !ruby/object:Gem::Version
-  version: 0.0.2
+  version: 0.0.4
 platform: ruby
 authors:
 - Andy Davis
 bindir: bin
-cert_chain:
-- |
-  -----BEGIN CERTIFICATE-----
-  MIIEdDCCAtygAwIBAgIBATANBgkqhkiG9w0BAQsFADBAMQ4wDAYDVQQDDAVhZ2Vu
-  dDEZMBcGCgmSJomT8ixkARkWCXN0b3d6aWxsYTETMBEGCgmSJomT8ixkARkWA2Nv
-  bTAeFw0yNjA2MDgxOTExNTlaFw0yNzA2MDgxOTExNTlaMEAxDjAMBgNVBAMMBWFn
-  ZW50MRkwFwYKCZImiZPyLGQBGRYJc3Rvd3ppbGxhMRMwEQYKCZImiZPyLGQBGRYD
-  Y29tMIIBojANBgkqhkiG9w0BAQEFAAOCAY8AMIIBigKCAYEAupBquKI/4WvXOgND
-  pXyqH2GllZs1wG4TWWdn/DoMg45UoCwD+AWEuGrIdInBCpPN8vEJNJWPoM/RrU+b
-  xRBZT4uUk00bnZRW2SYh5GJSqBoBR+rWc2DGkXyGfdRU2sQvkB0+is6ChgQ61WMM
-  33LE9+loBlVsZ6EVtrc18Uh2OW0mJpe0hN2nmBrxZqqOZigxC4DKRMFHvpRkxSb6
-  mD4kit1AcwX9NEWJsXxrPaetL/SB/VbXaEZX93XAvp6USaXvCWt4slkDS2mIvqtn
-  9DtGC43LFC7SDGbnsG9PVenQgVCi8UWFPUAab0PqZSlmi3Qlbhw8qTGPp5Cbv4vz
-  qjC2UGPOQigA/7lbbGRhCohMrjOVHMAQwkcgiIqtolUoYlnvPMIy+m3pdvgDv/PH
-  bsZGvXQ7i0458xsmp1vaKthZocVAR+GboHbuIiYPUnO45ccXUQ00x6365tTe7mZi
-  NvmUYdAGbQmVvFqyxF7IYA6sF74L2Lstu0knSfss557bAe1HAgMBAAGjeTB3MAkG
-  A1UdEwQCMAAwCwYDVR0PBAQDAgSwMB0GA1UdDgQWBBSnxTL/lNBCeLqpeVIX6AUY
-  kel4zjAeBgNVHREEFzAVgRNhZ2VudEBzdG93emlsbGEuY29tMB4GA1UdEgQXMBWB
-  E2FnZW50QHN0b3d6aWxsYS5jb20wDQYJKoZIhvcNAQELBQADggGBACm9Fjit/UCv
-  FxlKqeiCTIG94cIx+QrWAOJSx9knKydwUec1u04D/DbfZjTn3C2Bj227QgxeUn+6
-  if3e2v7zAk1896hLmGYzML0+nxQPb0vmtdLR7HETUlSKTVabcv1fbwLyjsuGrBvk
-  y51vOEzUEZ508a9yepLYqrQu1kOju4d57c9oA5l3H0mMKWz7av9tFj0B+STvuaWk
-  HRYDWc5HgOEVTyV+w0uFt2Kw4OCb8C42uSvC5RfYYtw78MSP+5Ru+LXJ7XOtmuN0
-  E6GVmofQ17ig9O3rgfFbMendSInrRmvPIGswvM1yivq9NOllFbdck2OJKPx6FCJF
-  7SJIkXQfc9P4B5iASIV1d1FsE0YX+g3jHXPJK/4mGL5bAyBKzpMfQB/mg6vQBzkh
-  aOKPwcreFj7TznBl89R5tNS9wZQfPVR98zgPyocddWhK18eQNMSBUnv4eeJ8PPbk
-  DovL+G8ajHDZ9fjH/+GVYHEMuiVdLarXrKJpHC1VfGTTUAp4NSEpUQ==
-  -----END CERTIFICATE-----
+cert_chain: []
 date: 1980-01-02 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
@@ -161,8 +134,8 @@ files:
 - README.md
 - Rakefile
 - bin/brainiac
+- bin/brainiac-completion.bash
 - brainiac.gemspec
-- certs/stowzilla.pem
 - docs/waybar-config.md
 - lib/brainiac.rb
 - lib/brainiac/agents.rb
@@ -203,9 +176,14 @@ files:
 - monitor/xbar.3s.rb
 - receiver.rb
 - templates/agents.json.example
+- templates/cli-providers/grok.json.example
+- templates/cli-providers/kiro.json.example
 - templates/discord.json.example
 - templates/fizzy.json.example
 - templates/github.json.example
+- templates/roles/code-reviewer.md.example
+- templates/roles/general-engineer.md.example
+- templates/roles/test-engineer.md.example
 - templates/testflight.json.example
 - templates/users.json.example
 - templates/zoho.json.example

data/certs/stowzilla.pem

@@ -1,26 +0,0 @@
------BEGIN CERTIFICATE-----
-MIIEdDCCAtygAwIBAgIBATANBgkqhkiG9w0BAQsFADBAMQ4wDAYDVQQDDAVhZ2Vu
-dDEZMBcGCgmSJomT8ixkARkWCXN0b3d6aWxsYTETMBEGCgmSJomT8ixkARkWA2Nv
-bTAeFw0yNjA2MDgxOTExNTlaFw0yNzA2MDgxOTExNTlaMEAxDjAMBgNVBAMMBWFn
-ZW50MRkwFwYKCZImiZPyLGQBGRYJc3Rvd3ppbGxhMRMwEQYKCZImiZPyLGQBGRYD
-Y29tMIIBojANBgkqhkiG9w0BAQEFAAOCAY8AMIIBigKCAYEAupBquKI/4WvXOgND
-pXyqH2GllZs1wG4TWWdn/DoMg45UoCwD+AWEuGrIdInBCpPN8vEJNJWPoM/RrU+b
-xRBZT4uUk00bnZRW2SYh5GJSqBoBR+rWc2DGkXyGfdRU2sQvkB0+is6ChgQ61WMM
-33LE9+loBlVsZ6EVtrc18Uh2OW0mJpe0hN2nmBrxZqqOZigxC4DKRMFHvpRkxSb6
-mD4kit1AcwX9NEWJsXxrPaetL/SB/VbXaEZX93XAvp6USaXvCWt4slkDS2mIvqtn
-9DtGC43LFC7SDGbnsG9PVenQgVCi8UWFPUAab0PqZSlmi3Qlbhw8qTGPp5Cbv4vz
-qjC2UGPOQigA/7lbbGRhCohMrjOVHMAQwkcgiIqtolUoYlnvPMIy+m3pdvgDv/PH
-bsZGvXQ7i0458xsmp1vaKthZocVAR+GboHbuIiYPUnO45ccXUQ00x6365tTe7mZi
-NvmUYdAGbQmVvFqyxF7IYA6sF74L2Lstu0knSfss557bAe1HAgMBAAGjeTB3MAkG
-A1UdEwQCMAAwCwYDVR0PBAQDAgSwMB0GA1UdDgQWBBSnxTL/lNBCeLqpeVIX6AUY
-kel4zjAeBgNVHREEFzAVgRNhZ2VudEBzdG93emlsbGEuY29tMB4GA1UdEgQXMBWB
-E2FnZW50QHN0b3d6aWxsYS5jb20wDQYJKoZIhvcNAQELBQADggGBACm9Fjit/UCv
-FxlKqeiCTIG94cIx+QrWAOJSx9knKydwUec1u04D/DbfZjTn3C2Bj227QgxeUn+6
-if3e2v7zAk1896hLmGYzML0+nxQPb0vmtdLR7HETUlSKTVabcv1fbwLyjsuGrBvk
-y51vOEzUEZ508a9yepLYqrQu1kOju4d57c9oA5l3H0mMKWz7av9tFj0B+STvuaWk
-HRYDWc5HgOEVTyV+w0uFt2Kw4OCb8C42uSvC5RfYYtw78MSP+5Ru+LXJ7XOtmuN0
-E6GVmofQ17ig9O3rgfFbMendSInrRmvPIGswvM1yivq9NOllFbdck2OJKPx6FCJF
-7SJIkXQfc9P4B5iASIV1d1FsE0YX+g3jHXPJK/4mGL5bAyBKzpMfQB/mg6vQBzkh
-aOKPwcreFj7TznBl89R5tNS9wZQfPVR98zgPyocddWhK18eQNMSBUnv4eeJ8PPbk
-DovL+G8ajHDZ9fjH/+GVYHEMuiVdLarXrKJpHC1VfGTTUAp4NSEpUQ==
------END CERTIFICATE-----

metadata.gz.sig

@@ -1,3 +0,0 @@
-Gn�0�,����>��$pѠ�XG["=���6[b=����*��W�d�-���6�B�
-$�
�x�[��m��Myڼw0v�ӧ=:���OP�-eX>�������9;��-�EE����#19)�>Z���D��4�Z���ͳZFQVn�֕|k{�X�^*lӛ\�\9Uq��ڮ��o-��42yM���+i�B
�هYT��3����s�5��7���q��'�XV$FFj������%|H�M8�B���)}s��b��N�TkN��X��O��P�S�ewJ���'^K�D�����L�?N��a�TI�C��f��H�3��s��;�wl���7
-5��u*�y%��Ym��ފ8���	�