[ROADMAP][NORTH STAR] PatchPitch Full Release Kit — input → platform copy, video, GIF, ZIP (R0–R6)

Open
#63 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Active
Tech stack
python
Domain
tooling

Research direction

Start by reading the linked roadmap issues, especially #48 for the Fact Pack v2 contract and #45 for the current release handoff; the payload names no implementation files or tests. The roadmap spans multiple adapters, review flows, publishing handoffs, and outcome receipts, so first identify which dependency is ready and its acceptance criteria. Done means completing the ordered, owner-approved experiment without duplicating existing issues or building the excluded platform components.

Written by the indexing model from the issue text.

Description

documentation

North Star — FULL RELEASE KIT (owner decision, 21 October 2026)

Give PatchPitch any combination of (A) GitHub URL, (B) screenshots/real video clips, (C) a release description. It produces a coherent, editable, verifiable COMPLETE PUBLICATION PACK: platform-native posts/articles with correct tags, GitHub Release Notes, video/GIF scripts, real rendered MP4, real generated GIF loops, captions/ALT/approved artwork, and an offline ZIP with files and provenance.

The practical promise is input once → review facts → choose platforms/Quillgrain voice → generate all applicable content/media → review → Download Full Kit. Users should not have to copy the same release facts into separate products. PatchPitch remains a small LOCAL-FIRST, free/self-hostable product with explicit human verification; content generation does not equal automatic posting.

Baseline verified 2026-10-21

Public repo: https://github.com/drevendev/PatchPitch . Current checked main c30d213, after PR #72 added explicit Save/Open session/profile, local bounded Git diff → reviewed fact candidates → DevLog, manual published-head marker and fixed important source-preservation issues. Existing 0.2 features include local Ollama/Gemma X Single/Thread, source-selected facts, editor/export, documented real Gemma runs, opt-in Sentry and a recorded static Pages demo.

P0 CI regression exists: main run 39588939745 has 245 passed / 1 failed in a Playwright test's unsafe-eval-based wait under strict CSP; #74 contains an exact minimal fix and acceptance. The prior local 246 passing tests are NOT green CI for this merge. No v0.2 GitHub Release was found; the historical Pages video remains a recording, not an interactive hosted inference service.

Existing developer-only media: scripts/capture_demo.py records the specifically scripted original product UI; scripts/render_video.py hard-codes one 63-second historical scene/narration plan; scripts/build_sample.py creates a static sample. They are reusable components, NOT an owner-operable arbitrary release video/GIF generator. No product screenshot importer or universal GitHub URL importer exists yet.

Planned releases (provisional versions, not promised dates)

R0 — 0.2.x HARDEN & SHIP CURRENT VALUE · P0

Value: existing X/local DevLog tool is stable and the owner can really run, preview and copy an actual release text.

  • #74 RED CI BLOCKER, no CSP weakening.
  • #45 release/owner-gated Pages handoff; #38 real X preview; #35 X composer code already implemented.
  • #8 local Git import and #11 local Save/Open implemented in #72: VERIFY exact merged code and acceptance after fixing CI, do not restart development.
  • #46, #47, #65–#68 track source/context/media QA from #72; resolve receipts individually rather than bulk-close on promises.
    Exit: clean exact-head CI, one genuine local model/user run, owner preview in real X, accepted review state. Release/tag and public Pages deploy require separate explicit owner authorization.
R1 — 0.3 SOURCE STUDIO · P0

Value: GitHub link OR screenshots OR text OR mixture becomes one safe, editable reviewed evidence/fact pack.

  • #75 unified Campaign Intake — single UI/workspace and explicit source-review state.
  • #76 public GitHub URL — reuse #8 local diff core; exact public tag/commit/compare, no code execution.
  • #87 private GitHub URL — conditional v0.3.x read-only via explicitly configured local credentials; no token or private corpus in public exports. Existing local checkout path already works without this addition.
  • #77 screenshot/clip importer — file selection, metadata, review, privacy/rights; screenshot observations are NOT proof of product behavior.
  • #48 Fact Pack v2 — correct distinction DRAFT/PR/MERGED/VERIFIED/TAGGED/PUBLISHED, timestamps, visibility, source hashes, owner public clearance.
  • #50 Quillgrain + #31 — consume existing pack compiler, permission/host/digest checks and measured real style; Common as default, private Dreven pack stays CANDIDATE/unvalidated until accepted.
  • #51 media rights/asset manifest basic import and ownership/safe ALT.
    Exit: from one actual public GitHub URL + screenshots + a plain note generate and export an evidence-grounded X post; screenshot-only truth limits and missing media are surfaced; local session Save/Open works.
R2 — 0.4 COPY FACTORY · P0

Value: one reviewed source pack produces independent platform-native social text, tags and GitHub Release Notes.

R3 — 0.5 STORYBOARD & MP4 · P0

Value: complete editable video/GIF shot-list and script, then actual local MP4 (not a promised future video).

  • #79 Storyboard — sources → 30–60s script, scene IDs, durations, captions, media choices, narration, fact IDs, scene type and author approval; recommend GIF candidate moments.
  • #7 general local video renderer — refactor existing Playwright/FFmpeg/Kokoro tools out of the fixed 63-second patch-specific script into a general reviewed scene-plan renderer with progress/errors and verified output.
  • #9 approved MP4/WebM clips — trim real footage, synchronize with screenshots and captions; #10 capture vs synthetic motion research only.
    Exit: one owner-reviewable MP4 with real decoded frames, readable captions, correct CTA, inspected rights/hashes; mixed screenshots are described as illustrative, never mislabeled as observed app interaction. If footage missing, a labelled screenshot explainer is possible, not a fake gameplay demo.
R4 — 0.6 GIF & MEDIA VARIANTS · P0

Value: generate actual GIF loops, alternative MP4s and platform-appropriate video profiles from the approved story.

  • #80 GIF maker — local FFmpeg-based short-loop GIF, actual size/frame checks, fallback short MP4.
  • #81 media profiles/captions — landscape/vertical/square, safe zones, captions and verified playback/codec.
  • #83 real app capture — optional P2 trusted browser action recording for owner-controlled pages; uploaded clip path remains first-class so automated capture doesn't block media delivery.
  • #51 media approval/rights.
    Exit: one reviewed real-motion GIF and one illustrative screenshot loop correctly labelled, playable MP4 fallback, at least two properly framed video variants; no invented UI actions.
R5 — 0.7 FULL RELEASE KIT · P0

Value: one intentional Generate Full Kit operation after fact review → all applicable actual media and text files, then a single verified publication ZIP.

  • #85 local resumable job graph — source/facts → channels → storyboard → video → GIF → packaging; selective regeneration, stable hashes, progress/cancel/resume and no loss of human edits.
  • #86 verified publication ZIP — all applicable copy/, video/, gif/, media/, captions, tags, credits, scripts, source manifest, checksums and offline preview, plus honest READY / PARTIAL / BLOCKED statuses.
  • #54 portable reviewed agent handoff — to existing Starforge/authorized publisher without publication authorization, #55 actual owner dogfood across games+OSS, #56 manual publication receipts/feedback. Existing #18 external tester validation after owner case.
    Exit: owner starts with a public GitHub URL + 2 approved screenshots + release description, then from another game release+real clip; reviews facts and scenes, runs full local generation, receives editable native copy + actual MP4 + actual GIF(s) + source/rights-provenance ZIP; independent ZIP extract/hash/media smoke, owner approves. Missing source material yields explicit PARTIAL/NEEDS_SOURCE, never invented output.
R6 — 1.0 POLISH / ADOPTION · conditional, not a dependency for full kit
  • #40 zero-cost hosted interactive demo only after real no-card/no-paid entitlement + privacy/rate gates; does not replace local media tooling.
  • #34 headless compose/provider abstraction optional opt-in local-first CLI and separate publisher integration.
  • #36 Feedback Summary and #37 Answer Drafts are adjacent features, not blockers for the full release pack.
  • Specialized source adapters (#57 Devostasis, #58 HungryCrab, #59 TradeSim, #60 Lanterra, #61 Scriptorium, #62 creative) remain optional after one common pipeline works.
  • Sentry, external users, setup diagnostics, adoption experiment only with actual observations; no invented reach or payments.

One target UX

New Campaign → choose any 1–3 inputs: GitHub URL / screenshots + clips / description → Review Facts (source ID + release status + privacy) → Brand & Quillgrain → Destinations + Tags → Generate Drafts → Review Storyboard → Render Video / GIFs → Review All → Download Publication Pack.

"Generate all" does not bypass source approval, model errors, media rights or final human review. Browser/local inference and FFmpeg resources must be real on the user's machine. The product remains useful if users select only text outputs. It is not an account-manager, social scraper or auto-posting bot.

Safety / honesty constraints

  • Input GitHub public links require explicit pinned scope, no executing repo code or arbitrary redirects; private sources never auto-exported publicly. Existing local Git importer is reused, not reinvented.
  • Screenshots may show UI but cannot verify an unseen behavior. Real application footage vs illustrative slideshow/animated screenshots are visibly distinguished in every asset/manifest. With no footage, local rendering may create a labelled TEXT_EXPLAINER from approved copy, not a fake gameplay demo.
  • Quillgrain supplies stylistic instructions not facts; private author corpus is CANDIDATE and may only go to an explicitly authorized offline host, not a public Cloudflare demo.
  • All rights/credits/music and image uses must be owner-approved. No invented viewer, benchmark, feature availability, game art authorship or demo interaction.
  • No paid services, card requirements, mandatory cloud API, automatic posts, account changes, or modifying game/agent repositories as a side effect of preparing a pack.
  • Each issue describes exact implementation and test artifacts. Real generated MP4/GIF/model answers and owner accepted/published statuses are separate evidence from mock-only green tests.
  • Version numbers in this issue are planning batches, not existing GitHub tags, released builds, exact timelines or permission to deploy.

How to measure product value

Measure owner time from input to publishable kit, number of manual fixes by kind, source errors found, number of completed media files, actual copies used/publications/feedback where observed. A finished pack is useful only when owner can open its MP4, view its GIF and paste its platform text. User attention, stars, and revenue stay UNKNOWN until directly observed.

First action: resolve red CI #74 and owner 0.2 publication gate #45. Next coding: #75/#76/#77/#48/#50, with #87 private URL access only after the public route is working. Video tooling (#79/#7/#9) is elevated from old P3 precisely because the owner states media generation is a central goal.

Relation to earlier portfolio synergy roadmap

The previous framing (21 Oct) focused on source adapters for Owned games/OSS, Quillgrain, BeautifulRepo, DigitalFrontier, release receipts and operator handoffs. Those concrete issues are preserved: #48–#62. They now feed this full-product pipeline. Do not treat the previous suggested P2/P3 placement of video and GIF features as current priority; they are core in R3/R4.

Dominant language
Python
Stars
1
Forks
0
Avg merge
1h 56m
Merged PRs (30d)
7

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from drevendev/PatchPitch

All issues in drevendev/PatchPitch

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.