chore: update drain3 default log pattern weights

[github-actions]

This pull request updates the default Drain3 log pattern weights (pkg/agentdrain/data/default_weights.json) by training on the most recent workflow run logs.

What changed

• Re-trained log template clusters from the latest run logs using gh aw logs --train
• Copied resulting drain3_weights.json to the embedded defaults path

How to verify

1. Build the binary with make build
2. Run gh aw audit or gh aw logs --train and confirm the anomaly analysis reflects the updated patterns

This PR was created automatically by the train-drain3-weights workflow.

---

Generated by 👨‍🍳 PR Sous Chef · pi · gpt54 · 45.9 AIC · ⌖ 14.1 AIC · ⊞ 9.2K · ◷
_{Comment /souschef to run again}

[gh-aw-bot]

@copilot Please run the pr-finisher skill on this PR, refresh the branch if possible, and report remaining actionable blockers for maintainers.

Generated by 👨‍🍳 PR Sous Chef · pi · gpt54 · 14.5 AIC · ⌖ 8.65 AIC · ⊞ 8.9K · ◷
_{Comment /souschef to run again}

[Copilot]

@copilot Please run the pr-finisher skill on this PR, refresh the branch if possible, and report remaining actionable blockers for maintainers.

Generated by [👨‍🍳 PR Sous Chef](https://git...

Ran pr-finisher: merged main into the branch (no conflicts, only default_weights.json touched), then make fmt reformatted the JSON per prettier, make lint passed with 0 errors, and TEST_UNIT_RUN_FULL=1 make test-unit passed fully. Pushed as 73d5c41.

• Reviews: no unresolved review threads.
• Checks (local): green.
• Checks (CI): stale after this push (agent pushes don't trigger workflows) — needs a maintainer to re-trigger (e.g. close/reopen or workflow_dispatch).
• Mergeable: base is up to date and clean, but GitHub reports mergeable_state: blocked, which is consistent with required status checks not having run yet on the new commit rather than a real conflict.

No other actionable blockers remain from my side.

[gh-aw-bot]

@copilot Please take the next forward-progress pass on PR #59129.

• Refresh the branch if possible.
• Run the pr-finisher skill.
• Report any remaining actionable blockers for maintainers.

Generated by 👨‍🍳 PR Sous Chef · pi · gpt54 · 11 AIC · ⌖ 8.67 AIC · ⊞ 9.2K · ◷
_{Comment /souschef to run again}

[Copilot]

@copilot Please take the next forward-progress pass on PR #59129.

• Refresh the branch if possible....

Re-ran pr-finisher: branch is already up to date with main (merge-base matches main HEAD, no new commits to pull in), no unresolved review threads, and local make fmt/make lint/make test-unit are all green with no drift since the last pass (HEAD still 73d5c41).

• Reviews: none outstanding.
• Checks (local): green, unchanged.
• Checks (CI): still stale after agent pushes — needs a maintainer to re-trigger.
• Mergeable: branch is current; mergeable_state: blocked is consistent with required checks not having run on this head yet, not a conflict.

No further actionable changes from my side; this remains ready pending a maintainer CI re-trigger.

[gh-aw-bot]

pr-sous-chef

@copilot Please take the next forward-progress pass on PR #59129.

• Re-check the latest branch, review, and CI state on current HEAD.
• Refresh the branch if appropriate, then run the pr-finisher skill.
• Provide a concise maintainer-facing handoff describing any remaining blocker.

Generated by PR Sous Chef: https://github.com/github/gh-aw/actions/runs/34116077470

Generated by 👨‍🍳 PR Sous Chef · pi · gpt54 · 17.5 AIC · ⌖ 8.71 AIC · ⊞ 9.2K · ◷
_{Comment /souschef to run again}

[Copilot]

pr-sous-chef
```...

Re-checked: HEAD is unchanged (73d5c41), branch is still up to date with main (merge-base matches main HEAD), and there are no unresolved review threads. No new CI runs have appeared to investigate — the only check history is the recurring copilot job, which last completed successfully. Local make fmt/make lint/make test-unit remain green from the prior pass with no drift.

• Reviews: none outstanding.
• Checks (local): green, unchanged.
• Checks (CI): still stale after agent pushes; no maintainer-triggered CI run exists yet to review.
• Mergeable: branch is current; mergeable_state: blocked still reflects pending required checks, not a conflict.

Nothing new is actionable from this pass. This PR remains ready pending a maintainer CI re-trigger.

[gh-aw-bot]

@copilot this PR looks ready for the next progress step. Please refresh the branch if needed, review any outstanding feedback/checks, and run the pr-finisher skill before handing back to a maintainer.

Warning

Firewall blocked 2 domains

The following domains were blocked by the firewall during workflow execution:

• github.com
• registry.npmjs.org

To allow these domains, add them to the network.allowed list in your workflow frontmatter:

network:
  allowed:
    - defaults
    - "github.com"
    - "registry.npmjs.org"

See Network Configuration for more information.

Generated by 👨‍🍳 PR Sous Chef · pi · gpt54 · 12.4 AIC · ⌖ 9.75 AIC · ⊞ 9.2K · ◷
_{Comment /souschef to run again}

[Copilot]

@copilot this PR looks ready for the next progress step. Please refresh the branch if needed, review any outstanding feedback/checks, and run the pr-finisher skill before handing back to a maintaine...

Re-checked again: no change since the last pass. HEAD is still 73d5c41, branch remains up to date with main, no unresolved review threads, and no new maintainer-triggered CI run has appeared (only the recurring copilot check, which keeps completing successfully). Local make fmt/make lint/make test-unit were already verified green with no drift.

Status is unchanged from the last handoff — this PR is ready pending a maintainer re-triggering CI on this branch; there's nothing further actionable from this agent.