docs: bootstrap .planning/ via /gsd-ingest-docs (2 docs) /home/parf/projects/work/repremium/.planning/PROJECT.md /home/parf/projects/work/repremium/.planning/REQUIREMENTS.md /home/parf/projects/work/repremium/.planning/ROADMAP.md /home/parf/projects/work/repremium/.planning/STATE.md /home/parf/projects/work/repremium/.planning/intel /home/parf/projects/work/repremium/.planning/INGEST-CONFLICTS.md /home/parf/projects/work/repremium/.ingest-manifest.yaml

This commit is contained in:
2026-05-15 15:16:30 +02:00
parent 555eb0543f
commit 89ca09ccec
12 changed files with 1637 additions and 0 deletions

View File

@@ -0,0 +1,28 @@
{
"source_path": "/home/parf/projects/work/repremium/README.md",
"type": "DOC",
"confidence": "high",
"manifest_override": true,
"title": "AI Call Recorder - Браузерное расширение для записи сессий операторов",
"summary": "Developer-facing README covering installation, usage, technical stack, and Phase 1 acceptance criteria for a Chrome extension that records operator sessions locally and exports a ZIP archive.",
"scope": [
"Chrome Extension Manifest V3",
"Service Worker",
"Content Script",
"Popup UI",
"chrome.tabCapture video buffer",
"rrweb DOM capture",
"user event logging",
"JSZip archive packaging",
"chrome.downloads",
"Vite + crxjs + TypeScript build",
"ring buffer (video 30s, rrweb 10min, events 10min)",
"sensitive data masking",
"Phase 1 acceptance criteria",
"memory consumption targets"
],
"cross_refs": [],
"locked": false,
"precedence": 1,
"notes": "Manifest declared type=DOC and precedence=1, treated as authoritative. POTENTIAL CONFLICT WITH SPEC: line 106 states expected memory '~5-10 МБ in background mode', while line 118 acceptance criterion states ceiling 'не превышает 50 МБ' — synthesizer should reconcile against the SPEC's 50 МБ ceiling. INTERNAL INCONSISTENCY: README presents both an expected-value (5-10 МБ) and a ceiling (50 МБ) for the same memory metric without explicit relationship. Other claims to cross-check against SPEC: video buffer = 30s, rrweb buffer = 10min/5000 events, user event buffer = 10min, archive delivery < 5s, sensitive data masking via input[type=password] and data-sensitive='true'."
}

View File

@@ -0,0 +1,28 @@
{
"source_path": "/home/parf/projects/work/repremium/Тз расширение фаза1.md",
"type": "SPEC",
"confidence": "high",
"manifest_override": true,
"title": "Техническое задание: Браузерное расширение для записи сессий операторов — Фаза 1 (Локальная запись + экспорт архива)",
"summary": "Technical specification for Phase 1 of a Chrome Manifest V3 browser extension that continuously records operator session video, DOM snapshots, and event logs locally and exports them as a ZIP archive on demand.",
"scope": [
"Chrome Extension Manifest V3",
"Service Worker / Background Script",
"Tab video capture (chrome.tabCapture)",
"DOM recording via rrweb",
"User event logging (Content Script)",
"ZIP archive packaging (JSZip)",
"File download via chrome.downloads",
"Popup UI for archive export",
"Screenshot capture (chrome.tabs.captureVisibleTab)",
"Ring buffer video (last 30 seconds)",
"DOM/event buffer (last 10 minutes)",
"Sensitive data masking (passwords, data-sensitive)",
"Manifest permissions configuration",
"Phase 1 acceptance criteria"
],
"cross_refs": [],
"locked": false,
"precedence": 0,
"notes": "Manifest-declared SPEC; document contains explicit technical contracts (codec/bitrate, API surface, manifest permissions, archive layout, meta.json schema, event log JSON schema), engineering constraints (WebM header retention, Service Worker keepalive, rrweb buffer cap of 5000 events, 50MB RAM ceiling), and Phase 1 acceptance criteria. Explicit Phase 1 vs Phase 2 scope boundary documented in section 9. Russian-language source; scope translated to English while preserving technical identifiers."
}