Session Handoff — Why Dachshunds: script CTA/opener standard fixed, topics 1-6 made (both formats), download in progress

Where it started

Session opened with /prime, then a pasted Batch-7 handoff (briefing only). User asked to build an HTML review of the new topics 1-10 scripts, then gave hard feedback that became channel standards, then had topics 1-6 produced in Agent Opus (create-only) and is now downloading them.

Decisions locked + what shipped

• Two new channel-wide script standards (user was emphatic, both kept getting dropped): (1) NEVER open on the stock phrase "surprisingly scientific reason" — rotate it; (2) every LONG-FORM must end with the FULL CTA stack (topic-specific COMMENT question + LIKE + SHARE + SUBSCRIBE), worded fresh. Shorts stay comment+follow only (cross-post to Reels/TikTok). Locked in c:\Users\srver\AIOS-Workspace\aios-starter-kit\PROJECTS\YT - Why Dachshunds Channel\Scripts\LONG-FORM-script-formula.md (new; there was only a shorts formula before) + memory.
• Rewrote all 10 long-form scripts — c:\Users\srver\AIOS-Workspace\aios-starter-kit\PROJECTS\YT - Why Dachshunds Channel\new-scripts-longform-2026-07-07.md (varied openers, full CTA, em-dashes removed, thinned "studies on dog behavior show"). Shorts file was already compliant — untouched.
• HTML review page — c:\Users\srver\AIOS-Workspace\aios-starter-kit\PROJECTS\YT - Why Dachshunds Channel\scripts-review-topics-1-10-2026-07-07.html (both formats side by side; opened in Edge; reflects the rewrite).
• Synced prompt SCRIPT blocks for topics 1-6 ONLY in c:\Users\srver\AIOS-Workspace\aios-starter-kit\PROJECTS\YT - Why Dachshunds Channel\new-prompts-batch-2026-07-07.md. Topics 7-10 still have OLD scripts ("scientific reason") — MUST sync before making them.
• Made topics 1-6 in Agent Opus, create-only (6 long-form + 6 shorts = 12 sessions). Never confirmed by Claude; user confirms/renders in UI. All 12 verified FINISHED via download collect-only.
• Added --prompts / --scripts flags to scripts\dachshund\make_fresh_longform.py and make_fresh_shorts.py; both defaults now point at the 07-07 batch files (were hardcoded to 07-06).
• Tracker updated in place — Why_Dachshunds_MASTER_Tracker_v24.xlsx, sheet "Master Tracker": rows #269-274 got Video ID(s) = LF16:9 <id>; Short9:16 <id> and Created in Agent Opus? = Y.

Session ID map (tracker # / topic / long-form / short)

• #269 Leans against you — LF 07071445-nlu / Short 07071453-8wm
• #270 Waits at the door — LF 07071445-jm1 / Short 07071453-2en
• #271 Half off the couch — LF 07071445-uwy / Short 07071453-8fl
• #272 Launches when excited — LF 07071445-gr7 / Short 07071453-x7z
• #273 Won't cross floors — LF 07071445-ysp / Short 07071453-196
• #274 Won't eat until home — LF 07071505-2ov / Short 07071507-p23

Key files for next session

• c:\Users\srver\AIOS-Workspace\aios-starter-kit\scripts\dachshund\file_fresh_batch.py — files _staging → Batch 7 by tracker Video ID(s). dest_dir_for() sends #>=260 to EVERGREEN. For a new Batch 8, BASE (line 24) must change. Run --dry-run first.
• c:\Users\srver\AIOS-Workspace\aios-starter-kit\PROJECTS\YT - Why Dachshunds Channel\new-prompts-batch-2026-07-07.md — topics 7-10 SCRIPT blocks still need syncing to new-scripts-longform-2026-07-07.md.
• c:\Users\srver\AIOS-Workspace\aios-starter-kit\scripts\dachshund\make_fresh_longform.py / make_fresh_shorts.py — runners; --numbers N create-only.
• c:\Users\srver\AIOS-Workspace\aios-starter-kit\scripts\agent_opus_download.py — --search "Dachshund" --days 1, NEVER --all.
• Plan file: none.
• Memory files touched: C:\Users\srver\.claude\projects\c--Users-srver-AIOS-Workspace-aios-starter-kit\memory\feedback_why_dachshunds_script_standards.md (new) + MEMORY.md (pointer).

Running state

• Background processes: shell bhyr6o5rh — the download (agent_opus_download.py --search "Dachshund" --days 1 --dest ".../Batch 7 - Fresh 2026-07-06/_staging"). At handoff: 16/19 files in _staging, still running. Kill via TaskStop bhyr6o5rh if needed; otherwise let it finish.
• Dev servers / ports: none.
• Open worktrees / branches: none.

Verification — how to confirm things still work

• ls "D:/Videos/000-YT Why Dachshunds/Batch 7 - Fresh 2026-07-06/_staging/" | wc -l — expect ~19 when download done.
• grep -ci "scientific reason" "PROJECTS/YT - Why Dachshunds Channel/new-scripts-longform-2026-07-07.md" — expect 1 (header meta line only).
• python scripts/dachshund/file_fresh_batch.py --dry-run — shows which staged files map to #269-274 and their dest (EVERGREEN). Moves nothing.
• Agent Opus token was valid this session. If a later call 401s: python scripts/agent_opus_refresh_token.py --login.

Deferred + open questions

• Open (BLOCKS final filing): folder home for #269-278 — filer defaults them to Batch 7 / EVERGREEN; user asked twice about a new Batch 8, never answered. Decide before the real file_fresh_batch.py run.
• Open: does user want a bare "like" ask added to SHORTS (currently comment+follow only)? Offered, unanswered.
• Deferred: topics 7-10 not made — sync their prompt SCRIPT blocks first, then create-only.
• Deferred: topics 11-30 in new-topics-batch-2026-07-07.md still need scripts/prompts.
• Dropped mid-session: user asked what the 2-min videos cost in credits "yesterday" — search was interrupted, never answered. (~4,600 credits balance per prior handoff.)

Pick up here

When download bhyr6o5rh finishes (~19 files in _staging), run python scripts/dachshund/file_fresh_batch.py --dry-run, get the user's Batch 7-EVERGREEN-vs-Batch 8 answer, then run it for real to file #269-274.