Files
mokosh/.planning/intel/classifications/README-a1b2c3d4.json

29 lines
1.7 KiB
JSON

{
"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'."
}