§
    ¬	ÊjÍ  ã                   ó2   — d Z ddlZddlmZ eej        e<   dS )a  Back-compat alias. The module is `invisible_core.pin` since 2026-07-27.

WHY IT WAS RENAMED. The leading underscore told every reader of this package
that the module was internal and free to change. It was not: measured that day
by parsing both consumers' sources, `invisible-playwright` and
`invisible-firefox` import **nineteen names** from it, at module level, on the
first line of their own `__init__`. They pin `invisible-core==` to an exact
version, so a rename in here does not fail their build - it fails their IMPORT,
on the machine of whoever upgrades next, with a traceback naming a symbol
instead of a version. That exact shape had already reached a user once.

The names are the contract either way. The rename makes the file say so, and
`tests/test_consumer_contract.py` is what enforces it.

WHY THIS FILE STILL EXISTS. Consumers published BEFORE the rename import
`invisible_core._pin` by name, and their pin normally resolves the core they
were built against - but an editable checkout, a `--no-deps` install or a
lockfile can put a new core under an old consumer, and that combination is
exactly the one the pin machinery exists to explain rather than crash on.
Two lines is a cheap way not to add another entry to the bug archive.

(No version number appears above, deliberately. A sibling guard,
`test_the_module_holds_no_version_literal`, forbids one anywhere in this
module INCLUDING the prose - a second copy of the version is the original bug -
and it caught the first draft of this docstring, which is the behaviour it is
for.)
é    Né   )Úpin)Ú__doc__ÚsysÚ_sysÚ r   Ú_modÚmodulesÚ__name__© ó    úCC:\Projects\Muse2API\.venv\Lib\site-packages\invisible_core/_pin.pyú<module>r      sC   ððð ð6 Ð Ð Ð à Ð Ð Ð Ð Ð ð €„ˆXÑ Ð Ð r   