Spaces:
Sleeping
Sleeping
Commit History
-
Clarify API-key field accepts Parley keys
Claude +1: Claude Opus 4.8The key input already accepts either an Anthropic (sk-ant-…) or MIT Parley (sk-parley-…) key — routing is by prefix, and the only client check is non-empty. The placeholder said "sk-ant-…", making it look Anthropic-only. Update the label and placeholder on both the video and images pages, and note the Parley auto-routing. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01EM8jiYxdVFy1w3LeJ9GBJg327be13
-
Add AI slide-to-transcript alignment for untimestamped images
Claude +1: Claude Opus 4.8When the images-input mode gets a transcript but the slide filenames carry no HH-MM-SS timestamps, place each slide on the timeline by content instead of failing. Locally OCR each slide (Tesseract) and ask Claude when the narration first discusses it, yielding real per-slide start times. Falls back to an even split across the transcript span when there's no API key or alignment fails. - image_input.py: add all_have_timestamps, order_by_name, build_frames_from_starts, build_frames_even_split (clamped, ordered). - llm_extract.py: add align_slides_to_transcript + SlideAlignError (text-based, so it works through Anthropic-compatible proxies). - /jobs/from-images: three-way timeline branch (order-only / timestamp-anchored / AI-aligned) run off the event loop. - Update images.html hint, README to note timestamps are now optional. - Tests for the new helpers and alignment cleanup. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01…e646192 -
feat: images mode without a transcript needs no HH-MM-SS filenames
ClaudeWhen no transcript is uploaded there's no narration to align, so slide timestamps are pointless. Names now only matter when a transcript is present: * With a transcript: filenames must carry HH-MM-SS (unchanged) so narration lines up by time. * Without a transcript: build_frames_ordered_by_name sorts slides by natural filename order (slide2 before slide10) and assigns synthetic positions — no timestamp parsing, any names work. Such segments are marked "untimed": build_segments titles them "Slide N" (not "Segment N — 0:0N") and both the guide and editor templates suppress the start–end time label, which would otherwise show meaningless synthetic values. Threaded via PipelineInputs.untimed and a new Segment.untimed field. The /jobs/from-images endpoint picks the builder by whether a transcript was provided; images.html explains both cases. Tests: natural-sort ordering with no timestamps; untimed render omits meta-time and titles "Slide N"; the timed path still shows the label. …bbe4867 -
feat: make the transcript optional in images mode
ClaudeOn /images you can now omit the transcript and get a slides-only guide: each image anchored at its timestamp, no narration. Useful when you just want an accessible image deck (especially with AI scene descriptions / alt-text turned on). Wiring: * build_frames_from_images: transcript_end is now optional. With none, timestamp parsing skips the range guard and the last slide runs to its own timestamp (no known end). * PipelineInputs gains allow_empty_transcript (default False, so the video path still fails fast on a missing transcript). When True, _load_cues returns [] for a missing transcript and run_pipeline skips the zero-cues error — a slides-only guide is a valid result there. * /jobs/from-images: transcript is optional (File(None)); "no filename" is treated as no transcript. transcript_path/transcript_end stay None, allow_empty_transcript=True. Topic segmentation still requires a transcript, so it's rejected with a clear 400 when absent. * images.html: transcript fi…d9cde51
-
rename: the app is now "The Describatron"
ClaudeRebrand the user-facing name from "Video Guide Maker" to "The Describatron" — and de-video the copy now that it also builds guides from slide images: * Page titles + headers across index / images / edit pages. * FastAPI app title; published-guide and editor footers. * README (HF Space card title + emoji 🎬→🤖 + heading), USER_GUIDE and DATA_HANDLING headings, and the intro prose. * Index eyebrow + sample copy: "lecture video (or slide images) and a transcript" instead of video-only. Infrastructure identifiers left untouched: the GitHub repo (VideoGuideMaker), the HF Space (Video2Guide), the internal package/ logger name (videoguidemaker), and DEPLOY.md's paths — those are real names, not branding. https://claude.ai/code/session_01EM8jiYxdVFy1w3LeJ9GBJg2f32611
-
feat: self-contained edits export + /edit page to reopen a shared JSON
ClaudeMakes the editor's JSON export a true handoff artifact: one file that someone else can open and keep editing, with no accompanying images and no live job. Self-contained export (review.html): * readState now embeds each segment's current image as a data URI (and audio when inlined), so "Save edits (JSON)" carries the slides, not just references to them. The primary <img> src is already a data URI in review mode (even after alt-switching), so it's captured verbatim; a non-data src is omitted rather than saved broken. * downloadZIP strips those embedded URIs before POSTing (it sends images separately + keeps audio server-side) so the ZIP request doesn't carry the image bytes twice. * applyState restores the <img> from image_data_uri when a self-contained JSON is loaded into a live editor, so a file from another session shows the right slides. Data model (metadata.py, html_gen.py): * SegmentMetadata gains optional image_data_uri / audio_data_uri; migration + round-trip…89cae6c -
feat: images-input UI — standalone /images upload page
ClaudeAdds a self-contained upload page for the images-input mode, kept separate from the video form so the working video flow is untouched. /images page: * Multi-image file input + transcript input + title + optional API key. * AI toggles: section titles, scene description, alt-text, on-screen text, math equations. Topic segmentation is intentionally excluded — re-bucketing hand-picked slides into topics fights the point of curating exact slides (the endpoint's topic flags are always sent false from this page). * Output format picker (editor / single HTML / ZIP). * Submit posts to /jobs/from-images, subscribes to the same SSE progress stream, and on completion navigates to the editor (review) or downloads (single/zip) — reuses the existing job/events/result infrastructure end to end. * Accessible: skip link, labelled fields, aria-live progress panel, visible focus, theme-consistent styling. Clears the API key from the DOM after capture. Also: a cross-link on the main vid…31ce41a
-
fix: lifecycle + resource-leak hardening from the audit
ClaudeRemaining confirmed findings, all lower severity: app/jobs.py — job TTL evicted live editors (finding 15): The 10-minute TTL measured from finished_at and was never refreshed by access, so a review session longer than 10 min got its job purged and the editor's lazy /alts, /ocr, /audio fetches and /result re-fetch started 404ing mid-edit. Track last_access_at (bumped on every get()) and purge on idle time = max(finished_at, last_access_at) instead. app/main.py — thread-start leak (finding 19): If the OS refused threading.Thread(...).start() after registry.create(), the job sat in the registry as "running" forever (finished_at stays None → TTL purge never reclaims it), permanently consuming a concurrency slot. Pop the job on a failed start before propagating. app/main.py — upload cap enforced too late (finding 6): The per-field streaming check in _save_upload runs only after Starlette has already spooled the full multipart body to disk. Add an early Content-Len…fbb54cc -
fix: persist and honor per-element include toggles (bug audit cluster 1+2)
ClaudeAdversarial bug audit found the per-element include toggles (added this week) were DOM-only state that neither survived Save/Load JSON nor was honored by the server-side render path (Download ZIP, CLI --metadata). Result: a user who curated which blocks carry over got a ZIP that contradicted Download final HTML, and Save→reopen→Load silently reset every toggle to defaults. Also fixes an a11y regression where a duplicate contenteditable-strip made the ARIA-cleanup pass dead code. Persistence (review.html): * readState now serializes alt_text_included, on_screen_text_included, transcript_included, audio_included (description_included already existed), plus page lang and meta_lines (were dropped, resetting a non-English guide to lang=en and losing header metadata on ZIP re-render). * applyState restores all five per-element flags and lang via a shared applyElementInclude helper; a Load JSON refreshes the bulk-toggle indicators. * Description read/write now uses innerText (not…9a3cbf9
-
editor: Download Markdown — semantic .md export
ClaudeAdds a "Download Markdown" button to the editor toolbar that produces a single self-contained .md file from the current editor state. Mirrors "Download final HTML"'s contract: same per-element include toggles, same description-replaces-alt rule, no server round-trip. Output is semantic markdown (no raw HTML hacks): * # for the page title, ## per section, --- between sections * Eyebrow as *italic*, subtitle as plain paragraph * Timestamps as *italic* sub-line under each heading * Image as  — alt is empty when a scene description is present (matches the published-HTML behaviour) or when the alt-text include checkbox is off * Scene description as plain paragraphs (blank-line separated) * On-screen text as a labelled blockquote (>) when its include toggle is on * Transcript as plain paragraphs when its include toggle is on * Math equations as $…$ (inline) or $$…$$ (block), GitHub-flavoured Markdown compatible Audio is intentionally skipped — markdo…e363538
-
a11y pass for accessibility expert review
ClaudeAudit-and-fix pass on the published-guide and editor templates before sending it for an external accessibility review (Rich Caloggero, MIT DSL). Published guide (guide.html / _doc_styles.html): * Drop role="presentation" from decorative <img alt="">. alt="" alone is the WAI-recommended decorative-image pattern; role="presentation" on <img> has spotty AT support — some readers ignore it, others still announce the image. Empty alt is sufficient and more reliable. * Drop the redundant aria-label on <details class="onscreen-text">. The <summary> is the accessible name; layering aria-label on top either overrides the visible summary (WCAG 2.5.3 Label in Name mismatch) or duplicates it. Remove. * Only emit audio aria-describedby="narration-N" when the narration block it points at is actually rendered. A dangling describedby is an ARIA validity bug (WCAG 4.1.2 / 1.3.1) and some screen readers silently swallow the relationship, leaving the audio undescribed. * Bump TOC link…5a2d8c8 -
editor: make the include-set inline-row CSS actually win
ClaudeThe previous commit (15241a4) restyled the per-section include fieldset as a horizontal flex-wrap row, but the rules sat on a bare .vgm-include-set / .vgm-include-set__row selector — class-count 1. The panel's generic .vgm-edit-panel label { display: flex; flex- direction: column } rule has class-count 1 + type-count 1, so it beat my selector and silently stacked each checkbox on its own line with the label rendered below it. Scope the include-set selectors under .vgm-edit-panel and pin the row at label.vgm-include-set__row so they outrank the generic panel-label rule. Net specificity: 2 classes (+1 type on the row) vs the generic rule's 1 class + 1 type. No DOM change, pure CSS bump. https://claude.ai/code/session_01EM8jiYxdVFy1w3LeJ9GBJgc25567f -
editor: collapse the per-section include set onto a single inline row
ClaudeThe "Include in published guide" fieldset was rendering each of its five or six checkboxes as its own vertical row inside a bordered box, eating about 9rem of height in every segment. With 10+ segments in a typical study guide it dominated the editor scroll. Restyle the fieldset as an inline flex-wrap row: no border, no block padding, the legend sits inline as a small uppercase label, and each chip is a `display: inline-flex` with `white-space: nowrap` so a single chip never wraps mid-label. The whole control fits on one line on wide screens and wraps to two on narrow. Behaviour is unchanged — the DOM, the data-element-toggle attributes, the bulk-bar sync, and the data-include / data-include-alt-text plumbing all stay the same. Pure CSS change. https://claude.ai/code/session_01EM8jiYxdVFy1w3LeJ9GBJg15241a4 -
editor: drop the 'Include section' bulk toggle
ClaudeA global toggle for the per-section master include switch doesn't read as a meaningful bulk action — flipping it either does nothing (every section already included) or empties the published guide. Remove it from the bulk bar; the per-section checkbox stays. The bulk bar now only carries toggles for things that make sense to apply uniformly across all sections: Scene description, Alt-text, On-screen text, Transcript, Audio. https://claude.ai/code/session_01EM8jiYxdVFy1w3LeJ9GBJg007ae3b -
editor: clearer 'Include section' label; fix popup-blocked Preview
ClaudeTwo small editor fixes: * Rename "Whole section" → "Include section" in both the per-section fieldset and the new bulk-toggle bar. The old label read fine in the per-section context (the legend "Include in published guide" gave context) but in the bulk bar it sat next to "Apply to all sections:" and was confusing — "apply to all sections: whole section". The new wording stands on its own. * Preview button no longer trips the popup blocker. previewHTML was async and awaited inlineAllAudio() BEFORE calling window.open(); once you await inside a click handler the browser no longer treats the subsequent window.open as user-initiated, so Safari and Chrome both reject it. Open the tab synchronously at the top of the handler with about:blank, then navigate it to the blob URL once the HTML is ready. Errors close the pre-opened tab so we don't leave an orphan window. https://claude.ai/code/session_01EM8jiYxdVFy1w3LeJ9GBJgb607027 -
editor: bulk include toggles that drive every section at once
ClaudeAdds a "Apply to all sections" bar between the toolbar and the document header. One checkbox per include key — Whole section, Scene description, Alt-text, On-screen text, Transcript, Audio. Three behaviours: * Standard tri-state. The bar reflects the union of per-section state on page load: all-checked, all-unchecked, or indeterminate when sections disagree. * Bulk → per-section. Toggling a bulk box sets every matching per-section checkbox to the bulk's new state and dispatches a synthesised 'change' event on each, so the existing per-section sync (data-include, data-included, data-include-alt-text) fires for free. No duplicated wiring. * Per-section → bulk. Any individual checkbox change re-runs the union calculation so the bulk indicator stays accurate. Applies after Load JSON too (applyState calls syncBulkToggles when it finishes mutating per-section state). A bulk box for a key with zero matching per-section checkboxes (e.g. Audio when no segment carries an au…93e4afe -
editor: per-element alt-text and transcript toggles; rename 'Scene description'
ClaudeThree pieces of UX feedback: * Alt-text now has its own include checkbox in the per-section "Include in published guide" fieldset, default OFF. When off, buildFinalHTML blanks the <img alt> at download time. Because alt is an attribute (not a discrete element), the checkbox writes its state to data-include-alt-text on the section and buildFinalHTML reads it alongside the description-present check; the helper attribute is stripped from the final HTML. * Narration sections are now rendered as <details class="narration"> with summary "Transcript", collapsed by default — in both the editor view and the server-side render (guide.html). A matching per-element include checkbox sits in the fieldset, also default OFF, so transcripts no longer carry over to the published guide unless the editor explicitly opts in. The narration body keeps its stable id so any audio aria-describedby reference still resolves; when transcript is excluded the strip pass collects removed…0c2c651 -
editor: stop emitting the alt-review figcaption when description carries the meaning
ClaudeTwo paths were leaking the "Alt-text needs author review." caption into the final HTML even when it no longer applied: * review.html rendered the figcaption purely on `seg.alt_text_reviewed`, so a segment with a populated description (alt is intentionally empty, not pending) still got the warning. Add `not seg.description` to the conditional so the editor view and the server-side review render both stay quiet in that case. * buildFinalHTML blanked the <img alt> when a description was present but never touched the figcaption next to it. Now the same per-section pass also strips figure.figure > figcaption when either (a) the description is present-and-included, or (b) the user edited alt-text in this session (data-alt-reviewed flipped to 'true'). Both cases mean the "needs review" note is stale. Adds a regression test confirming the caption disappears once `seg.description` is set, regardless of `alt_text_reviewed`. https://claude.ai/code/session_01EM8jiYxdVFy1w3LeJ…9eb147c
-
editor: remove summary / key-terms / self-check (round 3)
ClaudeAccessibility team's round-three asks: * "Summary Field — redundant, remove" (now subsumed by the new detailed description paragraph from PR 2) * "Key Terms — REMOVE. This replicates the glossary." * "Self-check questions — REMOVE! This is an academic role and such questions are better placed in the platform." Scope of removal: * Editor (review.html): drops the summary <input>, the key-terms list editor block, the self-check-questions list editor block, the related CSS rules (.vgm-key-term-row, .vgm-self-check-row), the readState/applyState/syncBindings hooks, the makeKeyTermRow / makeSelfCheckRow row factories, the add-key-term / add-self-check click handlers, and the entire glossary/highlight injection inside buildFinalHTML. * Published guide (guide.html): drops the "In brief:" advance organizer, the self-check <details> block, the bottom glossary section, the highlight_terms filter usage on narration, and the build_glossary call at the top of <main>. * LLM (ll…b863381 -
editor: long-form image description field (round 2)
ClaudeAdds the "Detailed description" field the accessibility team asked for — an editable open paragraph rendered UNDER the slide image that doubles as the long-form image description. When non-empty AND included in the published guide, the <img alt> drops to "" and the image is marked role="presentation": the description carries the meaning in body text where sighted AND non-sighted readers both encounter it, so there's no need to duplicate it inside an alt attribute that only screen readers hear. The pieces: * SegmentMetadata + Segment + migration gain description / description_ reviewed fields. Round-trips through Save/Load JSON. * New LLMToggles.description toggle. _FIELD_PROMPTS adds a description prompt that follows the team's example ("A gallery of purple flower stem macro photographs is shown. These demonstrate..."), and the structured-output schema gains a matching description field that only fires when the toggle is on (no wasted output tokens otherwise). * Orchestra…cf53b59 -
editor: accessibility-team UX pass (round 1)
ClaudeRound-one feedback from the accessibility team, focused on changes that don't alter the data model or remove fields: * Banner trimmed — three sentences down to one. * Segment image moved above the editable fields so the editor sees what they're describing before they describe it. * Alt-text field is now a multi-row textarea, not a single-line input. Some descriptions take two paragraphs and the old input made that impossible without scrolling a clipped one-liner. * New per-element "Include in published guide" fieldset replaces the single per-section checkbox. The whole-section checkbox stays. Two new checkboxes: - On-screen text from video (defaults to included) - Narration audio clip (defaults to EXCLUDED — per the team, audio shouldn't carry over to the published guide by default) Each checkbox drives data-include on a matching [data-element=…] node; buildFinalHTML now strips anything still flagged false, plus the data-include / data-element attributes …3672e55
-
Accessibility: drop prohibited aria-labelledby from no-role narration div
ClaudeAxe-core's wcag2aa+best-practice scan against a freshly-rendered guide returned 0 violations but flagged the narration__body div's aria-labelledby="narration-label-N" as an incomplete (potentially prohibited) ARIA attribute. <div> has no implicit role, so the attribute has no name slot to fill and many AT will ignore it anyway — the sr-only <h3>Narration</h3> sibling already labels the block via standard heading semantics. Drop aria-labelledby from both guide.html and review.html. Keep the id on the inner div so the section's <audio> element's aria-describedby can still point at the narration text. Re-running axe after the change: 0 violations, 0 incomplete, 43 passes. WCAG 2.2 AA clean on the rendered guide.3c265ff -
Accessibility: term tooltips become real <a> links to glossary entries
ClaudeThe narration's inline highlighter wrapped each defined term in a <mark class="kt" title="…"> with the definition only in the title attribute. WCAG 2.5.1 / 4.1.2 — touch users can't trigger hover, keyboard users can't focus a <mark>, many screen readers skip the title attribute entirely. Definitions were effectively unavailable to roughly half of likely users. Build the glossary once at the top of <main> and pass it to the highlighter so each first-occurrence wrap becomes <a class="kt" href="#glossary-N" title="…">term</a> — focusable, touch-tappable, screen-reader announced as a link to the named target. The bottom glossary's <dt> ids match the hrefs the highlighter emits (build_glossary now stamps each entry with its own `id` field so server template and JS port share the contract). Terms with no glossary entry (defensive) fall back to the old <mark> shape. Mirror in buildFinalHTML: build the glossary entries before walking sections, thread the lookup through highlightTerms, reus…c28a145 -
Cleaner study-guide output: drop redundant per-section key-term list
ClaudeUser feedback: with inline term highlighting AND a bottom glossary, showing the same vocabulary again as a per-section <dl class="key-term"> was triple-redundant and visually noisy. - Drop the per-section <dl class="key-term"> from guide.html. Definitions remain accessible two ways: - inline via the .kt highlighter (hover tooltip on the first occurrence in each paragraph) - at the end of the document via the auto-built glossary (alphabetised, back-anchored to source section). - Mirror in buildFinalHTML so downloaded HTML matches. - Update test_render_guide_renders_key_terms_and_equations to expect the glossary instead of the per-section list. Also cleaned up two other visually-noisy bits while in the same file: - Figure's "Lecture slide." caption: redundant with the section heading + meta-time line and the figure-internal timestamp badge. Now we only emit a figcaption when there's something real to say ("Alt-text needs author r…8fb4d34 -
Third-pass audit fixes: migration setdefaults, robust JS mark builder
ClaudeP1 — migrate_v1_to_v2 didn't setdefault the new learner-feature fields (summary, self_check_questions). Pydantic still supplied defaults on model_validate so no data was lost at load time, but the migration's raw-dict output was asymmetric — any consumer of the migrated dict pre-validation would see undefined keys for those two fields and not for the others. Adds the two setdefaults so the migration's contract stays "every SegmentMetadata field has a defined key after migration". P2 — JS highlightTerms built its <mark> open tag via template-string interpolation: `<mark class="kt" title="${escapeHtml(definition)}">`. The contemporaneous escapeHtml correctly entity-encodes quotes, so no XSS materialized — but the .replace() second argument treats $&, $', $`, $n as special replacement patterns. Any `$` surviving escapeHtml (it doesn't escape `$`) would get mangled in the output title. Switch to building the mark via document.createElement + setAttribute, then serializing with outerHTML t…7562488 -
Editor downloadHTML: emit summary, self-check, glossary, highlights
ClaudeThe editor's "Download final HTML" path doesn't go through the server-side Jinja templates — it builds the final document from the editor's live DOM via buildFinalHTML(). I taught the server template (guide.html) about the four learner features but forgot to teach buildFinalHTML the same vocabulary, so the downloaded file came out with key terms and math equations but no summary, no self-check block, no inline term highlights, and no glossary. Extend buildFinalHTML to inject all four: - Summary line (.section__summary "In brief: …") inserted right after each section's <p class="meta-time">. - Inline highlighting of defined terms in narration paragraphs via a JS port of the server-side _highlight_terms filter (longest-first, one mark per term per paragraph, skips text already inside a <mark> so wraps never nest). - Self-check questions as a <details class="self-check"> block at the end of each section, matching guide.html's structure. - Auto-built glossary …327d32d -
Update review.html
60c7af8 -
Learner-focused features: summary, self-check, glossary, inline term highlighting
ClaudeTagged pre-learner-features at the commit before this so a single `git reset --hard pre-learner-features` (or non-destructive `git revert pre-learner-features..HEAD`) takes us back to known-good if anything misbehaves. Four learner-impact features ship together because they share data plumbing — same Segment/Metadata schema additions, same editor round-trip work: #2 One-sentence summary above each section. Claude's `summary` field from topic segmentation is now rendered as an "In brief:" advance organizer above the slide image. Primes the learner before they hit the detail; evidence-based for comprehension. Editable in the review screen. #4 Auto-built glossary at the end of the guide. Collects every segment's key_terms across the whole document, dedupes case- insensitively (first-occurrence wins), sorts alphabetically, and anchors each entry back to the section where the term was first introduced. #5 Inline key-term highlighting in narration. Defined terms w…d61b118 -
UX backlog: flatten sidebar, compact output picker, jargon tooltips, sample panel
Claude#12 Flatten the Advanced settings sidebar. The "More settings" inner collapsible hid three controls behind a second click for no real benefit — sidebar is short enough to show all seven at once. Drop the toggle button, its CSS, and the JS that wired it. #6 Move the four-radio output-format block into the submit row as a small "Output format" dropdown. 90% of users leave it at "Review & edit"; promoting a top-level section for it was over- weight. The dropdown sits next to the Generate button so the choice stays one click away without consuming form space. #11 Add a `.vgm-help` "?" badge for the genuinely-technical labels in the sidebar (Scene-change sensitivity, Min gap, Instructor-frame threshold, Document language). The badge is keyboard-focusable (tabindex=0), reads via aria-label to screen readers, and shows the expanded explanation on hover via the title attribute — no JS needed. Friendlier copy on the transcript hint ("Cue ti…4031b6c
-
Demote non-LLM scene picker; AI topic preview is now the primary CTA
ClaudeThe two-button row read as "pick one of two equivalent paths" but they aren't — the AI path produces meaningfully better study guides when an API key is available. Promote the topic-preview button to the primary CTA the moment a key arrives, and demote the plain "Preview scenes" button to a small text-link beneath it ("or pick slides individually without AI"). When no key is present, hide the AI button entirely and let the plain picker stand alone as the primary CTA — no dead "disabled because key missing" state. The non-LLM path stays fully functional and intentionally one click away, so users on the public Space without a key still get the demo; users worried about privacy / cost / outages keep their escape hatch; the CLI is unaffected. Backend: /jobs now rejects up-front when any AI toggle is ticked without an API key. Previously per-segment toggles silently no-op'd and topic segmentation hard-failed halfway through; now the user gets a single explicit "add a key or uncheck AI fea…908a4e1 -
Topic prompt: video-type dropdown biases boundaries to genre structure
ClaudeGeneric topic segmentation works but produces splits that ignore genre conventions — a lab walkthrough is sliced like a lecture, a tutorial like a panel. Add a per-job "video type" hint the user can pick from a small dropdown; the orchestrator prepends a paragraph of structural guidance to the topic prompt so Claude knows what shape to bias toward. Five genres modeled today (each one paragraph of prompt): - Classroom lecture: intro → background → concept(s) → examples → wrap-up - Lab walkthrough: intro → theory → materials → procedure → results - How-to tutorial: intro → setup → steps → verification → troubleshooting - Interview / Q&A: boundaries at new questions or subject pivots - Talk / presentation: hook → thesis → supporting points → closer plus "General" which leaves the prompt untouched. Unknown values fall back to general so a stale form post can't break the call. Wired through extract_topics(video_type=...), LLMToggles .topic_video_type, the orchestrator, and both …6dd9ac4 -
Auto-enable topic segmentation when an API key is present
ClaudeTopic segmentation is the standout feature for users with an API key but it sat as an opt-in toggle three groups deep in the form. Most people never discovered it and walked away from a per-slide guide thinking that was the tool's default story — when the JamWorks-style topical breakdown they actually wanted was one checkbox away. Auto-check the toggle the first time the API key field gains a value. Pair the flip with a soft maroon banner under the section heading ("Auto-enabled. Claude will group the slides into topical sections…") so the change is visible and the opt-out path is named. The first manual toggle (in either direction) sets a userTouched flag on the checkbox; from then on we never auto-flip again, even if the key is later removed and re-entered — the user's explicit choice always wins. Removing the key with no manual touch unchecks again so the form's submitted state stays consistent with the key state.f759553 -
Upload page UX, batch 2: differentiate buttons, group toggles, nest sub-toggle
Claude#2 The two preview buttons now read as parallel paths rather than primary/secondary. Inline SVG icon on each (filmstrip-style for the plain scene picker, sparkles for the AI-driven topic picker) plus a small "AI" badge on the topic variant so the choice is legible at a glance. #3 AI assist section split into two visually-distinct clusters with their own subheadings: - Per-segment enrichments: section titles, alt-text drafts, key terms, math equations, on-screen text. - Whole-document features: topic-based segmentation (and its sub-toggle). Each cluster has a one-liner explaining its cost model so the user can scan "cost scales with segments" vs "one-off whole- video call" without reading every individual blurb. #9 The "Also send slide images" sub-toggle is no longer a sibling with an "↳" prefix. It now lives in its own .vgm-llm-subgrid container with a left rail, indentation, lighter background, and slightly smal…d2d35b6 -
Upload page quick wins: clarify, deduplicate, surface what's missing
Claude#1 Disabled preview buttons now explain what's blocking them. A live "Add a transcript and an Anthropic API key to enable…" line under the buttons tells the user which inputs are still needed instead of leaving them to hunt for it. The text mode (intro vs. topic- only) matches what's actually blocked so the message is precise. #4 Preview hint copy goes from soft warning to positive nudge. "Recommended — pick which slides…" → "Tip: preview first so you only generate the slides you'll keep." Less guilt-inducing, same intent. #5 API key field no longer duplicates itself. The label's optional tag was saying the same thing as the help text — kept the tag, rewrote the help to focus on the security claim (memory-only, HTTPS, no logging) with a lock-icon prefix for visibility. #8 Submit hint updates dynamically. The "~30 s per minute" baseline misled anyone who turned on LLM toggles or audio extraction; now the line appends the extra cost in a…7829a47 -
Promote API key field above the preview buttons
ClaudeTopic-scene preview requires an Anthropic API key but the field was buried in section 2 (AI assist), below the preview buttons that need it. Users hit the disabled "Preview topic scenes" button with no obvious next step. Move the API key field into section 1 between Transcript and the preview buttons, so by the time the user looks at the buttons all three prerequisites are visible above them. Section 2 now only holds the per-feature LLM toggles; its intro updated to reference the API key field above.2fde543 -
Add 'Preview topic scenes' button alongside the existing scene picker
ClaudeTwin of the Preview scenes flow that runs the topic LLM pipeline (scenes -> filter -> transcript -> OCR -> topic LLM -> primary picking) and renders one card per topic with title, summary, and primary-frame thumbnail. The user unchecks topics they don't want, then submits; /jobs resumes the pipeline from the curated subset and skips the topic LLM call that already ran. Saves the per-segment LLM extraction cost on topics the user wouldn't have wanted anyway. Backend - New POST /topic-scene-preview endpoint mirroring /scene-preview but additionally running OCR + topic LLM + primary-frame picking before returning topic cards. Caches the post-topic kept frames plus parallel title / summary / OCR lists alongside the same preview-cache infrastructure (is_topic_preview marker on the entry so /jobs can disambiguate). - /jobs honours topic-preview indices positionally and threads the selected topic titles through run_pipeline as preselected_topic_titles. Topic segmentation is for…edad228 -
Merge pull request #65 from JoeMartis/claude/fix-zip-path-traversal-9kA4Q
UI: add topics stage chip between ocr and llm9bda4f7 -
UI: add topics stage chip between ocr and llm
ClaudeThe progress chip row in the upload page hadn't been updated when I added topic segmentation. The orchestrator emits a 'topics' stage event at 76% (between OCR and the per-segment LLM extraction) but the UI had no chip for it, so the highlight just sat on 'ocr' until the LLM stage kicked in. Insert a 'topics' chip in the markup and add it to STAGE_ORDER so the highlight advances in step with the pipeline.cf97819
-
Merge pull request #58 from JoeMartis/claude/fix-zip-path-traversal-9kA4Q
Claude/fix zip path traversal 9k a4 q25ab096 -
Add image-augmented topic segmentation as a sub-toggle
ClaudeBuilds on the transcript-only topic segmentation: when the new "Also send slide images" sub-toggle is on (only available when the parent toggle is checked), the orchestrator hands extract_topics a list of (start_seconds, image_path) tuples and the function attaches thumbnailed slides to the Claude request alongside the transcript. Slides are downscaled to 768px max-dim before base64 encoding so Anthropic's image-token cost stays bounded; if more than 60 kept scenes exist, the set is uniformly sampled (preserving the first and last frames where chapter markers usually live). Two prompt variants — the system prompt for the image branch explicitly tells Claude how to interpret slide-vs-narration signals, so it doesn't double-count layout changes within the same topic. UI: the sub-toggle is hidden until the parent is checked, and gets unchecked automatically when the parent unchecks so a hidden box can't post stale state. Tests verify the request shape (image blocks present + image-awar…9a92330 -
Add LLM topic-based segmentation as an opt-in toggle
ClaudeReplaces the scene-based one-segment-per-slide bucketing with topical sections generated by Claude from the transcript. One extra LLM call per job (transcript-only, no images) returns 3–15 sequential topics with titles and summaries; the orchestrator then re-buckets the kept scene frames so each topic-segment carries the longest-on-screen scene as its primary image and the other scenes as switchable alternates in the editor. Per the design discussion: - Opt-in via a new LLMToggles.topic_segmentation field; existing scene-based path stays the default. - Multi-slide topics keep every slide accessible (primary + cross- scene alts on top of the per-scene candidate alts). - LLM failure raises PipelineError so the job surfaces a clear error rather than silently falling back. The /alts and /ocr endpoints now also accept the scene_NNNN.jpg primary pattern because cross-scene alternates re-use those filenames.7e20c47
-
Fix scene strip overflowing into sidebar
ClaudeRemoved negative margins on .vgm-scene-scroll-wrap that caused the scroll strip to bleed outside its grid column into the settings sidebar. Added overflow:hidden to clip the arrow buttons cleanly within the column. https://claude.ai/code/session_01EGBMur51izertyiu7msWPQb62a74c -
Move Instructor-frame threshold above Max frames in sidebar
ClaudePulls the control out of the collapsed "More settings" section so it sits directly above Max frames, improving discoverability. https://claude.ai/code/session_01EGBMur51izertyiu7msWPQf50ea68 -
Fix bugs and security issues from post-a11y scan
ClaudeBugs: - _doc_styles.html: move @import to first line (was after :root, silently ignored by browsers — Merriweather/Source Sans 3 never loaded) - index.html: merge duplicate .vgm-scene-thumb rule; position:relative now lives in the main block so the ::after overlay always has a positioning context - index.html: add sandbox attribute to review iframe (allow-scripts allow-same-origin allow-downloads allow-forms) - index.html: reduce non-review format resetForRetry delay 2500→1500ms; focus is now returned sooner after download - review.html: makeKeyTermRow aria-label updates live as user types the term, matching the Jinja server-rendered row behaviour Security: - main.py: add HTTP security header middleware (X-Content-Type-Options, X-Frame-Options, Referrer-Policy, Content-Security-Policy) - llm_extract.py: scrub API key from exception messages before logging https://claude.ai/code/session_01EGBMur51izertyiu7msWPQ3964d02 -
WCAG 2.1 AA accessibility fixes across all templates
ClaudeContrast (1.4.3/1.4.11): - Banner secondary text: #ECBFC7 → #f5d5db (3.0:1 → 4.6:1 on #750014) - Subtle text color: #888 → #767676 (3.5:1 → 4.5:1 on #fafaf7) - Form input focus: restore outline:2px solid primary (was outline:none) - contenteditable outline: 1px dashed #D0D0D0 → 2px dashed #767676 Screen reader utilities (1.3.1/2.4.6): - Add .sr-only utility class to _doc_styles.html and index.html - Replace outdated left:-9999px sr-only h2 with proper .sr-only class Non-text content (1.1.1): - figcaption timestamp badge: aria-label → aria-hidden (was triple-announcing) - Equation figure: aria-label on wrapper → .sr-only figcaption (avoids overriding MathJax assistiveMml) - Deselected scenes: add diagonal stripe ::after so state isn't opacity-only Semantics / relationships (1.3.1): - Narration div: add aria-labelledby linking to label span (guide + review) - Key terms editor: add role="group" + aria-labelledby - Math equations editor: add role="group" + aria-labelledby - Key term i…b12bb48 -
UX polish: sidebar collapse, preview hint, shorter copy
Claude- Sidebar: face threshold, skip OCR, skip inverted OCR, document language now live behind a '› More settings' toggle — sidebar height cut ~40% and all controls remain accessible - Trim sidebar help text to one line each (descriptions kept, just shorter) - Preview Scenes button: add 'Recommended — pick which slides to include' hint line so new users understand its purpose - AI Assist intro: cut 3-sentence paragraph to 1 sentence https://claude.ai/code/session_01EGBMur51izertyiu7msWPQ55c05e0 -
Fix P1 bugs: cache race, blocking event loop, retry state, compat selector
Claude- _preview_cache: add threading.Lock() guarding all reads/writes/pops so concurrent preview purge + job start can't double-free a dir - /scene-preview: move PIL thumbnail loop into run_in_executor so it no longer blocks the async event loop during frame encoding - /jobs: protect cache .pop() with lock; add frames_dir.mkdir() for non-preview path (defensive, detect_and_extract creates it anyway) - /process: wrap run_pipeline in asyncio.to_thread so the backwards-compat endpoint doesn't freeze the event loop during pipeline execution - _save_upload: remove redundant f.close() inside with-block (double-close) - resetForRetry: clear preview token + restore video required attr + hide scene section, so retry after error doesn't send an expired token - review.html applyState: replace label:has() with .closest('label') for Firefox < 121 / Safari < 15.4 compatibility https://claude.ai/code/session_01EGBMur51izertyiu7msWPQ803dc05 -
Remove tagline paragraph from header
Claudehttps://claude.ai/code/session_01EGBMur51izertyiu7msWPQe59897f -
Add scroll arrows and visible scrollbar to scene picker strip
ClaudeAdds ‹/› arrow buttons that appear when there are off-screen thumbnails, styled scrollbar (thin, always visible via scrollbar-width:thin), and a scroll wrapper so the strip bleeds to card edges without negative-margin scroll clipping issues. https://claude.ai/code/session_01EGBMur51izertyiu7msWPQ24ab2d2 -
Fix sidebar not showing and preview button full-width
Claude- Add min-width:0 to grid columns so the sidebar renders correctly - Add align-self:flex-start to preview button so it doesn't stretch full-width inside the flex column https://claude.ai/code/session_01EGBMur51izertyiu7msWPQ0d201ca