+ iHjnRt^RIHt^RIHtHt^RIHt^tRt R RRllt R RR llt R R lt .R Ot R#)aVerification-loop helpers for the ``pre_verify`` round-end gate. After code edits the loop fires ``pre_verify`` (directives resolved by :func:`hermes_cli.plugins.get_pre_verify_continue_message`). The shipped coding guidance rides on the evidence-based verification-stop nudge rather than a second default stop gate, so default token cost stays tied to the "missing verification evidence" decision while ``pre_verify`` remains free for user/plugin policy. ) annotations)AnyOptional)is_truthy_valuea`[Coding] Before you run tests/linters or call this done: if this is creative UI/visual work, hold off on tests and linters until the user says they like the result or you're about to commit. And before every commit, clean your work: keep it KISS/DRY, match the surrounding code style, and be elitist, shorthand, clever, concise, efficient, and elegant.Nc V^8dQhRRRR/#)configOptional[dict[str, Any]]returnint)formats"7/home/ubuntu/.hermes/hermes-agent/agent/verify_hooks.py __annotate__rs))6)#)c\^\\V4PR444# \\ 3d \ u#i;i)zHBound on consecutive ``pre_verify`` continue directives per turn (>= 0).max_verify_nudges)maxr _agent_cfgget TypeError ValueErrorDEFAULT_MAX_VERIFY_NUDGESrs&rrrsD)1c*V,001DEFGG z ")(()s,/A A c V^8dQhRRRR/#)rrr r z Optional[str]r )r s"rrr%s""#;"}"rcj\\V4PRR4RR7'gR#\#)zBReturn the optional guidance appended to verification-stop nudges.verify_guidanceT)defaultN)rrrCODING_VERIFY_GUIDANCErs&rcoding_verify_guidancer%s, :f-112CTJTX Y Y !!rc V^8dQhRRRR/#)rrr r zdict[str, Any]r )r s"rrr,s < </ r.s=# ! C)" < qr