Files

T

agent_coder 02308012a6 feat(gitmost-bridge): insert transcript into the recording page (#377 )

The native gitmost.app (stage 2) now sends a `transcript` field to
window.gitmost.createPageWithRecording, but the web bridge ignored it — the page
was created with audio only. Insert it.

- gitmost-recording.ts: add `transcript?: string` to GitmostCreatePagePayload
  (plain text, \n-separated `You:` / `Speaker N:` lines, ready to insert). Add a
  gitmostInsertTranscriptIntoEditor(editor, transcript) helper: a "Transcript"
  heading + one paragraph per non-empty line, each line inserted VERBATIM as a
  text node (never HTML → no injection), appended at doc end (below the audio).
  No-op when transcript is undefined/empty/whitespace-only/non-string.
- gitmost-global-bridge.tsx (createPageWithRecording): after the audio insert
  succeeds, call the helper inside a try/catch — best-effort, so a transcript
  failure can never turn the already-successful recording into an error (logs +
  still returns ok). Absent transcript → audio-only page, exactly as today.

DoD: recording with speech → page has audio AND a labeled transcript block;
without transcript → unchanged. Closes the web-side dependency of gitmost-app
stage 2. Verified: apps/client tsc --noEmit 0 errors; 2 unit tests
(transcript present → heading+paragraphs; undefined/""/whitespace/number/object
/null → no-op, doc unchanged).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

2026-07-06 00:01:25 +03:00

perf

test(ai-chat): add dev-only perf harness for the chat stream pipeline

2026-07-04 03:51:22 +03:00

public

feat(#371 ): roles catalog modal redesign — bundle cards + per-role import results

2026-07-05 05:35:58 +03:00

scripts

fix(dictation): also ship the plain onnxruntime-web wasm variant

2026-06-22 17:40:45 +03:00

src

feat(gitmost-bridge): insert transcript into the recording page (#377 )

2026-07-06 00:01:25 +03:00

.dockerignore

…

.gitignore

…

eslint.config.mjs

…

index.html

feat(brand): roll out Gitmost logo, favicon and app name

2026-06-18 00:12:26 +03:00

package.json

feat(observability): dev-side perf metrics — /metrics + client vitals (#355 )

2026-07-04 23:10:29 +03:00

postcss.config.js

…

README.md

…

tsconfig.json

…

tsconfig.node.json

…

vite.config.ts

feat(client): show git-describe version next to the brand logo

2026-06-18 04:51:21 +03:00

vitest.config.ts

test(infra): coverage-gate + acceptInvitation atomicity int-spec + turn-end unit (#324 )

2026-07-04 12:37:28 +03:00

vitest.setup.ts

chore(comments): address PR #143 review (operator doc, badge test, dedup, type)

2026-06-23 23:56:26 +03:00

README.md

React + TypeScript + Vite

This template provides a minimal setup to get React working in Vite with HMR and some ESLint rules.

Currently, two official plugins are available:

@vitejs/plugin-react uses Babel for Fast Refresh
@vitejs/plugin-react-swc uses SWC for Fast Refresh

Expanding the ESLint configuration

If you are developing a production application, we recommend updating the configuration to enable type aware lint rules:

Configure the top-level parserOptions property like this:

   parserOptions: {
    ecmaVersion: 'latest',
    sourceType: 'module',
    project: ['./tsconfig.json', './tsconfig.node.json'],
    tsconfigRootDir: __dirname,
   },

Replace plugin:@typescript-eslint/recommended to plugin:@typescript-eslint/recommended-type-checked or plugin:@typescript-eslint/strict-type-checked
Optionally add plugin:@typescript-eslint/stylistic-type-checked
Install eslint-plugin-react and add plugin:react/recommended & plugin:react/jsx-runtime to the extends list