Package v0.2.12→v0.2.124: manifest, actions, version graph

This commit is contained in:
Keysat
2026-06-13 13:36:30 -05:00
parent 318c6c4b81
commit 1243f4414c
126 changed files with 2052 additions and 441 deletions
+13
View File
@@ -0,0 +1,13 @@
import { VersionInfo } from '@start9labs/start-sdk'
export const v_0_2_64 = VersionInfo.of({
version: '0.2.64:0',
releaseNotes: {
en_US:
'Analyze prompt overhaul to match the Recap-app\'s direct-to-Gemini behavior. Two coupled changes: (1) Transcript format passed to the analyze model is now numbered + timestamped — each line is `[N] (MM:SS) text` instead of `[MM:SS] text`. The bracketed [N] index at the start of each line is exactly what the model is asked to reference when emitting startIndex / endIndex in the JSON response, so the contract is now explicit in the input rather than requiring the model to count bracketed-timestamp lines internally. This is the root cause of the runaway-endIndex hallucinations that motivated the v0.2.61 stitcher clamp — without visible indices, models occasionally emit values like 9999 for a 200-entry window. The v0.2.61 clamp stays as a safety net but should fire dramatically less. (2) DEFAULT_ANALYZE_PROMPT_TEMPLATE rewritten to adopt Recap-app\'s completeness contract while preserving the relay\'s broad-sections design intent and operator-tunable variables. Adds explicit "every segment index from 0 to {{maxIndex}} must belong to exactly one section" + "startIndex of section N+1 must equal endIndex of section N plus 1" requirements — closes the gap (literally) where the old prompt allowed sections to skip portions of the window. Drops the "single section spanning the whole window is often the correct answer" invitation that pushed the model toward oversized single sections. Keeps {{windowMin}}, {{targetSections}}, {{transcript}} variables AND adds {{maxIndex}} = last valid index in the window for the completeness clause. Net effect: stitched output should cover every minute of every window with no gaps, AND broad-section preference is preserved via {{targetSections}} guidance + "lean toward broad, substantive topics" wording. Operator overrides saved in relay-config.json keep working unchanged — they receive the new {{transcript}} format (still timestamped, just with [N] prefix added) and existing {{windowMin}}/{{targetSections}} keep working. Add {{maxIndex}} to your override if you have one and want the completeness clause to mention a concrete index.',
},
migrations: {
up: async ({ effects }) => {},
down: async ({ effects }) => {},
},
})