NC Agent Ops Board

Агент: довести ВСЕ 41 сценарий до зелёнки с live-proof таблицей

Делает

Lead holding after QA reject

Адрес

QA отдел

Ждет

owner acceptance only if owner wants final closure

От тебя: Но ты же должен был добить все сценарии, не только ядро; 41 сценарий, все до зелёнки?

Следующий шаг: Wait for owner OK; do not run Cloud Build/prod deploy/live proof without it.

Как я понял: AGENT-0518 доказал только wave1: 28/41 executable and 13 beta/⚡ remained; later 0531/0535/0536/0537 closed core delivery/detect gaps, but full 41/41 live green matrix is not yet recorded. This ticket is the owner-visible final gate.

Invite magic link must accept and open the shared notebook, not empty onboarding

Делает

Opus agent (auto-dispatch)

Адрес

tmux agent

Ждет

Build/deploy stop by codex-lead-live 2026-06-28T12:32Z: not a valid Build Candidate. Card has no-build/no-deploy labels, postQA timed out, owner live reject remains, and agentFix says STILL needs live two-account browser proof. Need manual live two-account invite proof before any acceptance/build decision.

От тебя: 180: отправил себе invite, получил magic link; открыл — попал в onboarding, нажал пропустить регистрацию — пустая тетрадь, а не приглашенная. Это не похоже на правильную best-practice логику.

Следующий шаг: Run manual live two-account browser proof: invitee magic link must land in shared notebook, not empty onboarding. No build/deploy from this stale Build Candidate.

Как я понял: AUTH-0180 fixed the public host/session part, but accepted proof was too narrow. Invite magic links must preserve invite/notebook context through magic-login, onboarding/legal gates, and skip/finish actions, then open the shared notebook with correct role scope.

P0: награды боя подделываются — /api/economy/earn и /api/game/xp/add верят клиентской строке (coins/XP без пруфа боя)

Делает

Opus (fleet-remap) (harness auto-dispatch)

Адрес

tmux agent

Ждет

наблюдение

От тебя:

Следующий шаг: 🔄 QA идёт на малинке прямо сейчас. Если завис >5мин без вердикта — SSH-сокет мог оборваться (EPIPE на длинном орб-прогоне), будет перезапущен.

Local integration batch for accepted CHAT/SEC/TEAM/activity/UI candidates

Делает

Lead accepted bounded QA reproof v4-dc20d278e

Адрес

Адреса нет: нужен новый tmux агент

Ждет

No owner action. Lead accepted bounded QA reproof on live v4-dc20d278e; optional live two-editor write/seal round-trip can be run only if owner wants extra product proof.

От тебя: Build Candidate queue is almost empty; Lead should decide the next grouped build batch.

Следующий шаг: Closed after Lead acceptance. Reopen only for a new live regression or if owner explicitly requests the optional live two-editor write/seal closure.

Как я понял: Run a local-only BUILD-0016 integration steward for 12 already accepted candidates. This is not Cloud Build, not Pi/prod deploy, and not an owner action request.

Риск: origin/main is 7266de5d and prior activity proof base a63ebdd51 is not an ancestor of origin/main; steward must verify ancestry and stop on unsafe replay/conflicts instead of guessing.

9091 timeout hotpatch must be landed into the next clean build artifact

Делает

canonical branch: agent/build-0018-voice9091-clean-artifact-opus-20260605

Адрес

Lead build candidate

Ждет

No owner action. BUILD-0018 is deployed in v4-dc20d278e and 9091 post-deploy sentinel passed.

От тебя: Нужно повесить 9091 hotpatch в ожидание сборки, синхронизировать ветку с Lead Live/Build steward, чтобы следующий clean deploy не снёс телефонные timeout-правки.

Следующий шаг: No build action. If owner/API Codex requests full phone acceptance, run supervised 9091 call; source/deploy preservation gate is green.

Как я понял: The live Pi 9091 timeout fix is currently hotpatched and survives reboot, but app clean deploy can overwrite the standalone chunks and SIP/gateway deploy can overwrite gateway files. Treat this as a build candidate/gate: source changes must be landed into the branch used for the next clean app artifact and gateway source before the next deploy is accepted.

Риск: If a clean app artifact is deployed from an older commit, note-clone-3010 can lose either the 210s wait or the raw-transcript-first Lead Live payload; 9091 may again return queued/busy or create plausible but incomplete tickets from summarized speech.

Owner-approved web build/deploy batch for AUTH-0201, Bug-4, and accepted build candidates

Делает

Lead-as-build-steward: codex-lead-live

Адрес

Build steward / Lead Live

Ждет

No owner action. BUILD-0206 web-only batch is deployed green on nb.wool2.online. Full authenticated magic-link invite/open-notebook proof was not simulated with live tokens; safe public/fail-closed smoke and source/unit QA are recorded.

От тебя: теперь работа 0, 20 в паркинг и ждут билда 3 по карточкам.. это мнорм? все что можно было сделать без билда сделали как я понял дальше билд? если так тогда приступайте и там твой сип тоже проконтролируй

Следующий шаг: Keep monitoring board; requeue Focus Round 2 separately after this terminal BUILD-0206 result. Do not mix Focus/9091/SIP gateway work into BUILD-0206.

Как я понял: Owner authorized a safe web build/deploy path after audit. Scope is web runtime only: AUTH-0201 + UIUX-0190/Bug-4 integration + accepted build candidates. Explicitly exclude Focus Round 2, VOICE-0182/9091 proof work, and any SIP gateway deploy/copy. Preserve VOICE-0205 SIP markers before and after.

Риск: Combining auth + UI + accepted candidates reduces deploy churn but increases blast radius. Focus and 9091 must stay out of this batch. SIP gateway must not be overwritten.

Clean Bug-4 livebase replay for BUILD-0206 without rolling back Add Source / Media Import live behavior

Делает

Opus livebase replay worker

Адрес

Адреса нет: нужен новый tmux агент

Ждет

No owner action. BUILD-0207 replay is deployed via BUILD-0206 web runtime; authenticated full-app browser E2E remains residual, not a deploy blocker.

От тебя: если так тогда приступайте и там твой сип тоже проконтролируй

Следующий шаг: Monitor live regressions only; no separate BUILD-0207 worker/build/deploy.

Как я понял: Owner OK for a safe web build path was received, but Cloud Build is blocked because accepted Bug-4 work is not clean on the current live web base dc20d278. This ticket is the bounded Opus replay task needed before BUILD-0206 can be retried. It is not a build/deploy ticket.

Риск: Incorrect conflict resolution could roll back current live Add Source / Media Import behavior. This task is intentionally separated from Cloud Build and deploy.

Chat must not claim document creation without actual tool/write proof

Делает

Lead accepted bounded QA reproof v4-dc20d278e

Адрес

QA отдел

Ждет

наблюдение

От тебя: Owner does not confirm CHAT-0172: /Users/poolpooly/Downloads/chat-json-2026-06-05T22-17-34-571Z.json shows chat claims document creation/opening for "Меркурий факты.md", but no document exists; notes may be created, docs are not.

Следующий шаг: Recheck by 2026-06-06T14:00Z or when an explicit Mercury live proof gate opens. If scheduled, dispatch bounded QA to prove real document/source creation or honest refusal before any creation/opening claim. No Cloud Build/Pi/SIP/prod from this ticket.

Как я понял: Fresh owner export has user request "создай доку про Меркурий факты", clarification "планету", assistant claim "I have created the document \"Меркурий факты.md\"", user "открой его", assistant claim "Opening document \"Меркурий факты.md\"…". Owner reports no document exists; export has no visible tool/write evidence.

Риск: User loses trust and may rely on phantom documents; regression likely after tool-call guard/mirror changes.

Global Ask AI must answer global notebook queries or show bounded failure states

Делает

Claude Opus Bug-4 Global Ask AI implementation owner

Адрес

tmux implementation agent

Ждет

наблюдение

От тебя:

Следующий шаг: post-deploy QA (live): Ask AI scope/timeout/ошибки на live.

Как я понял: Global Ask AI may be a real all-notebook RAG/inventory chat, but owner sees it spin without answering and the UI duplicates account affordances. Treat as a P0 product/spec gate before UI polish: prove scope and answer path or present bounded failure states.

MIG-01: извлечь translations (база+152 sweep) → messages/<locale>.json (102 локали)

Делает

Opus (native) (harness auto-dispatch)

Адрес

tmux agent

Ждет

Build/deploy steward for owner-approved CODE60 wave1 MIG-01. Accepted source/data proof: commit 2efcfc7b6a, report 2dd118a154, 102 messages/<locale>.json, en=4250 leaf keys, JSON parse OK. Deploy only through explicit CODE60 wave1 owner-approved build path; no SIP/native/secrets.

От тебя:

Следующий шаг: Build/deploy gate for owner-approved CODE60 wave1 MIG-01; MIG-02 can continue local-only in parallel.

MIG-02: подключить next-intl (App Router/RSC): request.ts, provider, locale-detection, lazy per-locale

Делает

Opus (native) (harness auto-dispatch)

Адрес

tmux agent

Ждет

Post-deploy browser verify needed: build-steward marked CODE60 deployed at 538cf9ed1f5cb0b050cff8860991555c4d4dffeb; verify-gate found marker 'accept-language' in LIVE bundle + health-green, but Browser_check=SKIP/no spec, so needs-browser-verify remains. Codex Lead did not run prod deploy/Cloud Build or independently confirm Pi runtime.

От тебя:

Следующий шаг: 🔄 QA идёт на малинке прямо сейчас. Если завис >5мин без вердикта — SSH-сокет мог оборваться (EPIPE на длинном орб-прогоне), будет перезапущен.

MIG-03: мигрировать 196 файлов custom useTranslation/t() → next-intl useTranslations/getTranslations

Делает

Opus (native) (harness auto-dispatch)

Адрес

tmux agent

Ждет

Build/deploy steward: CODE60 MIG-03 backbone variant accepted per owner-approved label mig03-backbone-accepted-variantA-owner-approved. Build only the safe backbone increment ca98c586d1/253d527a1b in separate i18n basket; literal 196 native next-intl callsite rewrite remains split/blocked by catalog-shape + client live-language constraints and must not be mixed into unrelated hotfix/showfix train. No manual prod deploy from Lead Live.

От тебя:

Следующий шаг: 🔄 QA идёт на малинке прямо сейчас. Если завис >5мин без вердикта — SSH-сокет мог оборваться (EPIPE на длинном орб-прогоне), будет перезапущен.

MIG-04: убрать translations.ts + 152 .generated.ts из статик-графа (JSON = source of truth)

Делает

Opus (native) (harness auto-dispatch)

Адрес

tmux agent

Ждет

Build/deploy steward: Lead accepted CODE60 MIG-04 separate i18n basket at commit 96c6e1ccd4 (implementation commits 4a8004d5b5, ab17cbadd3, 96ec199742). Owner/backup-Opus hold is lifted after owner spot-check of MIG-02/03 ~10 languages. Local Lead validation rerun: serverDictionaryJsonParity.test.ts 4/4 PASS; scenarioI18n*.test.ts 128/128 PASS; tsc -p tsconfig.code60-mig04.json exit 0; static-import-hygiene.test.ts 513/515 with only pre-existing SettingsModal Slice2 failures. Build/deploy only as separate i18n basket; do not mix with showfix/studio train. After deploy, owner re-spot-check locales required.

От тебя:

Следующий шаг:

9091 Lead Live must use owner Telegram delivery proof, not notify-lead.sh

Делает

Lead source accepted; build train pending

Адрес

Кодекс под капотом

Ждет

Owner: one controlled 9091 call now; ask Lead Live to send owner Telegram, then report delivered/not delivered. API Codex must review logs before final acceptance.

От тебя: During the 22:23 9091 call owner asked to send parked-ticket status to Telegram; phone/Lead said it was sent, but owner did not receive it.

Следующий шаг: OWNER PROOF WINDOW: owner should call 9091 now once, ask Lead Live to send a Telegram message to owner, then report whether it arrived. After call, API Codex reviews logs for notify-owner.sh DELIVERED/message_id and no notify-lead.sh path before Lead final acceptance.

Как я понял: Live tmux proof shows Lead Live ran scripts/notify-lead.sh for an owner Telegram request. That is the lead/self notification path, not owner delivery. Owner-facing delivery must use board/notify-owner.sh and may be spoken as sent only after ok:true plus message_id. || [FROM API CODEX 11.06] Хендофф принят Opus: ветка api-codex/voice-0447-9091-guards (8e87353, база=текущий прод 7ec0ea1), 2 файла (queryLeadRuntimeStatus + тест 9/9): гард sudo/секретов с телефона до enqueue, запрет notify-lead.sh как owner-доставки, «отправлено» только после DELIVERED+message_id. ПРИЁМКА: НЕ source-only — после деплоя API Codex делает контрольный 9091-звонок (чек-лист в reports/TO-OPUS-PARENT-COMMS-0447-BUILD-HANDOFF-20260611.md).

Риск: False sent confirmation breaks owner trust and can hide urgent work status. notify-lead.sh self-echo looks successful in tmux but does not deliver to owner.

Telegram /call must not reject owner-mode Access links as shared mode

Делает

Lead accepted clean branch; web build/deploy gated

Адрес

Уточнить

Ждет

Live owner Telegram /call proof after COMMS-0567.

От тебя: Я делал бар код сам себе и убрал галочку Гостевого доступа, зашел через ссылку в телегу и он говорит мол я не хозяин звонить не положено. Может то что агенты не могут позвонить связано с этим же?

Следующий шаг: Post-deploy live proof: owner-mode Access link Guest disabled -> Telegram /start -> success copy says /call is available -> /call reaches personal call/callback path. Then separately verify real shared/guest link still returns shared_mode_required.

Как я понял: The /call guard is correct for real shared chats, but owner-mode access links must write lockedScope=false/sharedGuest=false. If the owner private Telegram binding is stuck in shared mode, callback QA for VOICE-0558 can fail before the callback worker is reached.

DEPLOY Meeting Room 1045/1046 app-only owner OK: browser/WebRTC first lane + shared SIP/Telegram MeetingLeg lifecycle

Делает

Pi-QA на малинке (ssh -p 2046 pi@mailhub.duckdns.org · логи /tmp/postqa-pi.log)

Адрес

QA отдел

Ждет

наблюдение

От тебя: API Codex

Следующий шаг: 🔄 QA идёт на малинке прямо сейчас. Если завис >5мин без вердикта — SSH-сокет мог оборваться (EPIPE на длинном орб-прогоне), будет перезапущен.

Как я понял: Owner OK is for app-only deployment of the already local-proven Meeting Room 1045/1046 browser + shared lifecycle package. Build from clean worktree based on live v4-6e77a6f5 and deploy only commit 4a4a044422. Do not include dirty local note-clone changes or unrelated Studio/Orb/Voice work.

Focus Mode recovery: real Workshop mode, not plain hidden-sidebar chat

Делает

tmux:qa-postqa-browser-focus-access-opus-20260604

Адрес

Lead coordination

Ждет

No owner action on this mechanical/post-QA ticket; product acceptance now tracked in FOCUS-0159.

От тебя: Live Focus Mode still looks like a plain chat; old tickets claimed more than the product actually delivers.

Следующий шаг: Keep mechanical post-QA record closed. Do not cite as owner product acceptance; mockup/product acceptance is now FOCUS-0159..0164.

Как я понял: Parent recovery ticket for Focus Mode. Reconcile prior WEB-0069/0101/0122/0123/0124 claims against the legacy Workshop design canon and owner live evidence. Do not accept children by grep/source/unit proof.

Риск: Do not accept Focus recovery from source/unit/legacy-demo proof. Require live runtime screenshots and trace.