mirror of
https://github.com/garrytan/gstack.git
synced 2026-09-21 04:10:47 +02:00
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This commit is contained in:
@@ -93,6 +93,20 @@
|
||||
"reproduced_defect": "Record only signal-bearing learnings",
|
||||
"regression_fixture": "evals/parity/regressions/pr-2030.json",
|
||||
"explanation": "### Signal-gated learning\n\nPersist a learning only when the interaction contains a useful, reusable signal such as an explicit preference, correction, accepted recommendation, or rejected direction. Track helpful and harmful outcomes separately. Do not manufacture a learning merely because a workflow completed."
|
||||
},
|
||||
{
|
||||
"classification": "INTENTIONAL_IMPROVEMENT",
|
||||
"issue_or_pr": "https://github.com/garrytan/gstack/pull/1523",
|
||||
"reproduced_defect": "Detect the shai-hulud campaign in comprehensive mode only",
|
||||
"regression_fixture": "evals/parity/regressions/pr-1523.json",
|
||||
"explanation": "### Known-campaign IOC tier\n\nAdd Tier 3 rules that detect the mini-shai-hulud supply-chain campaign: `/proc/*/mem` reads from Claude Code settings hooks, auto-run persistence bridges (folderOpen tasks or settings hooks invoking payloads), packed droppers that decrypt or decompress an embedded blob at load, and the getsession.org C2 IOCs. Every rule matches a deterministic primary-source indicator, surfaces only under comprehensive mode, and carries a TENTATIVE marking. Daily mode's zero-noise contract stays unchanged: none of these rules add findings there."
|
||||
},
|
||||
{
|
||||
"classification": "INTENTIONAL_IMPROVEMENT",
|
||||
"issue_or_pr": "https://github.com/garrytan/gstack/pull/1053",
|
||||
"reproduced_defect": "Keep the audit report-only unless --fix is passed",
|
||||
"regression_fixture": "evals/parity/regressions/pr-1053.json",
|
||||
"explanation": "### Opt-in auto-fix boundary\n\nThe default audit is strictly report-only and mutates nothing. Auto-fixes apply only under an explicit `--fix` flag, and only for provably safe patterns where the correct change is deterministic and the breakage risk is near-zero (additive gitignore hardening, TLS-verification flips, non-breaking dependency patches). No business logic and no guessing. Without `--fix`, produce findings and remediation plans and change no files."
|
||||
}
|
||||
]
|
||||
}
|
||||
|
||||
Reference in New Issue
Block a user