* docs(autofix): add an operator guide for `/takeover from N`
`qwen-autofix.md` records why each line of the workflow is the way it is,
indexed by code site — af-007 for the `from N` parser, af-016 for the
marker it writes. That answers "why is this code shaped like this", but a
maintainer deciding whether to seed a takeover has a different question:
what do I type, what number do I pick, and what happens next. Nothing
answered that.
This adds a task-oriented sibling guide covering the problem the seed
solves, how to choose N (with a table of remaining suggestion budget per
seed), the three semantics that surprise people — the seed is a floor for
an empty window rather than an offset added to every round, it dies with
its counting window so `/retry` and a bare `/takeover` both return the
counter to zero, and it is clamped strictly below the round cap while the
audit record still cites the number that was typed — and the two things
it deliberately does not do: seed the growth brake, or change what
Critical-only keeps flowing.
Every row of the accepted/rejected command table was produced by
replaying the merged parser fragment verbatim, so the doc records
observed behaviour rather than intent: `from 04` and `from 08` seed 4 and
8 rather than tripping octal, `from 0` engages as the explicit no-seed
spelling, and `stop from 4`, a doubled space, a 3-digit number, and a
prefixed or suffixed body all fail closed to no label and no seed.
Cross-linked both ways: the design record's preamble now points at
task-oriented guides, and the parser keeps its af-007 pointer with an
operator-guide line beside it. The workflow grows by 64 bytes, which the
size gate covers.
* docs(autofix): align the round-seed guide with the workflow behavior
Co-authored-by: Qwen-Coder <qwen-coder@alibabacloud.com>
---------
Co-authored-by: qwen-code-dev-bot <qwen-code-dev-bot@users.noreply.github.com>
Co-authored-by: Qwen-Coder <qwen-coder@alibabacloud.com>