+ iHj4a0t$Rt^RIHt^RIt^RIt^RIt^RIt^RIt^RI H t H t ^RI H t Ht^RIHtHtHtHtHtHt^RIHt^RIHt^RIHt]P8!]4tR t!R R 4t ] R R l4t!RRlt"RRlt#RRRR/RRllt$RRRR/RRllt%^t&Rt'Rt(Rt)RRlt*RRR llt+RR!R"llt,RR#R$llt-R%R&lt.RR'R(llt/R)R*lt0R+R,lt1R-R.lt2RR/R0llt3R1t4R2]4,R3,t5R4t6R5t7R6]6,R7,]7,R8,t8R9]4,R:,]6,R;,]7,R<,t9R=R>lt:R?RR@RRARRBR/t;RC]RIRJlt?Rt@RKRLltARMRNltBRORPltCRQRRltDRRSRTlltERURRVRRWRRXR/RYRZlltFRtGR[R\ltHR]R^ltIR_R`ltJRaRbltKRtLRcRdltMRReRflltNRgRhltORiRjltPRRkRllltQRmtRRnRoltSRRURp/RqRrllltTRstURtRultVRvRwltWRRxRylltX] !RzR{44tYR|R}ltZRR~Rllt[RRlt\RRRllt]RRRRRRRR/t^RRRllt_.ROt`R#)u)Background memory/skill review — fork the agent to evaluate the turn. After every turn ``AIAgent.run_conversation`` may spawn a daemon thread that replays the conversation snapshot in a forked :class:`AIAgent` and asks "should any skill/memory be saved or updated?". Writes go straight to the memory + skill stores; the main conversation and prompt cache are never touched. The fork inherits the parent's live runtime (provider, model, credentials, cached system prompt) so it hits the same prefix cache, and runs under a dispatch-side tool whitelist.) annotationsN)contextmanagersuppress) dataclassfield)AnyDictIteratorListOptionalTuple)t)resolve_prompt_cache_scope_safe)thread_scoped_silenceg@cJ]tRt^tRtRRltRRltRRltRR ltR t R #) _BackgroundReviewRunz9Per-review cancellation and request-completion handshake.cV^8dQhRR/#returnNone)formats"Latch request completion once; the caller publishes the event.NFT)r#r%r$r's&rmark_request_finished*_BackgroundReviewRun.mark_request_finished7sD ZZZ%%%Z:>t 6D "D$6 ZZZsA A  A )r&r#r%r$r r!N) __name__ __module__ __qualname____firstlineno____doc__r)r0r5r9__static_attributes__rrrrrsCA&rrc$V^8dQhRRRRRR/#)ragentrattrstrrzIterator[None]r)rs"rrrAs!#S^rc#"\WR4pVfRxR#V;_uu_4RxRRR4R# +'giR#;i5i)zF``with`` over a lock attribute that may be absent (direct test stubs).N)getattr)rBrClocks&& r_optional_lockrH@s1 5 %D |    s!A2 A A Ac V^8dQhRRRR/#)rrBrrOptional[_BackgroundReviewRun]r)rs"rrrKs1Orcv\4p\VRR4pVf\P!4;q nT;_uu_4\VRR4pVe,VP P 4'g RRR4R#WnRRR4V# +'giT#;i \\3dR#i;i)zCInstall a unique run token on the parent before ``Thread.start()``._background_review_lockN_background_review_run) rrFrr"rLr!r/rMAttributeError TypeError)rBrunrGcurrents& rprepare_background_review_runrRKs  C u7> <3<>>3C CD0 Te%=tDG"7+?+?+F+F+H+HT,/ (  JT J I &sA6B#1B4B5B#?BB# B B# B##B87B8c$V^8dQhRRRRRR/#)rrBrrPrJrrr)rs"rrr\s#2PUYrcVeVP4'gR#\VR4;_uu_4\VRR4VJdRVnRRR4VPP 4R# +'giL,;i)zGPublish one run's request exit without clearing a successor (ABA-safe).NrLrM)r9rHrFrMr!r4)rBrPs&&rfinish_background_review_runrU\sb {#3355 8 9 9 52D 9S @+/E ( : : 9s A.. A> messagezsuperseded by a new live turn tool_reasonzbackground review supersededc(V^8dQhRRRRRRRR/#)rr,rrVrDrWrrr)rs"rrrfs8]]]] ]  ]rcaaaRVVV3Rllp\P!VRRR7P4R# \d\P RRR7R#i;i) aRequest abort off-thread so a wedged abort hook cannot stall the live turn (the bounded ``request_done`` wait in the canceller relies on this returning fast). ``message``/``tool_reason`` default to the original live-turn-preemption wording; callers cancelling for a different reason (e.g. the owning session itself is ending, #102895) should pass their own so logs/diagnostics describe what actually happened. cV^8dQhRR/#rr)rs"rr2_interrupt_background_review..__annotate__ssfffrc<^RIHpV!SSSR7R# \d\P RSRR7R#i;i))request_hard_interrupt)rWz1Failed to cancel in-flight background review (%s)Texc_infoN)agent.interrupt_compatr^ Exceptionloggerdebug)r^rVr,rWs r _interrupt0_interrupt_background_review.._interruptss= f E "<k R f LLLg`dL e fs #==Tzbg-review-cancel)targetdaemonnamez5Failed to start background-review cancellation threadr_N)rThreadstartrbrcrd)r,rVrWresfdd r_interrupt_background_reviewrlfsTff] 4>PQWWY ] LW[ \]s'9"AAc(V^8dQhRRRRRRRR/#)rrBrrVrDrWrrr)rs"rrrs2& & & &  &  & rcz\VR4;_uu_4\VRR4p\VRR4pRRR4XfXMVP4pVe\WQVR7VfR#VPP \ R7'g\PR\ V4R#R# +'giL;i)u>Cancel the current review and await its request-phase acknowledgement. Foreground priority: past the bounded deadline, warn and let the live turn proceed — self-improvement work must never block a user-facing turn. Foreground priority is preserved: if the review does not acknowledge within the bounded deadline, a warning is logged and the live turn proceeds anyway. See #84423. Despite the name, this is also the session-teardown/interrupt cancellation path (``tui_gateway.session_lifecycle._finalize_session`` and ``_interrupt_session_turn``, #102895): a session ending or being explicitly stopped while its background review is still running must cancel that review the same way a new live turn preempts one — the review fork is invisible to every other interrupt/teardown mechanism (not tracked on ``session["running"]``, not joined by the run-thread wait), so this is the only thing that ever sets its ``_interrupt_requested``. Pass a reason-appropriate ``message``/``tool_reason`` when the caller isn't the live-turn-preemption path so diagnostics describe the real cause. rLrMN_background_review_agent)rVrW)timeoutzPBackground review did not acknowledge cancellation within %.1fs; proceeding (%s)) rHrFr5rlr!wait)_BACKGROUND_REVIEW_CANCEL_TIMEOUT_SECONDSrcwarning)rBrVrWrP legacy_agentr,s&$$ r&cancel_background_review_for_live_turnrus, 8 9 9e5t<u&@$G  :$'; ``(enabled, task_cfg)``. Fail-open (``enabled=True``) so a broken config never silently disables reviews — but WARN so the cost is visible.)safe_worker_enabled)finite_turn_requiredTFr)is_truthy_valueenabled)defaultzVFailed to read background_review.enabled; leaving automatic review enabled (fail-open)r_) agent.safe_worker_policyrgateway.session_finiterrrutilsrrr}rbrcrs)rrrrrs rload_background_review_settingsrs=;  4 6$ >by :)/12txx 2DA4GG  )  Rx s6A!!&B  B c$V^8dQhRRRRRR/#)rrBrrrrrxr)rs"rrrs#&&3&2J&Vd&rcra VP4pVPR4;'gRpRVPRVPRVPR4;'gRRVPR4;'gRRVR8XdRMTR \ VR R4R \ \ VR /4;'g/4R \ VR R4R \ VRR4R\ \ VR.4;'g.4RR/ p\V4o V 3RlR4wrVrxV'dDVR8wd=V'd5YPP;'gR8XdY`P;'gR8XdV#^RIH p V !WVWR7p RV PR4;'gTRV PR4;'gT/RU u/uFqV PV 4bK up CR \ V PR 4;'g/4R\ V PR4;'g.4RR/C#uup i \dp \YYl4TuRp ? #Rp ? ii;i)aOResolve provider/model/credentials for the review fork. Default (auto / unset / same as parent): the parent's live runtime with ``routed=False`` (codex_app_server -> codex_responses downgrade applied). When ``auxiliary.background_review.{provider,model}`` names a different concrete model, resolve that runtime and set ``routed=True``.api_modeNprovidermodelapi_keybase_urlcodex_app_servercodex_responsescredential_pool_credential_poolrequest_overrides max_tokenscommand acp_commandargsacp_argsroutedFc3<"TF8p\SPVR44P4;'gRxK: R#5i)N)rDr}strip).0keyrs& r *_resolve_review_runtime..s9>:f3DHHS" $$&..$.:fs 4A Aautor)resolve_runtime_provider) requested target_modelexplicit_api_keyexplicit_base_urlT)rrrr)rrrrr) _current_main_runtimer}rrrFr~listrhermes_cli.runtime_providerrrb_warn_review_routing_fallback)rBrparent_runtimeparent_api_modeparent task_provider task_model task_base_url task_api_keyrrprers&& @r_resolve_review_runtimers 002N$((4<<OENNGU[[>%%i088D*nFXFXYcFdFlFlhl:f>:M} mv5*....B/J;;CTCTRT4U H %#)  z*;;mWbffWoFcFcYc +lm+lCBFF3K+lm  bff-@&A&G&GR!H D--2.$   m %eJJ sH(HHH$H> H#H HH H6 H1+H61H6c ,V^8dQhRRRRRRRRRR /#) rrBrrrDrerrorrbrrr)rs"rrr&s1ScZchlrc \V4'd!\V4P4^,MRp\PRWW@PVP 4\ RWW@PVP R7p\VRR4'dR#RVn\VR R4p\V4'd+\\4;_uu_4V!V4RRR4R#R# +'giR#;i) aThe configured review route could not be resolved, so the fork runs on the main model. That was a debug-level line nobody saw (#116055): the misrouted model never ran and nothing said so. User-visible notice once per agent (same rail as the reasoning_effort notice); log every time.ruauxiliary.background_review.provider=%r (model %r) could not be resolved: %s — background reviews run on the main model %s/%s instead.z'display.review.routing_fallback_warning)rrrrr_warned_bg_review_routingFNT _emit_warning) rD splitlinesrcrsrrr rFrcallablerrb)rBrrr error_linerVemits&&&& rrr&s035zzU&&(+rJ NN /0=:WeWeglgrgrt9 >>NGu1599&*E# 5/4 0D~~ i M!  s  C)) C: c V^8dQhRRRR/#)rrBrrr-r)rs"rrr9s  s t rc\VRR4pYe \V4MR3F'p\VRR4pVfKVfK\V4u# R#)uWhether a fork inheriting ``agent``'s runtime could act at all: an agent-as-provider client shim declaring ``SUPPORTS_HERMES_TOOL_CALLS = False`` (instance or class) is skipped — the fork would be a guaranteed no-op that still pays a full spawn. Silence means capable.clientNSUPPORTS_HERMES_TOOL_CALLST)rFtyper-)rBr candidate supporteds& r_parent_can_emit_tool_callsr9sTUHd +F.@d6ldK I'CTJ  Y%: ? "L rc V^8dQhRRRR/#)rmr~rrDr)rs"rrrEs333#3rcVPR4p\V\4'dRPRV44p\V\4'dVP 4#R#)content c3v"TF/p\V\4'gKVPRR4xK1 R#5i)textrNr|r~r})rbs& rr_msg_text..Hs*I1Z45H&QUU62&&s99r)r}r|rjoinrDr)rcs& r _msg_textrEsN iA!T HHII I"1c**177922rc$V^8dQhRRRRRR/#)rmessages_snapshot list[dict]tailrrr)rs"rrrLs!88z88j8rc\T;'g.4p\V4V8dLW!)Rp\V^,\4'dV^,P R4R8XgM V^, pK[V#.pVR\V4)EF6p\V\4'gKVP R4\ V4P RR4rvVR8Xd&V'dVPRVR, 24KsVR 8XgK|VP R 4'd~VR ,Uu.uFFp\V\4'gKVP R 4;'g/P R R 4NKH p pVPRRPV 4 R24V'gEKVPRVR, 24EK9 RRPV4,p RRRV /.V,#uupi)zCompact replay for the routed (different-model) path only: keep the recent ``tail`` messages verbatim (extended so the kept run never starts on a tool result) and collapse older turns into one synthetic user-role digest, preserving role alternation.Nroletool ruserzUSER: :Ni,N assistant tool_callsfunctionri?zASSISTANT[tools: , ]z ASSISTANT: :NNu[Earlier conversation digest — older turns summarised to bound the review's cold-write cost on the routed aux model. Recent turns follow verbatim below.] r) rlenr|r~r}rreplaceappendr) rrmsgskeeplinesrrrtcnamesdigests && r_digest_historyr Ls !''R (D d)d EF|47D))d1gkk&.AV.K    E +CI: !T"" UU6]IaL$8$8s$Cd 6>d LL6$t*. / [ uu\""OPQ]wblmoqubvD"&&,2277Dw 051A0B!DEt {4:,78 $&*ii&6 7 VY / 04 77xs"G%?G%G%uTWO distinct stores — pick the right one for each fact: • USER.md (memory tool, target='user'): who the user is — persona, preferences, communication and work style, personal details they revealed, and expectations about how you should behave. • MEMORY.md (memory tool, target='memory'): facts about the ENVIRONMENT you operate in — tool quirks, project conventions, config gotchas, paths and endpoints that matter. One fact goes to ONE store, never both — writing it to both bloats both files until they hit their size limits and crowds out the facts that matter; misrouting it puts it where the next session won't look. If the tool schema lists only one target, that store is the only one enabled — use it and skip the other. zXReview the conversation above and consider saving to memory if appropriate. Memory has zIf something stands out, save it once, in the right store, using the memory tool with the matching target. If nothing is worth saving, just say 'Nothing to save.' and stop.uHWhat a skill IS: the instructions for doing a class of task the most efficient and correct way, to THIS user's specifications — the procedure, the tools and commands that work, the order, the user's preferences for how the result should look, and the pitfalls that cost time. A future session should be able to follow it and produce what the user wants on the first try. Everything below is about writing that well: • Procedure first: the steps in the order they are done, with the concrete commands, tool calls, and decision points. Lessons and pitfalls attach to the step they affect. • A pitfall is a generalizable rule + one clause of WHY (the mechanism), imperative. 'Grep the test tree for the SYMBOL before widening a helper signature — hand-rolled mocks reimplement the old shape and fail on a shard you did not run.' Not a narrative of what happened this session. • No PR/issue numbers, dates, ticket IDs, or quoted user text as content — the rule must stand without the incident behind it. Keep a short quote ONLY when the quote itself is the clearest statement of the rule. • The same lesson learned twice is ONE rule. Before adding, search the skill (and its references/) for the rule already stated; strengthen or clarify it rather than appending a second copy. • Not a duplicate of what the environment already teaches: repo AGENTS.md files, tool schema descriptions, and other always-loaded context. A skill carries the WORKFLOW and the pitfalls; it does not restate the codebase map or a tool's parameter list. • Always-on rules (standing user preferences, gates that apply to every instance of the task) live in SKILL.md itself, whole. references/ is for depth that is only needed sometimes: a decision table, a recipe, a domain note — each file topical and reusable, never '-.md'. Prefer extending an existing references/ file over creating one; a skill with dozens of one-off references is the failure shape, not the goal. • Fix the skill in place when it is wrong: edit the sentence that misled, do not append 'UPDATE: actually...' underneath it. u (these become persistent self-imposed constraints that bite you later when the environment changes): • Environment-dependent failures: missing binaries, fresh-install errors, post-migration path mismatches, 'command not found', unconfigured credentials, uninstalled packages. The user can fix these — they are not durable rules. • Negative claims about tools or features ('browser tools do not work', 'X tool is broken', 'cannot use Y from execute_code'). These harden into refusals the agent cites against itself for months after the actual problem was fixed. • Session-specific transient errors that resolved before the conversation ended. If retrying worked, the lesson is the retry pattern, not the original failure. • One-off task narratives. A user asking 'summarize today's market' or 'analyze this PR' is not a class of work that warrants a skill. • Unresolved failures: if the session ended WITHOUT actually finding a working method — you tried several things, none worked, and told the user to check manually — do NOT write those attempts up as a 'reliable workflow' or 'recommended approach'. That presents an untested sequence of failures as validated guidance a future session will trust and repeat. Either say 'Nothing to save', or, only if you are independently confident of a real working alternative (not something you are merely guessing might work), capture ONLY that alternative — never the dead ends, and never dressed up as best practice. If a tool failed because of setup state, capture the FIX (install command, config step, env var to set) under an existing setup or troubleshooting skill — never 'this tool does not work' as a standalone constraint. uReview the conversation above and update the skill library. Be ACTIVE — most sessions produce at least one skill update, even if small. A pass that does nothing is a missed learning opportunity, not a neutral outcome. Target shape of the library: CLASS-LEVEL skills, each with a SKILL.md of always-on rules and a small `references/` set of topical depth. Not a flat list of narrow one-session skills, and not an umbrella hoarding a references/ file per session. This shapes HOW you update, not WHETHER you update. uSignals to look for (any one of these warrants action): • User corrected your style, tone, format, legibility, or verbosity. Frustration signals like 'stop doing X', 'this is too verbose', 'don't format like this', 'why are you explaining', 'just give me the answer', 'you always do Y and I hate it', or an explicit 'remember this' are FIRST-CLASS skill signals, not just memory signals. Update the relevant skill(s) to embed the preference so the next session starts already knowing. • User corrected your workflow, approach, or sequence of steps. Encode the correction as a pitfall or explicit step in the skill that governs that class of task. • Non-trivial technique, fix, workaround, debugging path, or tool-usage pattern emerged that a future session would benefit from. Capture it. • A skill that got loaded or consulted this session turned out to be wrong, missing a step, or outdated. Patch it NOW. Preference order — prefer the earliest action that fits, but do pick one when a signal above fired: 1. UPDATE A CURRENTLY-LOADED SKILL. Look back through the conversation for skills the user loaded via /skill-name or you read via skill_view. If any of them covers the territory of the new learning, PATCH that one first (re-load it with skill_view during this review — see Read-before-write below). It is the skill that was in play, so it's the right one to extend — whoever wrote it: hand-written, installed, bundled, and pinned skills are all yours to improve. 2. UPDATE AN EXISTING UMBRELLA (via skills_list + skill_view). If no loaded skill fits but an existing class-level skill does, patch it. Add a subsection, a pitfall, or broaden a trigger. 3. ADD A SUPPORT FILE under an existing umbrella. Skills can be packaged with three kinds of support files — use the right directory per kind: • `references/.md` — topical depth needed only sometimes: a decision table, a reproduction recipe, provider quirks, condensed domain notes or API excerpts. Name it by TOPIC and extend an existing file when one covers the topic; do not create a per-session or per-incident file, and do not paste error transcripts — distill them to the rule. • `templates/.` — starter files meant to be copied and modified (boilerplate configs, scaffolding, a known-good example the agent can `reproduce with modifications`). • `scripts/.` — statically re-runnable actions the skill can invoke directly (verification scripts, fixture generators, deterministic probes, anything the agent should run rather than hand-type each time). Add support files via skill_manage action=write_file with file_path starting 'references/', 'templates/', or 'scripts/'. The umbrella's SKILL.md should gain a one-line pointer to any new support file so future agents know it exists. 4. CREATE A NEW CLASS-LEVEL UMBRELLA SKILL when no existing skill covers the class. The name MUST be at the class level. The name MUST NOT be a specific PR number, error string, feature codename, library-alone name, or 'fix-X / debug-Y / audit-Z-today' session artifact. If the proposed name only makes sense for today's task, it's wrong — fall back to (1), (2), or (3). Read-before-write (ENFORCED — skill_manage refuses otherwise): before you patch or edit an existing skill's SKILL.md, call skill_view(name) for that skill during this review. Before you overwrite or remove an EXISTING supporting file, call skill_view(name, file_path=...) for that exact file. Content quoted earlier in the conversation transcript does NOT count — the guard requires a fresh load within this review, and your write must be based on what skill_view just returned. Creating a brand-new skill or adding a NEW supporting file needs no prior read. If a write is refused with a read-before-write error, call skill_view for the named target once and retry the write once; do not loop. User-preference embedding (important): when the user expressed a style/format/workflow preference, the update belongs in the SKILL.md body, not just in memory. Memory captures 'who the user is and what the current situation and state of your operations are'; skills capture 'how to do this class of task for this user'. When they complain about how you handled a task, the skill that governs that task needs to carry the lesson. If you notice two existing skills that overlap, note it in your reply — the background curator handles consolidation at scale. Never delete a skill here. Do NOT capturez'Nothing to save.' is a real option but should NOT be the default. If the session ran smoothly with no corrections and produced no new technique, just say 'Nothing to save.' and stop. Otherwise, act.zBReview the conversation above and update two things: **Memory**: u**Skills**: how to do this class of task. Be ACTIVE — most sessions produce at least one skill update. A pass that does nothing is a missed learning opportunity, not a neutral outcome. Target shape of the skill library: CLASS-LEVEL skills with a SKILL.md of always-on rules and a small `references/` set of topical depth — not narrow one-session skills, and not an umbrella hoarding a references/ file per session. u Signals that warrant a skill update (any one is enough): • User corrected your style, tone, format, legibility, verbosity, or approach. Frustration is a FIRST-CLASS skill signal, not just a memory signal. 'stop doing X', 'don't format like this', 'I hate when you Y' — embed the lesson in the skill that governs that task so the next session starts fixed. • Non-trivial technique, fix, workaround, or debugging path emerged. • A skill that was loaded or consulted turned out wrong, missing, or outdated — patch it now. Preference order for skills — pick the earliest that fits: 1. UPDATE A CURRENTLY-LOADED SKILL. Check what skills were loaded via /skill-name or skill_view in the conversation. If one of them covers the learning, PATCH it first (re-load it with skill_view during this review — see Read-before-write below). It was in play; it's the right place, whoever wrote it. 2. UPDATE AN EXISTING UMBRELLA (skills_list + skill_view to find the right one). Patch it. 3. ADD A SUPPORT FILE under an existing umbrella via skill_manage action=write_file. Three kinds: `references/.md` for topical depth (decision tables, recipes, quirks, condensed domain notes) — extend an existing topical file before creating one, never a per-session file; `templates/.` for starter files meant to be copied and modified; `scripts/.` for statically re-runnable actions (verification, fixture generators, probes). Add a one-line pointer in SKILL.md so future agents find them. 4. CREATE A NEW CLASS-LEVEL UMBRELLA when nothing exists. Name at the class level — NOT a PR number, error string, codename, library-alone name, or 'fix-X / debug-Y' session artifact. If the name only fits today's task, fall back to (1), (2), or (3). Read-before-write (ENFORCED — skill_manage refuses otherwise): before patching or editing an existing skill's SKILL.md, call skill_view(name) during this review; before overwriting or removing an EXISTING supporting file, call skill_view(name, file_path=...) for that exact file. Content quoted earlier in the transcript does NOT count — base the write on what skill_view just returned. New skills and NEW supporting files need no prior read. On a read-before-write refusal: view the named target once, retry the write once, do not loop. User-preference embedding: when the user complains about how you handled a task, update the skill that governs that task rather than memory. Memory says 'who the user is and what the current situation and state of your operations are'; skills say 'how to do this class of task for this user'. A user-preference lesson lives in exactly ONE place: the skill that governs the task when one exists, USER.md only for cross-cutting preferences no skill owns — never both. Duplicating it is how a memory file ends up restating SKILL.md until both hit their size limits. If you notice overlapping existing skills, mention it — the background curator handles consolidation. Never delete a skill here. Do NOT capture as skillsuAct on whichever of the two dimensions has real signal. If genuinely nothing stands out on either, say 'Nothing to save.' and stop — but don't reach for that conclusion as a default.c$V^8dQhRRRRRR/#)rrrDlimitrrr)rs"rrr<s!??3?s?s?rcJVRV\V4V8d R,#R,#)Nu…r)r)rrs&&r_previewr<s& >2 >>raddrpatchremovezdict[str, tuple[str, str, int]]_MEMORY_OP_FORMATSc(V^8dQhRRRRRRRR/#)rlabelrDactionfieldszdict[str, str]r Optional[str]r)rs"rrrGs.yy3yy^y yrc \PV4;'gRwr4pV'dVPV4;'gRMRpV'd\RW\We4R7#R#)zMVerbose line for one memory add/replace/remove, or None when no preview text.Nrzdisplay.review.memory_op_line)rglyphpreview)Nrr])rr}r r)rrrr field_namerrs&&& r_memory_op_linerGsY155f=NNEu+06::j ! ' 'RbDjn1 ,EPXY]Pe fxtxxrc(V^8dQhRRRRRRRR/#)rdatar~detailrVrDrr)rs"rrrNs.FFdFDF3F3FrcVPRR4pVPRR4pVPR4p\V\4'dTM/pVPRR4;'gVPRR4pVPRR4;'gVPRR4pVR8Xd+V'g V'dR Wx34wr\R WIV R 7#R R RR/PV4p V 'd:VPR4'd#\RV\RV 24VR,R7#V'd\RVR7#\RVR7#)rrri_changeold old_stringnew new_stringrc3Z"TF!p\V^P4PRR4xK# R#5i)PrrN)rr)rrs& rr&_verbose_skill_line..Ws)#oVndHT2$6$>$>tS$I$IVns)+z$display.review.skill_patched_verbose)rir$r&createcreatededit rewritten descriptionz$display.review.skill_changed_verbosedisplay.review.skill_verb.)riverbr/z$display.review.skill_message_verbose)rVzdisplay.review.skill_action)r)r}r|r~r ) r r!rVr skill_name change_rawchanger%r' old_preview new_previewverb_keys &&& r_verbose_skill_liner8Ns9 ZZ" %FFB'J)$J!+J!=!=:2FE2&FF&**\2*FJE2&FF&**\2*FJ jJ#oWaVn#o 7j_jkk)V[9==fEHFJJ}--7jqSmnvmwQxOy#M24 4IP1 3W EFVWXuEWFFrc$V^8dQhRRRRRR/#)rrrDr!r~r list[str]r)rs"rrr`s&xxxdxyxrc VPR4p\V\4'dgV'd_VUu.uF7p\V\4'gK\ WPRR4V4NK9 ppVUu.uFqU'gK VNK up#\ WPRR4V4;'g\ RVR7.#uupiuupi) operationsrrdisplay.review.label_updatedr)r}r|rr~rr )rr!ops_rawoprlines&& r_verbose_memory_linesrB`sjj&G'4  WLSlGbWabdfjWkAx( parsed call arguments for notify tools. Result JSON only says "Entry added"; the call arguments carry action, target and content previews. Restricting to notify tools keeps helper tools from surfacing as memory work just because they succeeded.memory skill_managerrrrririd arguments{}rr<) r4r|r~r}rjsonloadsJSONDecodeErrorrO_CALL_DETAIL_DEFAULTS) rD notify_toolsall_tool_call_ids call_detailsmsgr fnfn_nametcidrkrs & r_collect_review_call_detailsrWpsln-L UL$$"$#t$$;(F '',+11r1Bb$'' B'--2BffVR(G66$.s- Y~!At).s)fDeD%-DeFskillrFrzdisplay.review.label.c3,<"TF qS9xK R#5ir{r)rrVr}s& rrr~s N"MQ5j"Mrrr=r>)rmrsro)addedreplacedrqapplied) r}r|rr~rr r}anyr8rB)r r!rhrVrgis_skillverbsrlrresultr7rx label_keyrhitr}s&&& @r _action_linesrs xx%)HH->$?$?DHHYDWDWY _]__hhy"%G XXh # ? ?vzz(B'?Fzz&!^3HxI%9gy&+y-HiY((9%xx,--Z5N5NIFfd++vzz)/DD/PyyH!56HxFJJv..6$%(B8*&M$NUY[\  MMOE  U*i5.@!cc)fDe)fccc)fDe)f&f&fy F #(Hff)M)Q)QRX)YI6?A%i[1 2VE?G#D':;qMbchMqq # N"M N### N"M N N m mSYSlSl^cgl^lC?BA,E : ;JJrc(V^8dQhRRRRRRRR/#)rrDrr_notification_moderDrr:r)rs"rrrs,"""1;"PS""rc \T;'gR4P4pVR8Xd.#VR8Hp\V4wrV\V4wrx.p \ V4Fp V P R4p V 'dW9gV'd W9dK2M5\ V P R4\4'dV R,V9dKh\P!V P RR44p \ T \4'dT P R4'gKT P\YP T 4;'g/T44K V # \P\3dEKi;i)aHuman-facing action summary for a background review pass: successful memory / skill-management tool results from the review agent's messages, skipping tool messages already present in ``prior_snapshot`` so inherited results are not re-surfaced as fresh work. ``notification_mode``: ``off`` -> no actions; ``on`` -> generic "Memory updated"/tool messages; ``verbose`` -> content previews from the tool-call arguments. See #14944. onoffrhrbrrJru)rDr}rfrWr]r}r|rKrLrMrOr~extendr) rDr_rmoderhexisting_tool_call_idsexisting_tool_contentsrPrQactionsrRrUr s &&& r#summarize_background_review_actionsrs8  ((D ) / / 1D u} iG5En5U2&B?&S#Go.ww~& -2CH`  *C 0 0S^G]5]  ::cggi67D $%%TXXi-@-@ }T+;+;D+A+G+GRQR/ N$$i0   s&EE10E1 write_originexecution_contexttask_idrbc 0V^8dQhRRRRRRRRRRRR /#) rrBrrrrrrbrrxr)rs"rrrsFFF F!.FJWF F1>FFrcRT;'g\VRR4RT;'g\VRR4RVP;'gRR VP;'gRR VP;'g!\P P R R 4R RRT;'gRRT;'gR/pVP4UUu/uFwrgVR9gKWgbK upp#uuppi)z?Build provenance metadata for external memory-provider mirrors.r_memory_write_originassistant_toolr_memory_write_context foreground session_idrparent_session_idplatformHERMES_SESSION_SOURCEcli tool_namerFrNrb>Nr)rFr_parent_session_idrosenvironr}items)rBrrrrbmetadatarVvs&$$$$ rbuild_memory_write_metadatars  ``7MO_(`.gg'%AXZf2ge&&,,"U55;;ENNTTbjjnn5Le&TX7??d ,, H&^^- E-TQ*1DDAD- EE Es > CCc V^8dQhRRRR/#)rr,rrrxr)rs"rrrsrc /RUu/uFq\WR4bK upC\Uu/uF&q\\VRV 2^4;'g^4bK( upCR\VRR4/C#uupiuupi)zASnapshot in-memory usage counters from a review fork (pre-close).Nsession_estimated_cost_usdsession_estimated_cost_usd)rrr)rF_USAGE_COUNTERSr)r,rs& r_snapshot_review_usagers <] ^<]S 40 0<] ^ P_ `P_GLHSE*:A>CC!D DP_ `  gl4PRVW  ^ `s A%,A*c$V^8dQhRRRRRR/#)r parent_agentrusagerxrrr)rs"rrr s'TTT^TPTTrc@\VRR4p\VRR4p\Uu/uF'qD\VPV4;'g^4bK) ppVe(V'd \ VP 44'gR#VP !V3RRRVPR4RVPR4R VPR 4R VPR 4R VPR 4/VBR#uupi \d"p\PRT4Rp?R#Rp?ii;i)u<Record a fork's usage against the parent session (best-effort, never raises). The fork has ``_session_db = None`` so conversation_loop's DB-gated accounting never sees its calls; route them through the aux-accounting chokepoint, which writes only ``session_model_usage`` — never the transcript or ``sessions`` row. _session_dbNrrr{rbilling_providerrbilling_base_urlrrapi_call_count api_callsz8Background review usage recording failed (non-fatal): %s) rFrrr}rvaluesrecord_auxiliary_usagepoprbrcrd)rr session_dbrrcountsrs&& r_record_review_usage_to_parentr s T\=$? \<> ;JK?Cs599S>..Q//?K  Zs6==?7K7K ))  0 8= '8J "YYz2 EJYYzEZ  %yy)=> "::k2  7=  L T OQRSSTs;"C1!C, C, C1C1A*C1,C11 D<DDc V^8dQhRRRR/#)rrr:rrDr)rs"rrrs k kY k3 krcaaT;'g.Uu.uFGp\V4P4PR4P4P4NKI ppR\ R4P43oRR\ R4P4\ R4P43o\ ;QJdV3RlV4F 'gK R M R M!V3RlV44p\ ;QJdV3R lV4F 'gK R M R M!V3R lV44pR P R RV3RV3344;'gR#uupi)u9Map a review action summary to ``none`` / ``skill`` / ``memory`` / ``skill+memory``. Prefix-based on the formats :func:`summarize_background_review_actions` emits (``Skill …``, ``📝 Skill …``, ``Memory …``, ``User profile …``), so a free-text line like ``Skipped: no skill worth saving`` stays ``none``.u📝rzdisplay.review.label.skillrFz user profilezdisplay.review.label.memoryzdisplay.review.label.userc3D<"TFqPS4xK R#5ir{ startswith)rrAskill_prefixess& rr*_classify_review_result..(sGOON33 TFc3D<"TFqPS4xK R#5ir{r)rrAmemory_prefixess& rrr)sI&$___55&r+c3>"TFwrV'gKVxK R#5ir{r)rkindrs& rrr*s`*XYT\_DD*Xs  none)rDlstrip removeprefixr}r rr)rrlowers has_skill has_memoryrrs& @@r_classify_review_resultrs X_WdWdbdWd eWdVc&k  "//7>>@FFHWdF eq!=>DDFGN3P1Q1W1W1Y45;;=?OGGGGGII&II&IIJ 88`GY+?(JAW*X` ` j jdjjfsA E c$V^8dQhRRRRRR/#)rrrxrrDrrr)rs"rrr-s!.#$rcPa\P!R.V3RlR4OVN5!R#)zHEmit a per-fork completion line so cost is visible where it is incurred.zZBackground review complete: thread=bg-review calls=%d in=%d out=%d cache_read=%d result=%sc3l<"TF)p\SPV4;'g^4xK+ R#5i)r]N)rr})rrVrs& rr)_log_review_completion..2s+ n*mQ#eiila *ms!44N)r input_tokens output_tokenscache_read_tokens)rcinfo)rrsf&r_log_review_completionr-s/ KK " o*m n  rc V^8dQhRRRR/#)rrBrrrxr)rs"rrr@sS^rc R\VRR4R\VRR4/\Uu/uFp\WR4;p'gKWbK upCp\P!\VRR4;'g.4;p'dWCR&V#uupi)afAIAgent kwargs that keep a SAME-model fork's request bytes identical to the parent's. Only for the un-routed path: on a different model the cache is cold anyway, and the parent's reasoning-effort vocabulary may be invalid for the routed provider (OpenRouter forwards ``reasoning.effort`` unclamped; codex_responses passes ``max``/``ultra`` through unmapped).reasoning_configNephemeral_system_promptprefill_messages)rF_PROVIDER_PIN_ATTRScopydeepcopy)rBrCvalkwargsparent_prefills& r_same_model_parity_kwargsr@s GE+=tD!752KT#R  "5 \!4UY@Z9Z9Z949!4 \ Fwu6H$'O'U'USUVV~V%3!" M ]s BBc$V^8dQhRRRRRR/#)rrBrrrrrr)rs"rrrTs#""#"9Q"]a"rc\\V4PR4;'gR4P4pV'd\ VRR4'dR#RVn\ RVR7p\ VR R4p\V4'd)\\4;_uu_4V!V4RRR4\PR V4R# +'giL(;i) aOne-shot user-visible notice: ``auxiliary.background_review.reasoning_effort`` is IGNORED on the same-model path (#104116). The fork inherits the parent's ``reasoning_config`` verbatim so its request bytes keep the parent's prompt-cache prefix (#30532: a diverged ``thinking`` field on the fork-birth request re-created a large share of the cache); the no-op used to be silent, so a user who set the key saw no feedback at all. Gated on the parent so a nudge-per-turn session warns once, not per fork.reasoning_effortr"_warned_bg_review_reasoning_effortFNTz'display.review.reasoning_effort_warning)effortrz%s) rDrr}rrFrr rrrbrcrs)rBrrrVrs&& r_warn_ignored_reasoning_effortrTs/9==>PQWWUW X ^ ^ `F WU$H%PP/3E,9&IG 5/4 0D~~ i M! NN4!! s " C  C c V^8dQhRRRR/#rr,rrrr)rs"rrrgsKK3K4Krc\\VRR4RR4pRp\V4'dV!RRR7RpRVnW nV'd RVnR#R# \d\P RRR 7LDi;i) uQDetached in-memory compaction for a fork sharing the parent's session_id. Disabling compression (the old guard against compacting the parent's live session) removed the only bound on the review's snapshot. Persistence is already off, so compaction can only rewrite the fork's transcript — but the compressor's own SessionDB/session_id binding must be severed too, or cooldown/streak counters land on the parent's row. Force in-place mode and re-enable compression ONLY after the rebind succeeded (fail-closed); gates stay deferred until the first response so request #1 is a warm cache read.rNbind_session_stateFr)rrTzbackground-review compressor detachment failed; keeping compression DISABLED on this review fork (fail-closed, issue #93057 / #38727)r_)rFrrbrcrscompression_in_placecompression_enabled._review_defer_compaction_before_first_response)r,binddetacheds& r_detach_fork_compressionrgs 7<)=tDFZ\` aDH~~  DR 0H)-L%'/$FJ C  NN7   s A"A>=A>c V^8dQhRRRR/#)rrrrr)rs"rrrs'?D\rc\V4PR4pVeVR8XdR#^RIHpHpV!V4pVf'\ P RVRPV44V#)a``reasoning_config`` for a ROUTED fork from ``auxiliary.background_review.reasoning_effort`` (#94825). The routed branch never inherits the parent's effort (its vocabulary may be invalid for the routed provider), but an explicit per-task pin is the user's choice for THAT model and must win over provider defaults, as every other aux task already does via ``_get_task_extra_body``. None = unset (provider default); an unknown level warns and falls through to the default.rNr)VALID_REASONING_EFFORTSparse_reasoning_effortuwauxiliary.background_review.reasoning_effort %r is not a valid level (none, %s) — using the routed provider's defaultr)rr}hermes_constantsrrrcrsr)rrrrparseds& r_routed_reasoning_configrsa ,H 5 9 9:L MF ~2P #F +F ~ ,-3TYY?V5W  Mrc 0V^8dQhRRRRRRRRR R R R/#) rrBrrtrxrr-max_iterationsrrrrr)rs"rrrs9SndTW 8DRrcRVPR4;'g VPRTRRRVPRVPR4;'g VPRVPR4RVPR4;'gR R VPR 4;'gR R VPR 4R VPR 4;'g/R VPR\ VRR 4R\ VRR 4RR/p\ VPR4\4'd VR,VR&\ VPR4\4'dCVR,'d4TPVR,VPR4;'g.R7V'gVP\V44V#\V4;peWeR&V#)aAIAgent constructor kwargs for the review fork. skip_memory=True: an external memory plugin scoped to the parent's session_id would leak the harness prompt into the user's real memory namespace; built-in MEMORY.md/USER.md state is re-bound by the caller. Toolsets match the parent so ``tools[]`` is byte-identical (Anthropic's cache key includes it); the runtime whitelist restricts dispatch.rr quiet_modeTrrrrNrrrrenabled_toolsetsdisabled_toolsets skip_memoryrrr)rrr) r}rrrrrFr|rrDupdaterr)rBrrrrr routed_cfgs&&&&& r_fork_init_kwargsr s //EKK1A>S_aeENNJz0B0T0TennBFF:& BFF:4F4N4N$266)$,,.?HYAZRVV$78>>B@SUZUeUeGE+=tDWU,?F W[F"&&&,,!,/|"&&#S))bmm "Y-"&&.:N:NB O  /67 M1: :* G%/!" Mric$V^8dQhRRRRRR/#)rr,rrBrrr)rs"rrrs&NNsN3N4Nrc\P!\VRR4;'g.4VnVPUu0uFq"R,R,kK upVn\ VnR#uupi)u Same-model fork: advertise the parent's exact tools[] (its last outbound payload — an empty list included) so the request prefix matches byte-for-byte, then freeze the snapshot generation. Dispatch stays behind the review whitelist; advertising is not permission.toolsNrri)rrrFrvalid_tool_names _FROZEN_TOOL_SNAPSHOT_GENERATION_tool_snapshot_generation)r,rBrs&& r_inherit_parent_tool_surfacers^ wugt'D'J'JKLJVJ\J\$]J\$*%5f%=%=J\$]L!-ML*%^sA,r{c ,V^8dQhRRRRRRRRR R /#) rrBrrrrrrrDrz tuple[Any, dict[str, Any], bool]r)rs"rrrs=P&P& P&2P&NQP&P&&P&rc ^RIHp\W4p\VP R44pV'gVR8Xd \ W4V!R/\ WWbV4BpV;VnVnW7n VPVn VPVn VPVn ^;Vn VnR;Vn;VnVnRVnRVnVP(VnV'gjVP*VnVP,Vn\/V4pV'dWnVR8XdRVnVP54Vn\9Wp4\;V4\=W4VnWuV3#) u4Construct a detached AIAgent fork with warm prompt-cache parity (shared with ``/btw``): same runtime/credentials as the parent, byte-identical system prompt / tools[] / reasoning config on the same-model path, shared session_id for prefix warmth, full persistence detachment (no state.db writes, rotation, or external memory providers; in-place-only compaction). Returns ``(fork_agent, runtime_dict, routed)``; ``routed`` means a different model (cache cold — replay a digest). The caller owns registration, whitelisting, running, usage attribution and teardown.)AIAgentrr{TFNreviewr) run_agentrrr-r}rr rr _turn_origin _memory_store_memory_enabled_user_profile_enabled_memory_nudge_interval_skill_nudge_interval_skip_mcp_refresh_persist_disabledsuppress_status_output_end_session_on_closerr_cached_system_prompt session_startr_inherited_cache_scope_prompt_cache_fork_tag_conversation_root_id_cached_conversation_rootrrr) rBrrrr_rt_routedr,inherited_scopes &&$$ rbuild_cache_parity_forkr-sf" "% 2C3778$%G |'::&u7^.u7T\]^LMYYL% (J!-!&!4!4L#(#8#8L ).)D)DL&OPPL',*LmqpL"p\%ClFi).L&#L#..L -2-H-H *%*%8%8 ":%@ 2A / . .2:L /271L1L1N .$\9\*/I.`L+ g %%rc 2\PRW4R#)zNon-interactive approval: dangerous-command guards resolve to "deny" instead of input(), which would deadlock against the parent's TUI.z8Background review auto-denied dangerous command: %s (%s)deny)rcrs)rr/rs&&,r_bg_review_auto_denyr0s NNMwd rc V^8dQhRRRR/#)rcallbackrrrr)rs"rrr"s((C(D(rc^RIHp\\4;_uu_4V!V4RRR4R# +'giR#;i)r])set_approval_callbackN)tools.terminal_toolr4rrb)r2r4s& r_set_thread_approval_callbackr6"s'9 )  h'    s 1 A c(V^8dQhRRRRRRRR/#)rrBrr,registerr-rrr)rs"rrr)s.@@c@@4@D@rc ZVfR#\VR4'dD\VR4;_uu_4V'dWnMVPVJdRVnRRR4\VR4'd\VR4;_uu_4V'dVPP V4M@\ \ \4;_uu_4VPPV4RRR4RRR4R#R# +'giL;i +'giL/;i +'giR#;i)u`Add (``register=True``) or remove the fork on the PARENT's tracking slots: ``_background_review_agent`` (direct pointer the next live turn interrupts) and ``_active_children`` (interrupt() fan-out). Removal is identity-scoped and idempotent; both are best-effort for direct test stubs — the prepared run token is the live-turn cancellation authority.NrorL_active_children_active_children_lock) hasattrrHror:rrrrNr)rBr,r8s&&$r_track_review_forkr=)s u011 E#< = =1=.//<?15. > u()) E#: ; ;&&--l;j.99**11,?: < ;* > =:9 < ; ;s0'C3ADD D3 D  D D D* c(V^8dQhRRRRRRRR/#) rr,rrr review_memoryr-rr`r)rs"rrr@s2(F(F(F!9(FJN(F(Frcl^RIHpVP;'g VPpV'd V'dRR.MR.pV!VRR7Uu0uFqfR,R,kK ppVRR 0,p\ 4p\ V4P R .4p \V \4'dPV U u0uFCp \V \4'gKV P4'gK3V P4kKE pp Yx,T3#uupiuup i \d\PR RR 7L8i;i) u``(whitelist, configured_extra_tools)`` for the review fork — DISPATCH-side only, so the advertised ``tools[]`` stays byte-identical to the parent's (prompt-cache parity).)get_tool_definitionsrFskillsT)rrrri read_file search_files extra_toolsz*background_review extra_tools parse failedr_) model_toolsrArrr4rr}r|rrDrrbrcrd) r,rr?rA memory_onreview_toolsetsr whitelistconfigured_extra_tools extra_rawris &&& r_review_tool_whitelistrL@s 1,,RR 0R0RI.7Mx*PXzO0DVerv0wx0w1:v&&0wIx+~..I$#&%R28<@@PRS i & &?H%sytJW[]`Lalfjfpfpfrldjjly "%s  -/E EE;y4&t R AD QRs6 D:5D/D  D $D 8D D"D32D3cb]tRtRt$RtRtR]R&]!]R7t R]R&]!] R7t R ]R &R t R#) _ReviewForkStateikzSMutable hand-off between the fork phase and the outer worker's error/cleanup paths.Nrr,)default_factoryrrDrx review_usager) r;r<r=r>r?r,__annotations__rrrDr~rPr@rrrrNrNks-]L#"'"=OZ=#(#>L.>rrNc V^8dQhRRRR/#rr)rs"rrrts''''rc\\4;_uu_4VP4RRR4R# +'giR#;i)zThe fork shares the foreground session ID: close() / shutdown_memory_provider() are session-bound (close() kills that session's terminal processes), so release only clients.N)rrbrelease_clients)r,s&r_release_fork_clientsrUts* )  $$&    s 3 A c<V^8dQhRRRRRRRRR R R R R RRRRR/ #)rrBrrrpromptrDrr review_runrJstrNr?r-explicitrrr)rs"rrr{sX== =#-=7:=F^=.=4D=UY== =rc\W\R7wVnrWuPn\ WPRR7^RIHp Hp \VPW64wrRP\V 44pV 'dRV R2MRpV 'dR V R2MRpR V 9dR MRpR V 9dR MR pV !V RV,R,V,R,R7\\4;_uu_4^RI HpV!4RRR4Ve"VPVP4'dMVPP!VR,V,R,V,V 'd \#V4MTR7V !4VPeDVP$P'\)VP44\+WP$4\ WPRR7\-W4\/\1VPR.44Vn\5VP4RVnR# +'giEL@;i T !4TPeDTP$P'\)TP44\+YP$4\ YPRR7\-Y4i;i)aFork phase (inside thread-scoped silence): build the fork, run the prompt under the tool whitelist, snapshot its messages/usage, release its clients. Partial progress lands on ``st`` so the caller's error path still sees usage and the fork to clean up. ``explicit`` (/refine) keeps the ``background_review`` origin (curator/skill guards still apply) but marks the fork attended, so the unattended-only memory delete gate leaves the full operation set available.)rTr8)set_thread_tool_whitelistclear_thread_tool_whitelistrz& Configured extra tools also allowed: .ru8 Exception — these configured tools are also allowed: rFz and memory for notes (add only)zmemory and skill zskill zBackground review denied non-whitelisted tool: {tool_name}. Allowed here: skill_view/skills_list/read_file/search_files to read, skill_manage(action='patch'|...) to change skillsz Do not retry {tool_name}.) deny_msg_fmt)#_reset_background_review_read_marksNz You can only call uPmanagement tools. Other tools will be denied at runtime — do not attempt them.) user_messageconversation_historyF_session_messages)r-_REVIEW_MAX_ITERATIONSr,_review_attendedr=hermes_cli.pluginsr]r^rLrsortedrrbtools.skill_manager_guardsrar0run_conversationr rPr rrrUrrFrDrU)rBrrWrrXrYr?rZr*r+r]r^review_whitelistrJ extra_list deny_extra prompt_extramemory_phrase_denymemory_phrase_promptras&&&&&&&& r_run_review_forkrq{sT%< (>%@!BOS'/OO$uoo=Y/EbooW_/o,6"89:JKa9*QGgiJ_uMj\YZ[{}L@HK[?[;ac2:>N2N.T\ @! !$' '*4 47S S )  R+- 8  !9!9"//!J!J OO , ,558LL::$ &d+Y% $$  NNI   G  PBAF ??? "2??G < %%a(J&KQOO P'>&=$$ 5//EB$U7 ?? &)$$&;&=&=%boo6'>&=&=&=$$$$ &d+s+G:=F7 G:#G 82G:1I?I, I?7 G G: G7G2-G:2G77G:: I)AI$J$I))J, I< 7I?? J AML( -L  L( LL(  M( L8 3M_COMBINED_REVIEW_PROMPT_MEMORY_REVIEW_PROMPT_SKILL_REVIEW_PROMPTc8V^8dQhRRRRRRRRRR R R R R RR/#)rrBrrrr?r- review_skillsfocusrrrrXrJrZr)rs"rrrsS #->B(5'.__annotate__5s<._target5s $fxJ'( rs$T#  /(==D<   8 $,/)!!H"]3]6 ]6& 3& 6 & X '!%$+!2 k *2&R& 38N T)*YY/>,4 !4 49@@-A@-BCCP*+336II&.\"7].7^d_0dj?  "I/I7Tn %73 yF$x +>Z&KR"JF15FZ^F!FAEF$ T* k ("&K>&<$1 NP&+P&P&l(@.(FV ?? ?'=@dQ,l+];Q > r