linersh 0.5.5 → 0.5.7

package/cli-update-docs/AI-HANDOFF.md

@@ -1,28 +1,71 @@
 # Liner AI Handoff
 
-Last updated: 2026-05-31
+Last updated: 2026-06-01
 
-This handoff summarizes the current Liner state after the 0.5.5 TUI/testing pass. It is intended for any AI agent continuing the work without the full chat history.
+This handoff summarizes the current Liner state after the 0.5.6 TUI/core release,
+marketing-site launch-prep pass, and 0.5.7 PDF-download hotfix prep. It
+is intended for any AI agent continuing the work without the full chat history.
 
 ## Current Product State
 
-- `linersh@0.5.5` is the active TUI release candidate.
-- The Python core source is now versioned `0.5.5`; publish matching `linersh-*@0.5.5` platform packages before publishing `linersh@0.5.5`.
+- `linersh@0.5.6` is published on npm and promoted to `latest`.
+- The published Python core/platform packages are `0.5.6`; matching
+  `linersh-*@0.5.6` platform packages are published on npm and promoted to
+  `latest`.
+- The repo is prepared for `0.5.7` (`pyproject.toml`, `src/liner/__init__.py`,
+  and `packages/tui/package.json`). It needs rebuilt platform packages because
+  the Python core changed.
 - Platform packages are available for macOS arm64/x64, Linux arm64/x64, and Windows x64.
 - The TUI is installed/tested locally from the packed tarball in `/tmp/liner-playwright-test`.
 - The main tested mixtape is `staff-design-engenieer` (typo preserved in the folder name).
+- Clean npm smoke passed with `npx linersh@latest --version`: `liner 0.5.6 (tui)  ·  0.5.6 (core)`.
 
 ## Important Local Paths
 
-- Repo/worktree: `/Users/arturo/.codex/worktrees/44f8/liner`
+- Active repo/worktree for this thread: `/Users/arturo/.codex/worktrees/7117/liner`
+- Previous v0.5.5 implementation worktree: `/Users/arturo/.codex/worktrees/44f8/liner`
 - Original Liner project folder: `/Users/arturo/Documents/Projects/Youtube Grabber/liner`
 - Original mixtapes folder: `/Users/arturo/Documents/Projects/Youtube Grabber/liner/mixtapes`
 - CMD-UX copied mixtapes folder: `/Users/arturo/Documents/Projects/CMD-UX/Case Studies/mixtapes`
 - Local TUI test install: `/tmp/liner-playwright-test`
+- 0.5.5 release artifacts: `/tmp/liner-release-artifacts-0.5.5`
+- 0.5.6 release artifacts: `/tmp/liner-release-artifacts-0.5.6`
+- 0.5.7 release artifacts: `/tmp/liner-release-artifacts-0.5.7`
 - Tested mixtape now moved back to: `/Users/arturo/Documents/Projects/Youtube Grabber/liner/mixtapes/staff-design-engenieer`
 
 ## What Was Fixed In This Pass
 
+0.5.7 PDF-download hotfix:
+
+- `.pdf` sources that first hit a JavaScript or bot-detection stub and then
+  fall back to Playwright can make Chromium report `Page.goto: Download is
+  starting`. Liner now captures that Playwright download and extracts it
+  through the shared PDF helper.
+- Verified against the failing resume mixtape PDFs:
+  - `TheLadders-EyeTracking-StudyC2.pdf?type=standard` -> 4,095 chars.
+  - `Formula-for-a-Winning-Resume.pdf` -> 7,208 chars.
+- Full `staff-designer-resume-crafter` compile with `--no-cache` now reaches
+  `22/24 usable sources`; the remaining failures are PAIR cookie-consent-only
+  output and a Microsoft HAX network timeout.
+
+0.5.6 source-extraction hardening:
+
+- Remote web PDFs are detected before HTML extraction and extracted through the
+  shared PDF helper. This prevents raw `%PDF-` bytes from entering generated
+  source Markdown.
+- Bad web cache entries are purged and refetched when they contain raw PDF
+  bytes, stale PDF URL fallbacks, tiny soft/playwright fallback bodies, or
+  cookie-consent-only text.
+- Server HTML that looks like an empty client-side app shell now raises
+  `JsRenderingRequired`, so existing auto-fallback can try Playwright.
+- Cookie-consent-only output is rejected as unusable, including after Playwright
+  rendering. This is intentionally an honest failure, not an automatic
+  cookie-clicker.
+- Partial compile output now says how many source files are usable versus
+  unavailable placeholders.
+
+0.5.5 TUI/core release:
+
 - Skill bundle resolution for npm installs:
   - TUI now resolves the bundled `cli-update-docs/SKILL.md` reliably from the installed package.
   - `LINER_SKILL_PATH` can point either at the skill directory or at `SKILL.md`.
@@ -57,10 +100,15 @@ This handoff summarizes the current Liner state after the 0.5.5 TUI/testing pass
 
 ```sh
 cd /tmp/liner-playwright-test
-LINER_BIN=/Users/arturo/.codex/worktrees/44f8/liner/.venv/bin/liner ./node_modules/.bin/liner
+LINER_BIN=/Users/arturo/.codex/worktrees/7117/liner/.venv/bin/liner ./node_modules/.bin/liner
 ```
 
 - Running `./node_modules/.bin/liner` without `LINER_BIN` uses the bundled platform binary, which may not include local Python source edits until platform packages are rebuilt.
+- If Python source changed, publishing only the main `linersh` package is not
+  enough. Rebuild and publish all platform packages at the same version first.
+- Cookie-banner auto-dismissal is not implemented in 0.5.6. The safety net is
+  to reject cookie-only output; a future dismissal pass should keep that final
+  rejection in place.
 - The TUI package generated `packages/tui/cli-update-docs/` during `prepack`; the canonical docs live at repo-root `cli-update-docs/`.
 - The old root `docs/` folder was removed. `LINER-MASTER.md` now lives at `cli-update-docs/LINER-MASTER.md`.
 - The Jhey source URL currently 404s on the live site. The useful archived version is:
@@ -74,7 +122,7 @@ https://web.archive.org/web/20250408204038id_/https://jhey.dev/cheep/rotating-ga
 TUI package:
 
 ```sh
-cd /Users/arturo/.codex/worktrees/44f8/liner/packages/tui
+cd /Users/arturo/.codex/worktrees/7117/liner/packages/tui
 npm run typecheck
 npm run build
 npm test
@@ -84,11 +132,44 @@ npm pack --json
 Python suite:
 
 ```sh
-cd /Users/arturo/.codex/worktrees/44f8/liner
+cd /Users/arturo/.codex/worktrees/7117/liner
 uv run --extra dev pytest
 ```
 
-Result from the latest full Python run in this pass: `179 passed, 1 skipped, 1 deselected`.
+Result from the latest full Python run in this pass: `190 passed, 1 deselected`.
+
+Release-prep verification:
+
+```sh
+cd /Users/arturo/.codex/worktrees/7117/liner/packages/tui
+npm ci
+npm run typecheck
+npm test
+npm run build
+npm pack --dry-run
+
+cd /Users/arturo/.codex/worktrees/7117/liner
+python3 -m compileall -q src/liner
+uv run --extra dev pytest
+```
+
+Results: TUI `92 passed`; Python `179 passed, 1 skipped, 1 deselected`.
+
+Platform artifact workflow:
+
+```text
+Status: latest post-release-prep run is green; check `gh run list --workflow platform-bundles.yml --limit 3` if you need the current run ID.
+Artifacts downloaded to: /tmp/liner-release-artifacts-0.5.5
+Local npm bundle smoke: liner 0.5.5 (tui)  ·  0.5.5 (core)
+```
+
+npm release smoke:
+
+```sh
+rm -rf ~/.npm/_npx
+npx linersh@latest --version
+# liner 0.5.5 (tui)  ·  0.5.5 (core)
+```
 
 ## Useful Test Commands
 
@@ -96,29 +177,29 @@ Install the local TUI tarball into the scratch project:
 
 ```sh
 cd /tmp/liner-playwright-test
-npm install /Users/arturo/.codex/worktrees/44f8/liner/packages/tui/linersh-0.5.5.tgz
+npm install /tmp/liner-release-artifacts-0.5.5/linersh-darwin-arm64/linersh-darwin-arm64-0.5.5.tgz /tmp/liner-release-artifacts-0.5.5/linersh-tui/linersh-0.5.5.tgz
 ```
 
 Run the TUI against the local Python core:
 
 ```sh
 cd /tmp/liner-playwright-test
-LINER_BIN=/Users/arturo/.codex/worktrees/44f8/liner/.venv/bin/liner ./node_modules/.bin/liner
+LINER_BIN=/Users/arturo/.codex/worktrees/7117/liner/.venv/bin/liner ./node_modules/.bin/liner
 ```
 
 Force a fresh compile/fetch:
 
 ```sh
 cd /tmp/liner-playwright-test
-LINER_BIN=/Users/arturo/.codex/worktrees/44f8/liner/.venv/bin/liner ./node_modules/.bin/liner cache clear --yes
-LINER_BIN=/Users/arturo/.codex/worktrees/44f8/liner/.venv/bin/liner ./node_modules/.bin/liner
+LINER_BIN=/Users/arturo/.codex/worktrees/7117/liner/.venv/bin/liner ./node_modules/.bin/liner cache clear --yes
+LINER_BIN=/Users/arturo/.codex/worktrees/7117/liner/.venv/bin/liner ./node_modules/.bin/liner
 ```
 
 Run JS setup explicitly:
 
 ```sh
 cd /tmp/liner-playwright-test
-LINER_BIN=/Users/arturo/.codex/worktrees/44f8/liner/.venv/bin/liner ./node_modules/.bin/liner setup-js --yes
+LINER_BIN=/Users/arturo/.codex/worktrees/7117/liner/.venv/bin/liner ./node_modules/.bin/liner setup-js --yes
 ```
 
 Clean local state for reinstall testing:
@@ -147,8 +228,14 @@ Package-specific docs still live in `packages/tui/`:
 
 ## Suggested Next Work
 
-- Publish/promote `linersh@0.5.5` once final smoke testing passes.
-- Rebuild/publish all platform packages for `0.5.5`, then publish/promote `linersh@0.5.5`.
+- Deploy the marketing site from `marketing/site` once DNS/Vercel details are ready.
+- Update the public website docs and changelog for 0.5.7 after the release
+  artifacts are ready.
+- Consider a conservative Playwright cookie-banner dismissal pass for common,
+  low-risk labels, while still rejecting cookie-only output if dismissal fails.
+- Consider surfacing extraction mode/body length in the TUI compile details.
+- Consider adding `liner doctor-source <url>` or equivalent single-source
+  diagnostics.
 - Consider adding Wayback as an automatic fetcher tier between Playwright and agent-summary fallback.
 - Add per-source failure actions in CompileView: open URL, drop source, retry one source.
 - Add a regression test for completed Compile opening existing results rather than running `streamCompile`.

package/cli-update-docs/LINER-MASTER.md

@@ -524,7 +524,7 @@ Liner's methodology exists to catch these before compile.
 
 ## Project Status
 
-As of v0.5.5 (published on npm `latest`):
+As of v0.5.5:
 
 - The Python CLI is functional.
 - The TypeScript/Ink TUI is functional. The empirical-test phase has been removed from the driven flow — compilation is now the completion milestone (*compiled = complete*). The hub is a single summary view (status box + always-visible phase checklist), import auto-detects `.mixtape` files in the current folder, and completed/partial compiles open the existing compile result instead of rerunning by default.

package/cli-update-docs/README.md

@@ -26,13 +26,15 @@ The split is deliberate. Every invocation pulls SKILL.md's ~2,300 words into con
 
 ## Where the bundle lives
 
-**Local testing.** Drop the `curating-mixtapes/` folder into `~/.claude/skills/`. Claude Code and Claude Desktop both look there for user-installed skills. The skill fires when the user says something the description matches — "help me make a mixtape on [topic]" is the canonical trigger.
+**Local testing.** Drop this directory into `~/.claude/skills/curating-mixtapes/`. Claude Code and Claude Desktop both look there for user-installed skills. The skill fires when the user says something the description matches — "help me make a mixtape on [topic]" is the canonical trigger.
 
-**Shipping.** The bundle lives at `liner/skills/curating-mixtapes/` in the main Liner repository. End users install it from there (installation flow TBD — likely a `liner skills install` command or a documented copy step in the Liner README).
+**Shipping.** The canonical bundle lives at repo-root `cli-update-docs/`. The TUI copies this directory into `packages/tui/cli-update-docs/` during `prepack` and ships it inside the `linersh` npm package, so end users do not need a separate skill install for TUI-driven agent phases.
 
-**TUI subprocess.** The Liner TUI bundles the skill internally and invokes it via the Claude Agent SDK in quick mode. The user doesn't see the skill directly; they see the TUI's wizard UI. The methodology being applied is this skill's.
+**Direct skill use.** A documented copy/install flow for using the skill outside the TUI is still planned. Until then, direct local use is a developer workflow.
 
-The same file contents work in all three locations. Don't fork between a local-test version and a ship version.
+**TUI subprocess.** The Liner TUI bundles the skill internally and invokes it via the local Claude or Codex CLI in quick mode. The user doesn't see the skill directly; they see the TUI's wizard UI. The methodology being applied is this skill's.
+
+The same file contents work in every location. Don't fork between a local-test version and the package-shipped version.
 
 ## Runtime requirements
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "linersh",
-  "version": "0.5.5",
+  "version": "0.5.7",
   "description": "Liner — interactive tape editor for building curated mixtapes (AI-consumable context bundles).",
   "type": "module",
   "license": "MIT",
@@ -36,11 +36,11 @@
     "yaml": "^2.6.1"
   },
   "optionalDependencies": {
-    "linersh-darwin-arm64": "0.5.5",
-    "linersh-darwin-x64": "0.5.5",
-    "linersh-linux-arm64": "0.5.5",
-    "linersh-linux-x64": "0.5.5",
-    "linersh-win32-x64": "0.5.5"
+    "linersh-darwin-arm64": "0.5.7",
+    "linersh-darwin-x64": "0.5.7",
+    "linersh-linux-arm64": "0.5.7",
+    "linersh-linux-x64": "0.5.7",
+    "linersh-win32-x64": "0.5.7"
   },
   "devDependencies": {
     "@types/node": "^22.10.0",