add detection-and-anti-analysis reference

A decision file for when the app fights back or the tool cannot run here: separating
detection from a broken environment, choosing between workaround / change-route /
accept by cost instead of escalating, recognising an environment where dynamic
analysis genuinely cannot work (and switching to static rather than proving it
impossible), and keeping 'blocks my analysis' separate from 'blocks the deliverable'.
This commit is contained in:
inliver233
2026-09-19 23:03:15 +08:00
parent 173ad0d463
commit 02c832f847
3 changed files with 139 additions and 0 deletions
+5
View File
@@ -66,6 +66,11 @@ references/ loaded on demand, one topic each
mechanisms, how to tell which one actually fires, how to find the
site, forged section headers, function boundaries from
PT_GNU_EH_FRAME, scanner traps, and neutralising safely
detection-and-anti-analysis.md when the app fights back or the tool cannot run here: telling
detection apart from a broken environment, deciding by cost instead
of escalating, recognising an environment where dynamic analysis
simply does not work, and keeping the "blocks my analysis" question
separate from "blocks the deliverable"
toolchain.md what to install, how to invoke it non-interactively, which tools
are GUI-only, version-alignment traps, working offline
long-task-discipline.md live record, conclusion grading, drift control, timeout and