14 lines
2.8 KiB
TypeScript
14 lines
2.8 KiB
TypeScript
import { VersionInfo } from '@start9labs/start-sdk'
|
|
|
|
export const v_0_2_115 = VersionInfo.of({
|
|
version: '0.2.115:0',
|
|
releaseNotes: {
|
|
en_US:
|
|
"Internal meeting hints + transient operator notes + self-contained shareable HTML. Three related changes: (1) Participants are now treated as HINTS, not authoritative truth, in both the name-inference and meeting-extras LLM passes. Before: the upload's comma-separated participants field was being stuffed into the name-inference prompt's 'Description:' metadata slot as 'Likely participants: A, B, C', which the LLM tended to read as a definitive speaker list — even when fewer or different people actually spoke. After: participants flow through a new explicit OPERATOR HINTS block in the prompt that's prefaced with 'treat as suggestions only — verify against the transcript before assigning names', plus an instruction telling the LLM that a name in the hints is only a candidate, the transcript can override hints, and returning null is better than mapping a hint to the wrong chip letter. (2) New Notes field on the upload form — TRANSIENT, NOT PERSISTED. Free-form prose (up to 4000 chars) where the operator can describe who-said-what to help the LLM disambiguate speakers. Example: 'Steve from XYZ Corp gave a business update. John followed up with questions about Q3. Hank chimed in toward the end.' Notes get passed to the OPERATOR HINTS block in both prompts (name inference + extras) as a soft signal the LLM weighs against the transcript, then are DROPPED. They never appear on the saved meeting record, the dashboard detail view, or any of the downloads (.md / .html / .json). The operator can write candid disambiguation context ('Steve is the new guy still figuring stuff out', 'John was angry about Q3') without worrying about it becoming part of a shareable artifact. The upload form makes this explicit in the field's helper text. (3) Downloaded .html is now truly portable. The shareable HTML file embeds the .md and .json serializations inline as base64 data URLs and exposes 'Download .md' and 'Download .json' buttons in the page header — so a recipient who got the HTML via email / shared drive / etc. can grab any of the three formats with no relay round-trip and no admin auth needed (the relay download endpoints are gated, external recipients couldn't reach them anyway). Buttons hide in print stylesheet. Size overhead is ~33% from base64 — still tens of KB for a typical meeting. Existing YouTube/podcast flow is untouched — runNameInference's new participantHints / operatorNotes args default to empty, the OPERATOR HINTS block in the rendered prompt collapses to nothing when both are empty, and the prompt looks exactly like before for those callers.",
|
|
},
|
|
migrations: {
|
|
up: async ({ effects }) => {},
|
|
down: async ({ effects }) => {},
|
|
},
|
|
})
|