Skip to content

fix(workflow): feasibility gate + patches 6–10 (#65) - #73

Merged
dhicoc merged 1 commit into
mainfrom
fix/issue-65-feasibility-gate-patches-6-10
Aug 12, 2026
Merged

fix(workflow): feasibility gate + patches 6–10 (#65)#73
dhicoc merged 1 commit into
mainfrom
fix/issue-65-feasibility-gate-patches-6-10

Conversation

@dhicoc

@dhicoc dhicoc commented Aug 12, 2026

Copy link
Copy Markdown
Collaborator

Summary

Issue #65 follow-ups after PR #72:

A. User command feasibility gate

  • Keep redo X (no step substitution) but add prerequisite negotiation when X is blocked (e.g. packed sample + user wants IAT before unpack).
  • Forced steps still run with quality=unreadable/packed; unpack is prerequisite, not a substitute for import Evidence.

B. Reporter V3 patches 6–10

  • 6 self-check crash after unpack → dynamic
  • 7+10 breakpoint ladder TLS→EP→API→ExitProcess dump
  • 8 high-risk API clusters
  • 9 SHOULD time-boxes (overridable defaults)

Test plan

  • smoke + verify ×3 on pwsh and Windows PowerShell 5.1
  • CI
  • Maintainer confirm before merge

- User-command feasibility gate: obey goals not blind step order;
  blocked steps require explain + confirm; forced steps mark quality
- Redo-X clarified: named step or confirmed prerequisite path;
  unpack is prerequisite not substitute for import Evidence
- Patch 6: post-unpack self-check crash -> dynamic CreateFile/GetFileSize
- Patch 7+10: TLS -> EP -> sensitive API -> ExitProcess dump baseline
- Patch 8: high-risk API cluster hints when import table is huge
- Patch 9: SHOULD time-boxes (15min static / ~200 steps dynamic), overridable
- Wire RULES (en/zh), agent-obedience, malware, r2/ida; extend verify asserts
@dhicoc
dhicoc merged commit 0182b10 into main Aug 12, 2026
12 checks passed
@dhicoc
dhicoc deleted the fix/issue-65-feasibility-gate-patches-6-10 branch August 12, 2026 07:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant