j/ PUdZddlmZiddddddddddd d d d d d dd dd dd dd ddddddddddiddddddddddddd d!d"d#d$d#d%d#d&d#d'd#d(d#d)d#d*d+d,d-d.d-id/d-d0d-d1d-d2d-d3d-d4d-d5d-d6d-d7d-d8d-d9d-d:d;dd;d?d;d@d;idAd;dBd;dCdDdEdDdFdDdGdDdHdDdIdDdJdDdKdDdLdDdMdDdNdDdOdDdPdDdQdDdRdDdDdDdSdSdSdSdSdSdTZdUdUdVdWdXdYZhdZZd[d\hZhd]ZeZ d^e d_<eeezezeze zZ d`Z daS)buqWhat this package deliberately does NOT do, and why - one name at a time. ⛔ THIS FILE EXISTS SO A REFUSAL CAN NAME THE FEATURE. Without it an out-of-perimeter call reaches a guid that was never created and comes back as `no object 'artifact@3' to answer 'read'` - technically true, useless to read, and indistinguishable from a bug in this package. With it the caller is told that reading an artifact is tracing, that tracing is outside the automation core, and that the refusal is a decision rather than a gap. ⛔ AND IT LIVES HERE, IN THE SHIPPED PACKAGE, not in the workbench. The perimeter was written first in a workbench script that measures how much work is left, and that is the wrong home for it twice over: the thing that has to REFUSE is this package, and a list kept somewhere that is never shipped is a second copy of a fact. The workbench inventory now reads this module (rule 16). The perimeter itself was chosen by the owner on 2026-08-27: the automation core, with tracing, HAR, video, codegen and the recorder, `APIRequestContext`, `CDPSession` and the clock left out. See `32-stacco-da-playwright.md` section 1. ) annotationsdisposeAPIResponseAPIRequestContextfetchfetchLogfetchResponseBody newRequestcancelz'artifacts: traces, videos and downloadsdeleteconnectOverCDPCDPdetachnewBrowserCDPSession newCDPSessionsendharCloseHAR harExport harLookupharOpenharStartharUnzipreadzan artifact streamcredentialsCreateWebAuthncredentialsDeletecredentialsGetcredentialsInstallpdfcaptureclockFastForwardclock clockInstall clockPauseAt clockResume clockRunForclockSetFixedTimeclockSetSystemTimecreateTempFileszAthe streamed upload path - set_input_files with local paths workscancelPickLocatorrecordercreateSelectorForTest hideHighlight highlightnextpause pickLocatorregisterLocatorHandler requestPauseresolveLocatorHandlerNoReplyresumerunTounregisterLocatorHandler closePagez=the driver's WebSocket server, which is what is being removed closeServerconnect ensureOpened sendToPage sendToServer startServer stopServer __waitInfo__tracingaddStackToTracingNoReplypathAfterFinished saveAsStream startTracing stopTracingstreamtraceDiscarded tracingGrouptracingGroupEnd tracingStarttracingStartChunktracingStarted tracingStoptracingStopChunkvideo)writezipscreencastChapterscreencastHideActionsscreencastRemoveOverlayscreencastSetOverlayVisiblescreencastShowActionsscreencastShowOverlayz*the client calls it inside context.close()z(the client sends it while tracing is offz+the client sends it at the end of a sessionz4the client annotates every wait for the trace viewer)rNrOrBrHr@>drop setOffline setWebSocketInterceptionPatternsregisterSelectorEnginesetTestIdAttributeName>rejectresolve exposeBindingsetExtraHTTPHeadersset WITHDRAWNc`t|}|sdS|dz|zdz|zdzS)zEThe sentence a caller gets, or an empty string if it is in perimeter.z is part of z], which invisible_playwright does not implement: the package covers the automation core, and zX is outside it by decision, not by omission. See 32-stacco-da-playwright.md section 5.4.)OUTSIDEget) operationfeatures XC:\Projects\Historical\venv\Lib\site-packages\invisible_playwright/_juggler/perimeter.pyrefusalrksQkk)$$G r  & 04$ $&- .1K KLN) __doc__ __future__rrfCOURTESYNO_ENGINE_COMMANDFIXED_AT_BUILD NOT_WIRED_YETrbrc__annotations__REFUSEDrkrlrjrvs&#""""" ^ ':^  ':^ ': ^  ': ^  ': ^  'P^  'P^ u^  u^ u^ u^  u^ "u#^ $u%^ &u'^ (u)^ *u+^ ^ ,u-^ 0 ';1^ 4z5^ 6z7^ 8z9^ :z;^ > y?^ BwC^ DwE^ FwG^ HwI^ JwK^ LwM^ NwO^ R'jS^ VzW^ XzY^ ^ ^ Zz[^ \z]^ ^ z_^ ` za^ bzc^ dze^ fzg^ h#zi^ j zk^ l zm^ nzo^ r'fs^ t'fu^ v'fw^ x'fy^ z'f{^ |'f}^ ^ ^ ~'f^ @'fA^ DyE^ FyG^ HyI^ JyK^ LyM^ NyO^ P yQ^ RyS^ TyU^ VyW^ XyY^ Zy[^ \y]^ ^y_^ `ya^ ^ b(1'0 (/'.'.'.'.'.{^ ^ ^ R@D JCJ   8    P  3w<<+ +n <} L  LLLLLrl