mirror of
https://codeberg.org/reverse-skill-lab/apk-reverse
synced 2026-11-16 04:04:25 +08:00
docs: stop citing workbench paths that are not shipped
Eight citations in the reference documents pointed at tools/ paths, and .gitignore excludes tools/ -- so neither an installed skill nor a clone of this repository can open them. Each is now either an inline statement of the fact or a pointer to the evidence file under docs/tool-verification/ that actually holds it. One of the eight was introduced by the benchmark pass itself (protocol-reverse.md cited a workbench script). The evidence records keep quoting tools/_work/... deliberately: there they are operation records of where a run happened. docs/tool-verification/README.md now states that distinction and the rule that follows from it -- a reference document never cites a tools/ path as its evidence, even when the work happened there.
This commit is contained in:
@@ -12,7 +12,13 @@ build time) the figure is kept and the target is named generically.
|
||||
|
||||
Targets measured: Flutter AOT applications, multi-dex, mid-size native library sets, no packer.
|
||||
|
||||
The APKs themselves are **not** in this repository (`.gitignore` excludes `*.apk`).
|
||||
The APKs themselves are **not** in this repository (`.gitignore` excludes `*.apk`, and `tools/`).
|
||||
|
||||
**Workbench paths are an operation record, not a pointer.** A record may say a run happened *at*
|
||||
`tools/_work/...` so the command can be judged; `.gitignore` excludes `tools/`, so that path is not
|
||||
something a reader can open. Anything a reader is *meant* to follow is named under
|
||||
`docs/tool-verification/` or inside the skill — that rule is why a reference document never cites a
|
||||
`tools/` path as its evidence, even when the work happened there.
|
||||
|
||||
## Strength labels
|
||||
|
||||
|
||||
Reference in New Issue
Block a user