pipulate 2.41__tar.gz → 2.43__tar.gz

{pipulate-2.41/pipulate.egg-info → pipulate-2.43}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: pipulate
-Version: 2.41
+Version: 2.43
 Summary: AI-readiness for the agentic web — local-first, Nix-reproducible workflows. The successor to AI SEO software.
 Author-email: Mike Levin <pipulate@gmail.com>
 License-Expression: AGPL-3.0-or-later
@@ -108,6 +108,39 @@ cd ~/pipulate
 nix develop
 ```
 
+<!-- DO NOT MOVE THIS BLOCK ABOVE "## Quick Start". Two splicers own
+     parts of this file, with two different boundary schemes:
+       1. release.py run_waxascii_release_stamp() -- HEADER-BOUNDED.
+          It finds the "I HEREBY WILL NOT RE-GENERATE" line near the
+          top and replaces EVERYTHING between the "# Pipulate:" header
+          and the next header with the sealed white_rabbit art. Runs on
+          every `release`. Anything inside that region is destroyed.
+       2. prompt_foo.py update_readme_md_in_place() -- SENTINEL-BOUNDED,
+          the two HTML comments below. Runs on every compile, refuses on
+          CRC drift, writes only when the bytes change.
+     The sentinels below are safe ONLY because they sit after
+     "## Quick Start", outside splicer 1's blast radius. Verified from
+     line numbers, not from a release run. -->
+### Where your work lives
+<!-- --- START WORKSPACE TREE --- -->
+```text
+   Notebooks/  — the JupyterLab root (NOT Pipulate's own root)
+   │            FLAT siblings. Nothing nests. Nothing to get wrong.
+   │
+   ├── Advanced_Notebooks/     canon · flake-delivered, copy-if-absent
+   ├── Educational_Notebooks/  canon · your edits survive, updates do not arrive
+   ├── imports/                canon · the code-behind "sauce" modules
+   │
+   ├── Playground/             personal · gitignored · your own git repo goes here
+   ├── Client_Work/            personal · gitignored · never leaves this machine
+   ├── Deliverables/           personal · gitignored
+   │
+   └── Shared/                 the ONE folder for handing work to a teammate
+       ├── alice/              one folder per person; you write ONLY your own
+       └── bob/                single-writer partitions = zero merge conflicts
+```
+<!-- --- END WORKSPACE TREE --- -->
+
 ## 💡 What Can You Actually Build?
 
 **Real examples of what people create with Pipulate:**

{pipulate-2.41 → pipulate-2.43}/README.md

@@ -51,6 +51,39 @@ cd ~/pipulate
 nix develop
 ```
 
+<!-- DO NOT MOVE THIS BLOCK ABOVE "## Quick Start". Two splicers own
+     parts of this file, with two different boundary schemes:
+       1. release.py run_waxascii_release_stamp() -- HEADER-BOUNDED.
+          It finds the "I HEREBY WILL NOT RE-GENERATE" line near the
+          top and replaces EVERYTHING between the "# Pipulate:" header
+          and the next header with the sealed white_rabbit art. Runs on
+          every `release`. Anything inside that region is destroyed.
+       2. prompt_foo.py update_readme_md_in_place() -- SENTINEL-BOUNDED,
+          the two HTML comments below. Runs on every compile, refuses on
+          CRC drift, writes only when the bytes change.
+     The sentinels below are safe ONLY because they sit after
+     "## Quick Start", outside splicer 1's blast radius. Verified from
+     line numbers, not from a release run. -->
+### Where your work lives
+<!-- --- START WORKSPACE TREE --- -->
+```text
+   Notebooks/  — the JupyterLab root (NOT Pipulate's own root)
+   │            FLAT siblings. Nothing nests. Nothing to get wrong.
+   │
+   ├── Advanced_Notebooks/     canon · flake-delivered, copy-if-absent
+   ├── Educational_Notebooks/  canon · your edits survive, updates do not arrive
+   ├── imports/                canon · the code-behind "sauce" modules
+   │
+   ├── Playground/             personal · gitignored · your own git repo goes here
+   ├── Client_Work/            personal · gitignored · never leaves this machine
+   ├── Deliverables/           personal · gitignored
+   │
+   └── Shared/                 the ONE folder for handing work to a teammate
+       ├── alice/              one folder per person; you write ONLY your own
+       └── bob/                single-writer partitions = zero merge conflicts
+```
+<!-- --- END WORKSPACE TREE --- -->
+
 ## 💡 What Can You Actually Build?
 
 **Real examples of what people create with Pipulate:**

{pipulate-2.41 → pipulate-2.43}/__init__.py

@@ -12,8 +12,18 @@ Usage:
     pipulate
 """
 
-__version__ = "2.41"
-__version_description__ = "So wI chu"
+__version__ = "2.43"
+# APOSTROPHES RESTORED (2026-08-04). They were stripped as a workaround for
+# flake.nix's descMatch regex, whose character class excluded ' from the
+# CAPTURE and truncated the banner to "(So)". That regex was fixed in the same
+# ride, and this line is now the only thing that exercises the fix: with the
+# apostrophes gone, the old regex and the new one print an IDENTICAL string, so
+# the straddle could not discriminate between a landed patch and a missing one.
+# A convention the author has to remember ("no apostrophes in version names")
+# is not a property of the system; the regex is. Blast radius is one banner:
+# nothing but flake.nix reads this name -- version_sync.py syncs __version__
+# and __description__, never this. So'wI' chu' -- "engage the cloaking device."
+__version_description__ = "Planning Kata Walks"
 # SPDX expression, single source of truth, synced into pyproject.toml by
 # scripts/release/version_sync.py. "-or-later" (not bare AGPL-3.0, which is
 # deprecated SPDX) because the header below grants "any later version".

{pipulate-2.41 → pipulate-2.43}/cli.py

@@ -428,9 +428,20 @@ def main():
         uninstall_pipulate(args.app_name)
 
     elif args.command == 'db-inspect':
+        # SAME FOSSIL, SECOND FILE (2026-08-04). db-inspect opened
+        # data/botifython_dev.db -- last written May 3 -- and printed its tables
+        # under the heading "Tables in botifython_dev.db", so an inspector built
+        # to show live state was confidently reporting a dead file's contents.
+        # Derived from the same identity value as the backup roster next door.
+        try:
+            from config import APP_NAME
+            app_stem = APP_NAME.lower()
+        except Exception as e:
+            console.print(f"⚠️  Could not resolve app name from config ({e}); assuming 'pipulate'.")
+            app_stem = 'pipulate'
         db_map = {
-            'main_dev': 'data/botifython_dev.db',
-            'main_prod': 'data/botifython.db',
+            'main_dev': f'data/{app_stem}_dev.db',
+            'main_prod': f'data/{app_stem}.db',
             'discussion': 'data/discussion.db',
             'keychain': 'data/ai_keychain.db'
         }

{pipulate-2.41 → pipulate-2.43}/imports/ascii_displays.py

@@ -66,7 +66,7 @@ FIGURATE_LEDGER: dict = {
     "canal_lock": 311868176,
     "mechanical_man": 4142234675,
     # CRC32 after _expand_color_bits_ai() + .strip()
-    "workspace_tree": 1744376308,  # CRC32 no-strip (leading newline preserved, like honeybot_pipeline)
+    "workspace_tree": 2408173560,  # CRC32 no-strip (leading newline preserved, like honeybot_pipeline)
     "forcing_pair": 3594006631,  # CRC32 no-strip; seal re-taken 2026-07-27 — 208394658 sealed a re-typed copy of the art, not the bytes on disk; the straddle caught it (drift 1→0)
     # === FIGURATE_LEDGER_EXTRUDE_BOTTOM ===
     # Add new artwork CRC32 entries immediately above this line
@@ -789,38 +789,45 @@ def _figurate_mechanical_man():
     human = Panel(human_art, title="🗝️ Tik-Tok — Two Keys Wound, One on the Wall", border_style="white")
     return human, ai_art
 
+
 def _figurate_workspace_tree():
-    """Render the three-tier Notebooks workspace: Corporate / Personal / Shared.
-
-    Self-documenting governance: read-only canon, a private sandbox, and a
-    single-writer outbound-exchange partition per username. Authored with no
-    .strip() so the leading newline is preserved (the honeybot_pipeline
-    convention), which the FIGURATE_LEDGER seal must match. No [[[color bits]]]
-    and no <angle tags>, so _expand_color_bits_ai leaves it untouched and
-    ai_art == art.
+    """Render the Notebooks workspace as it ACTUALLY sits on disk: flat.
+    THE NESTED VERSION WAS THE ONLY AUTHORITY THAT SHIPPED, AND IT WAS WRONG.
+    update_agents_md_in_place() splices this art into AGENTS.md on every
+    compile, so it is what every external agent tool reads -- while flake.nix
+    argued for flat siblings and `ls Notebooks/` showed nine flat directories
+    and no Corporate/, Personal/, or Workshop/ at all. Three authorities, one
+    winner, and the winner disagreed with the disk. Fixed at the GENERATOR so
+    the output cannot drift back.
+    Three tiers, zero nesting: canon arrives by the flake's copy-if-absent
+    loop, personal is gitignored, and Shared/ is the single deliberate
+    outbound surface with one folder per person. Authored with no .strip() so
+    the leading newline is preserved (the honeybot_pipeline convention), which
+    the FIGURATE_LEDGER seal must match. No color-bit or angle-tag markers, so
+    _expand_color_bits_ai leaves it untouched and ai_art == art.
     """
     art = r"""
    Notebooks/  — the JupyterLab root (NOT Pipulate's own root)
-   │            every level advertises its own AGENTS.md + OKF index.md
+   │            FLAT siblings. Nothing nests. Nothing to get wrong.
    │
-   ├── Corporate/   read-only canon · auto-pulled · git wins on collision
-   │   ├── AGENTS.md
-   │   ├── .agents/skills/
-   │   └── apps/          org plugins ride in — no core commit needed
+   ├── Advanced_Notebooks/     canon · flake-delivered, copy-if-absent
+   ├── Educational_Notebooks/  canon · your edits survive, updates do not arrive
+   ├── imports/                canon · the code-behind "sauce" modules
    │
-   ├── Personal/    your sandbox · gitignored · vibe-code freely
-   │   ├── AGENTS.md
-   │   └── Playground/    NOTHING here is ever shared
+   ├── Playground/             personal · gitignored · your own git repo goes here
+   ├── Client_Work/            personal · gitignored · never leaves this machine
+   ├── Deliverables/           personal · gitignored
    │
-   └── Shared/      outbound exchange · one folder per name
-       ├── alice/        you write ONLY your own folder;
-       └── bob/          single-writer partitions = zero merge conflicts
+   └── Shared/                 the ONE folder for handing work to a teammate
+       ├── alice/              one folder per person; you write ONLY your own
+       └── bob/                single-writer partitions = zero merge conflicts
 """
     ai_art = _expand_color_bits_ai(art)
     human_art = _expand_color_bits_human(art)
-    human = Panel(human_art, title="🗂️ Notebooks Workspace — Corporate / Personal / Shared", border_style="white")
+    human = Panel(human_art, title="🗂️ Notebooks Workspace — canon · personal · Shared", border_style="white")
     return human, ai_art
 
+
 def _figurate_forcing_pair():
     """Render the two creativity forcing functions as ONE composed frame.
 

{pipulate-2.41 → pipulate-2.43}/imports/durable_backup_system.py

@@ -60,6 +60,32 @@ class DurableBackupManager:
                 logger.debug(f"Could not set backup directory permissions: {e}")
 
         logger.info(f"🗃️ Rolling backup root: {self.backup_root}")
+        # THE ROSTER IS DERIVED, NOT LITERAL (2026-08-04, fossil-convicted on
+        # the maintainer's own box). The app database filename is a pure
+        # function of whitelabel.txt: config.py builds data/{APP_NAME.lower()}.db
+        # and server.py:322 independently builds the same string. This roster
+        # hardcoded 'botifython'. whitelabel.txt here says Pipulate, so the live
+        # databases are data/pipulate*.db (mtime Jul 30) while the roster kept
+        # copying data/botifython_dev.db (mtime MAY 3) once per server start,
+        # forever. The distinct backup stems were ai_keychain / botifython /
+        # botifython_dev / discussion: the live Profiles/Tasks database had NEVER
+        # been backed up, and the two stale files are exactly what hid it --
+        # os.path.exists returned True, no warning fired, and the summary table
+        # printed a green checkmark beside a file nobody had touched in three
+        # months. A stranger with only one family at least gets a "not found"
+        # line in a log. THE DERIVED-PATH RULE: compute the target from an
+        # identity value you read and cannot author, so the mismatch becomes
+        # unrepresentable instead of merely unlikely.
+        try:
+            from config import get_app_name
+            app_stem = get_app_name().lower()
+        except Exception as e:
+            # Fail LOUD, then mirror config.py's own basename rule. A silent
+            # fallback would be the same disease this patch is curing.
+            logger.warning(f"⚠️ Could not resolve app name from config ({e}); "
+                           f"deriving the backup roster from the install directory name.")
+            root_name = Path(__file__).resolve().parent.parent.name
+            app_stem = (root_name[:-5] if root_name.endswith('-main') else root_name).lower()
 
         # 🎯 CRITICAL DATABASES TO PROTECT
         self.critical_databases = {
@@ -76,13 +102,13 @@ class DurableBackupManager:
                 'cross_cutting': True
             },
             'app_prod': {
-                'source_path': 'data/botifython.db',
+                'source_path': f'data/{app_stem}.db',
                 'description': 'Production Profiles/Tasks',
                 'critical': True,
                 'cross_cutting': False
             },
             'app_dev': {
-                'source_path': 'data/botifython_dev.db',
+                'source_path': f'data/{app_stem}_dev.db',
                 'description': 'Development Profiles/Tasks',
                 'critical': False,
                 'cross_cutting': False

{pipulate-2.41 → pipulate-2.43/pipulate.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: pipulate
-Version: 2.41
+Version: 2.43
 Summary: AI-readiness for the agentic web — local-first, Nix-reproducible workflows. The successor to AI SEO software.
 Author-email: Mike Levin <pipulate@gmail.com>
 License-Expression: AGPL-3.0-or-later
@@ -108,6 +108,39 @@ cd ~/pipulate
 nix develop
 ```
 
+<!-- DO NOT MOVE THIS BLOCK ABOVE "## Quick Start". Two splicers own
+     parts of this file, with two different boundary schemes:
+       1. release.py run_waxascii_release_stamp() -- HEADER-BOUNDED.
+          It finds the "I HEREBY WILL NOT RE-GENERATE" line near the
+          top and replaces EVERYTHING between the "# Pipulate:" header
+          and the next header with the sealed white_rabbit art. Runs on
+          every `release`. Anything inside that region is destroyed.
+       2. prompt_foo.py update_readme_md_in_place() -- SENTINEL-BOUNDED,
+          the two HTML comments below. Runs on every compile, refuses on
+          CRC drift, writes only when the bytes change.
+     The sentinels below are safe ONLY because they sit after
+     "## Quick Start", outside splicer 1's blast radius. Verified from
+     line numbers, not from a release run. -->
+### Where your work lives
+<!-- --- START WORKSPACE TREE --- -->
+```text
+   Notebooks/  — the JupyterLab root (NOT Pipulate's own root)
+   │            FLAT siblings. Nothing nests. Nothing to get wrong.
+   │
+   ├── Advanced_Notebooks/     canon · flake-delivered, copy-if-absent
+   ├── Educational_Notebooks/  canon · your edits survive, updates do not arrive
+   ├── imports/                canon · the code-behind "sauce" modules
+   │
+   ├── Playground/             personal · gitignored · your own git repo goes here
+   ├── Client_Work/            personal · gitignored · never leaves this machine
+   ├── Deliverables/           personal · gitignored
+   │
+   └── Shared/                 the ONE folder for handing work to a teammate
+       ├── alice/              one folder per person; you write ONLY your own
+       └── bob/                single-writer partitions = zero merge conflicts
+```
+<!-- --- END WORKSPACE TREE --- -->
+
 ## 💡 What Can You Actually Build?
 
 **Real examples of what people create with Pipulate:**

{pipulate-2.41 → pipulate-2.43}/pyproject.toml

@@ -5,7 +5,7 @@ build-backend = "setuptools.build_meta"
 [project]
 name = "pipulate"
 # VERSION NOTE: Synced from pipulate/__init__.py.__version__ via python version_sync.py
-version = "2.41"
+version = "2.43"
 authors = [
   { name="Mike Levin", email="pipulate@gmail.com" },
 ]

{pipulate-2.41 → pipulate-2.43}/tools/scraper_tools.py

@@ -154,7 +154,7 @@ def _simplify_html_for_llm(html_content, default_title=""):
 # selenium_automation. Nothing raised; ruff passed; the registry was simply
 # wrong. DECORATOR STRADDLE RULE: decorators bind downward, so any insertion
 # anchored on a def must include the line above it in the SEARCH.
-def _document_candidates(cdp_events: list, domain: str) -> list:
+def _document_candidates(cdp_events: list, domain: str, final_url: str = "") -> list:
     """Document responseReceived events that plausibly ARE the requested page.
 
     Returned in ledger order; the caller takes [-1]. Pure and ledger-only on
@@ -173,6 +173,33 @@ def _document_candidates(cdp_events: list, domain: str) -> list:
         if ev.get("method") == "Network.responseReceived"
         and ev.get("params", {}).get("type") == "Document"
     ]
+    # THE SAME-ORIGIN IFRAME DEFEAT (convicted 2026-08-04). The host-exact
+    # filter below was hardened on 2026-07-24 against THIRD-PARTY frames that
+    # carry the target host in a query parameter. It is structurally blind to a
+    # SAME-ORIGIN frame: a Shop Pay buyer-recognition callback served from the
+    # storefront's own host passes host-exactness BY DEFINITION, fires late,
+    # and the caller then takes [-1] -- the LAST Document, which is the iframe.
+    # The frame tiebreaker below is only a tiebreaker, and it is permitted to
+    # no-op, so nothing downstream can tell a witnessed choice from a guess.
+    # ANCHOR ON A VALUE THE BROWSER AUTHORED, NOT ON AN INFERENCE. final_url is
+    # driver.current_url, read before this selection runs. A sub-frame URL is
+    # NEVER the browser's current URL, so an exact match cannot be a frame --
+    # which makes this correct regardless of which inferential step below was
+    # the one that broke.
+    # PURITY PRESERVED, deliberately: the caller passes final_url IN, no live
+    # CDP call appears here, and the whole selection is still replayable
+    # offline over any cached network_log.jsonl -- which is what makes the
+    # straddle for this very patch cost zero browser flights.
+    # FAILS OPEN: no exact match degrades to the host+frame path unchanged, so
+    # the worst case equals the behaviour shipped before this block existed.
+    if final_url:
+        target = final_url.split("#", 1)[0]
+        exact = [
+            ev for ev in docs
+            if ev.get("params", {}).get("response", {}).get("url", "").split("#", 1)[0] == target
+        ]
+        if exact:
+            return exact
     want = _norm(domain)
     on_host = [
         ev for ev in docs
@@ -722,7 +749,7 @@ async def _selenium_capture(params: dict, checkpoint=None) -> dict:
             # Redirect chains do not threaten it either way; CDP surfaces those
             # as requestWillBeSent with redirectResponse, not as extra
             # responseReceived events.
-            doc_events = _document_candidates(cdp_events, domain)
+            doc_events = _document_candidates(cdp_events, domain, final_url)
             if doc_events:
                 doc_params = doc_events[-1]["params"]
                 # The subject of the headers on the very next line. Captured
@@ -777,6 +804,22 @@ async def _selenium_capture(params: dict, checkpoint=None) -> dict:
             # artifact that does not record its own subject cannot be audited
             # against the ledger sitting next to it.
             "header_source_url": doc_url,
+            # WHICH RULE CHOSE IT. header_source_url (2026-07-24) records the
+            # SUBJECT of these headers; this records HOW that subject was
+            # picked. The 2026-08-04 conviction cost two turns precisely
+            # because the artifact could name its subject but not its
+            # selection path. "final_url_exact" means the browser's own
+            # current URL matched a Document response; "host_fallback" means
+            # the selector guessed from host and frame order and the result
+            # did NOT match the final URL -- treat the whole triptych as
+            # suspect on that value; "none" means no Document was selected at
+            # all. One jq, not a two-turn investigation.
+            "header_selection": (
+                "none" if not doc_url
+                else "final_url_exact"
+                if final_url and doc_url.split("#", 1)[0] == final_url.split("#", 1)[0]
+                else "host_fallback"
+            ),
             # Consumers read this to decide whether source.html may be trusted
             # as the LEFT PANEL of the triptych. Absent on captures taken
             # before 2026-07-24, which consumers therefore treat as UNFLAGGED,