Prepare inherited ignore paths and file-only rules once per directory during fallback searches. Preserve nested overrides, directory semantics, rescanning, cancellation and result limits. Cover filename and content searches without ripgrep.
Prepare inherited ignore paths and file-only rules once per directory during fallback searches. Preserve nested overrides, directory semantics, rescanning, cancellation and result limits. Cover filename and content searches without ripgrep.
Accept optional text titles in visualization references, escape preview labels, and retain strict shape, path and sandbox validation. Cover streaming, invalid titles and interactive previews after reopening.
Accept optional text titles in visualization references, escape preview labels, and retain strict shape, path and sandbox validation. Cover streaming, invalid titles and interactive previews after reopening.
Preserve the PR's decoded-colon check for ambiguous prose, while masking explicit authentication fields even when credentials are invalid or truncated. Include proxy authorization in structured redaction and cover the logger delivery boundary.
Verified 72 related cases under Electron and the exact PR tree main typecheck. New privacy regressions fail before the repair.
Retain the last visible user-message boundary for active reply snapshots and restore replies after that boundary. Preserve newer messages with equal timestamps, viewport position and runtime polling order. Add renderer, bus and native recovery regressions.
Retain the last visible user-message boundary for active reply snapshots and restore replies after that boundary. Preserve newer messages with equal timestamps, viewport position and runtime polling order. Add renderer, bus and native recovery regressions.
Share the existing worker cleanup barrier across live projections and turn navigation. Reject new persisted-history admission during cleanup, preserve wait-and-succeed behavior for view recovery, and keep source history intact. Cover cold and warm lanes, repeated close, rejection and explicit recovery. Include the existing history-owner cleanup in desktop quit and relaunch, while retaining target lifecycle hooks.
Share the existing worker cleanup barrier across live projections and turn navigation. Reject new persisted-history admission during cleanup, preserve wait-and-succeed behavior for view recovery, and keep source history intact. Cover cold and warm lanes, repeated close, rejection and explicit recovery. Include the existing history-owner cleanup in desktop quit and relaunch, while retaining target lifecycle hooks.
Share the existing worker cleanup barrier across live projections and turn navigation. Reject new persisted-history admission during cleanup, preserve wait-and-succeed behavior for view recovery, and keep source history intact. Cover cold and warm lanes, repeated close, rejection and explicit recovery.
Validate file availability and kind before dispatching a native preview. Keep unsupported-file guidance, folder reveal, dismissal and focus in the owner window, with unit and Electron coverage.
Validate file availability and kind before dispatching a native preview. Keep unsupported-file guidance, folder reveal, dismissal and focus in the owner window, with unit and Electron coverage.
Keep the result list at its start when delayed categories or chat summaries arrive. Preserve anchoring after the user scrolls. Add deterministic and native renderer regressions.
Keep the result list at its start when delayed categories or chat summaries arrive. Preserve anchoring after the user scrolls. Add deterministic and native renderer regressions.
sanitizeLogTextForUpload masked any "basic <word>" as "Basic ***", so
ordinary log text such as "falling back to basic retrieval" lost the
word after "basic". Basic credentials are base64 of "user-id:password"
(RFC 7617), so only mask a token that decodes to something with a colon.
Resolve the existing real bundled executable independently of tool runtime mocks. All eight affected recovery cases fail before and pass after the repair with system FFmpeg absent from PATH; media and recovery assertions remain intact. Fixed-range postcheck passes. Cross-platform Actions are pending and are not counted as acceptance.
Resolve the real bundled executable independently of mocked tool runtime paths. Preserve real media generation and all recovery oracles when the host PATH has no FFmpeg.
Validation: the restricted-PATH negative control failed all eight affected cases before the repair; all eight pass after it with zero log findings.
Retain complete task recovery, recurring scheduling, search, Agent and video workflows, with public-edition boundaries and reviewed upstream changes.
Pinned-range postcheck and affected local verification pass. Cross-platform Actions remain in progress at merge time and are not reported as passed. The initial-overhead, browser GPU log and platform/performance findings remain explicitly open; this merge does not grant release acceptance.
Prompt audit:
- Keep: The previously confirmed behavior and its canonical placement. Type: Hard constraint. Why: Preserve execution authority, routing and recovery without duplicated resident procedure.
- Drop: Superseded overlapping guidance and generated duplicate entries. Type: Display only. Why: Preserve one canonical resource owner.
Prompt confirmation:
Confirmed-by: Requester, precise final-state proposal followed by explicit PR/merge instruction.
Scope: Existing confirmed behavior, resource placement and actors; no optional prompt optimization.
Retain upstream documentation, vendored byte pins and native test coverage. Preserve newer selection ownership, two-sided Library revision safety, cache receipts and final-source guidance. Update older transfer fixtures to verify both recoverable revisions and actual file bytes.
Validation: 127 affected cases passed, one platform skip. Initial six fixture/old-contract failures retained. Production and builtin resource bytes match the reviewed integration parent.
Prompt audit:
- Keep: Confirmed execution and guidance behavior at existing owners. Type: Hard constraint. Why: Main carries older overlapping content, with no additional resident responsibility.
- Drop: Duplicate generated guide entries and superseded overlapping guidance. Type: Display only. Why: Existing canonical resources already provide the confirmed behavior once.
Prompt confirmation:
Confirmed-by: Requester, after reviewing the precise final-state behavior proposal.
Scope: Preserve the previously confirmed final behavior, placement and actors while integrating main; no new instruction.
Preserve the reviewed user-facing behavior, public-edition boundaries and owning regression coverage.
Prompt audit: Keep existing permission, ownership and recovery contracts at their current tool, runtime or test owner (Hard constraint). No separate resident instruction is added. Drop excluded hosted-only branches; retain shared side effects and tests. No optional prompt rewrite.
Prompt confirmation: The requester confirmed the exact proposed final behaviors and existing resource placements by directing that the primary implementation be followed, then explicitly requested this PR and merge. Preserve that confirmed scope only.
- Keep: The behavior and placement detailed in the audit above. Type: Hard constraint. Why: Preserve its existing canonical owner without duplicated resident instructions.
- Drop: Superseded overlapping wording and excluded hosted-only behavior. Type: Hard constraint. Why: Preserve the confirmed public capability and authority boundary.
Confirmed-by: Requester, exact final-state proposal and subsequent delivery request.
Scope: The previously confirmed final behavior and existing placement described above; no optional prompt rewrite.
Preserve the reviewed user-facing behavior, public-edition boundaries and owning regression coverage.
Prompt audit: Keep existing permission, ownership and recovery contracts at their current tool, runtime or test owner (Hard constraint). No separate resident instruction is added. Drop excluded hosted-only branches; retain shared side effects and tests. No optional prompt rewrite.
Prompt confirmation: The requester confirmed the exact proposed final behaviors and existing resource placements by directing that the primary implementation be followed, then explicitly requested this PR and merge. Preserve that confirmed scope only.
- Keep: The behavior and placement detailed in the audit above. Type: Hard constraint. Why: Preserve its existing canonical owner without duplicated resident instructions.
- Drop: Superseded overlapping wording and excluded hosted-only behavior. Type: Hard constraint. Why: Preserve the confirmed public capability and authority boundary.
Confirmed-by: Requester, exact final-state proposal and subsequent delivery request.
Scope: The previously confirmed final behavior and existing placement described above; no optional prompt rewrite.
Preserve the reviewed user-facing behavior, public-edition boundaries and owning regression coverage.
Prompt audit: Keep existing permission, ownership and recovery contracts at their current tool, runtime or test owner (Hard constraint). No separate resident instruction is added. Drop excluded hosted-only branches; retain shared side effects and tests. No optional prompt rewrite.
Prompt confirmation: The requester confirmed the exact proposed final behaviors and existing resource placements by directing that the primary implementation be followed, then explicitly requested this PR and merge. Preserve that confirmed scope only.
- Keep: The behavior and placement detailed in the audit above. Type: Hard constraint. Why: Preserve its existing canonical owner without duplicated resident instructions.
- Drop: Superseded overlapping wording and excluded hosted-only behavior. Type: Hard constraint. Why: Preserve the confirmed public capability and authority boundary.
Confirmed-by: Requester, exact final-state proposal and subsequent delivery request.
Scope: The previously confirmed final behavior and existing placement described above; no optional prompt rewrite.
Preserve the reviewed user-facing behavior, public-edition boundaries and owning regression coverage.
Prompt audit: Keep existing permission, ownership and recovery contracts at their current tool, runtime or test owner (Hard constraint). No separate resident instruction is added. Drop excluded hosted-only branches; retain shared side effects and tests. No optional prompt rewrite.
Prompt confirmation: The requester confirmed the exact proposed final behaviors and existing resource placements by directing that the primary implementation be followed, then explicitly requested this PR and merge. Preserve that confirmed scope only.
- Keep: The behavior and placement detailed in the audit above. Type: Hard constraint. Why: Preserve its existing canonical owner without duplicated resident instructions.
- Drop: Superseded overlapping wording and excluded hosted-only behavior. Type: Hard constraint. Why: Preserve the confirmed public capability and authority boundary.
Confirmed-by: Requester, exact final-state proposal and subsequent delivery request.
Scope: The previously confirmed final behavior and existing placement described above; no optional prompt rewrite.
Preserve the reviewed user-facing behavior, public-edition boundaries and owning regression coverage.
Prompt audit: Keep dependency-aware production horizon, current-draft recovery, segment/whole preview and final delivery gates (Hard constraint, existing VideoStudio workflow and on-demand stage Skills). Keep bounded plan correction and AUTO/art-direction handoff guidance (Pitfall, owning plan and assembly routes), plus user-owned provider boundaries in existing feedback. Keep design examples in on-demand references. Drop superseded wording replaced by the same owner; no new system injection or duplicated schema in resident prose.
Prompt confirmation: The requester confirmed the exact proposed final behaviors and existing resource placements by directing that the primary implementation be followed, then explicitly requested this PR and merge. Preserve that confirmed scope only.
- Keep: The behavior and placement detailed in the audit above. Type: Hard constraint. Why: Preserve its existing canonical owner without duplicated resident instructions.
- Drop: Superseded overlapping wording and excluded hosted-only behavior. Type: Hard constraint. Why: Preserve the confirmed public capability and authority boundary.
Confirmed-by: Requester, exact final-state proposal and subsequent delivery request.
Scope: The previously confirmed final behavior and existing placement described above; no optional prompt rewrite.
Preserve the reviewed user-facing behavior, public-edition boundaries and owning regression coverage.
Prompt audit: Keep executable-work completion, necessary confirmation and sensitive-input boundaries (Hard constraint, resident Commander routing). Keep name/workflow/profile identity; drop display descriptions from execution identity (Display only, catalog owner). Keep same-outcome recurring suggestions and reminder-only requests (Hard constraint, existing turn guidance). Keep project operations separate with legacy to-do authority (Hard constraint, host catalog). Keep guide facts and creator procedures on demand in their existing Skills with one English discovery description; drop duplicated localized metadata and mirrored procedure. Resident routing must precede Skill selection; no optional prompt optimization.
Prompt confirmation: The requester confirmed the exact proposed final behaviors and existing resource placements by directing that the primary implementation be followed, then explicitly requested this PR and merge. Preserve that confirmed scope only.
- Keep: The behavior and placement detailed in the audit above. Type: Hard constraint. Why: Preserve its existing canonical owner without duplicated resident instructions.
- Drop: Superseded overlapping wording and excluded hosted-only behavior. Type: Hard constraint. Why: Preserve the confirmed public capability and authority boundary.
Confirmed-by: Requester, exact final-state proposal and subsequent delivery request.
Scope: The previously confirmed final behavior and existing placement described above; no optional prompt rewrite.
Preserve the reviewed user-facing behavior, public-edition boundaries and owning regression coverage.
Prompt audit: Keep existing permission, ownership and recovery contracts at their current tool, runtime or test owner (Hard constraint). No separate resident instruction is added. Drop excluded hosted-only branches; retain shared side effects and tests. No optional prompt rewrite.
Prompt confirmation: The requester confirmed the exact proposed final behaviors and existing resource placements by directing that the primary implementation be followed, then explicitly requested this PR and merge. Preserve that confirmed scope only.
- Keep: The behavior and placement detailed in the audit above. Type: Hard constraint. Why: Preserve its existing canonical owner without duplicated resident instructions.
- Drop: Superseded overlapping wording and excluded hosted-only behavior. Type: Hard constraint. Why: Preserve the confirmed public capability and authority boundary.
Confirmed-by: Requester, exact final-state proposal and subsequent delivery request.
Scope: The previously confirmed final behavior and existing placement described above; no optional prompt rewrite.
Preserve the reviewed user-facing behavior, public-edition boundaries and owning regression coverage.
Prompt audit: Keep existing permission, ownership and recovery contracts at their current tool, runtime or test owner (Hard constraint). No separate resident instruction is added. Drop excluded hosted-only branches; retain shared side effects and tests. No optional prompt rewrite.
Prompt confirmation: The requester confirmed the exact proposed final behaviors and existing resource placements by directing that the primary implementation be followed, then explicitly requested this PR and merge. Preserve that confirmed scope only.
- Keep: The behavior and placement detailed in the audit above. Type: Hard constraint. Why: Preserve its existing canonical owner without duplicated resident instructions.
- Drop: Superseded overlapping wording and excluded hosted-only behavior. Type: Hard constraint. Why: Preserve the confirmed public capability and authority boundary.
Confirmed-by: Requester, exact final-state proposal and subsequent delivery request.
Scope: The previously confirmed final behavior and existing placement described above; no optional prompt rewrite.
Preserve the reviewed user-facing behavior, public-edition boundaries and owning regression coverage.
Prompt audit: Keep existing permission, ownership and recovery contracts at their current tool, runtime or test owner (Hard constraint). No separate resident instruction is added. Drop excluded hosted-only branches; retain shared side effects and tests. No optional prompt rewrite.
Prompt confirmation: The requester confirmed the exact proposed final behaviors and existing resource placements by directing that the primary implementation be followed, then explicitly requested this PR and merge. Preserve that confirmed scope only.
- Keep: The behavior and placement detailed in the audit above. Type: Hard constraint. Why: Preserve its existing canonical owner without duplicated resident instructions.
- Drop: Superseded overlapping wording and excluded hosted-only behavior. Type: Hard constraint. Why: Preserve the confirmed public capability and authority boundary.
Confirmed-by: Requester, exact final-state proposal and subsequent delivery request.
Scope: The previously confirmed final behavior and existing placement described above; no optional prompt rewrite.
Preserve the reviewed user-facing behavior, public-edition boundaries and owning regression coverage.
Prompt audit: Keep existing permission, ownership and recovery contracts at their current tool, runtime or test owner (Hard constraint). No separate resident instruction is added. Drop excluded hosted-only branches; retain shared side effects and tests. No optional prompt rewrite.
Prompt confirmation: The requester confirmed the exact proposed final behaviors and existing resource placements by directing that the primary implementation be followed, then explicitly requested this PR and merge. Preserve that confirmed scope only.
- Keep: The behavior and placement detailed in the audit above. Type: Hard constraint. Why: Preserve its existing canonical owner without duplicated resident instructions.
- Drop: Superseded overlapping wording and excluded hosted-only behavior. Type: Hard constraint. Why: Preserve the confirmed public capability and authority boundary.
Confirmed-by: Requester, exact final-state proposal and subsequent delivery request.
Scope: The previously confirmed final behavior and existing placement described above; no optional prompt rewrite.
Preserve the reviewed user-facing behavior, public-edition boundaries and owning regression coverage.
Prompt audit: Keep existing permission, ownership and recovery contracts at their current tool, runtime or test owner (Hard constraint). No separate resident instruction is added. Drop excluded hosted-only branches; retain shared side effects and tests. No optional prompt rewrite.
Prompt confirmation: The requester confirmed the exact proposed final behaviors and existing resource placements by directing that the primary implementation be followed, then explicitly requested this PR and merge. Preserve that confirmed scope only.
- Keep: The behavior and placement detailed in the audit above. Type: Hard constraint. Why: Preserve its existing canonical owner without duplicated resident instructions.
- Drop: Superseded overlapping wording and excluded hosted-only behavior. Type: Hard constraint. Why: Preserve the confirmed public capability and authority boundary.
Confirmed-by: Requester, exact final-state proposal and subsequent delivery request.
Scope: The previously confirmed final behavior and existing placement described above; no optional prompt rewrite.
Preserve the reviewed user-facing behavior, public-edition boundaries and owning regression coverage.
Prompt audit: Keep existing permission, ownership and recovery contracts at their current tool, runtime or test owner (Hard constraint). No separate resident instruction is added. Drop excluded hosted-only branches; retain shared side effects and tests. No optional prompt rewrite.
Prompt confirmation: The requester confirmed the exact proposed final behaviors and existing resource placements by directing that the primary implementation be followed, then explicitly requested this PR and merge. Preserve that confirmed scope only.
- Keep: The behavior and placement detailed in the audit above. Type: Hard constraint. Why: Preserve its existing canonical owner without duplicated resident instructions.
- Drop: Superseded overlapping wording and excluded hosted-only behavior. Type: Hard constraint. Why: Preserve the confirmed public capability and authority boundary.
Confirmed-by: Requester, exact final-state proposal and subsequent delivery request.
Scope: The previously confirmed final behavior and existing placement described above; no optional prompt rewrite.
Preserve the reviewed user-facing behavior, public-edition boundaries and owning regression coverage.
Prompt audit: Keep existing permission, ownership and recovery contracts at their current tool, runtime or test owner (Hard constraint). No separate resident instruction is added. Drop excluded hosted-only branches; retain shared side effects and tests. No optional prompt rewrite.
Prompt confirmation: The requester confirmed the exact proposed final behaviors and existing resource placements by directing that the primary implementation be followed, then explicitly requested this PR and merge. Preserve that confirmed scope only.
- Keep: The behavior and placement detailed in the audit above. Type: Hard constraint. Why: Preserve its existing canonical owner without duplicated resident instructions.
- Drop: Superseded overlapping wording and excluded hosted-only behavior. Type: Hard constraint. Why: Preserve the confirmed public capability and authority boundary.
Confirmed-by: Requester, exact final-state proposal and subsequent delivery request.
Scope: The previously confirmed final behavior and existing placement described above; no optional prompt rewrite.
Preserve the reviewed user-facing behavior, public-edition boundaries and owning regression coverage.
Prompt audit: Keep existing permission, ownership and recovery contracts at their current tool, runtime or test owner (Hard constraint). No separate resident instruction is added. Drop excluded hosted-only branches; retain shared side effects and tests. No optional prompt rewrite.
Prompt confirmation: The requester confirmed the exact proposed final behaviors and existing resource placements by directing that the primary implementation be followed, then explicitly requested this PR and merge. Preserve that confirmed scope only.
- Keep: The behavior and placement detailed in the audit above. Type: Hard constraint. Why: Preserve its existing canonical owner without duplicated resident instructions.
- Drop: Superseded overlapping wording and excluded hosted-only behavior. Type: Hard constraint. Why: Preserve the confirmed public capability and authority boundary.
Confirmed-by: Requester, exact final-state proposal and subsequent delivery request.
Scope: The previously confirmed final behavior and existing placement described above; no optional prompt rewrite.
Reuse the standalone closing-line matcher from #163 across skill reading, quality validation, and recycle previews. Keep scalar values containing dashes intact and reject unterminated headers. Add file validation and real import/write-back and recycle preview regressions.
Preserve public local behavior and recovery with focused regression coverage. Keep the existing open-source provider, API-key and hosted-feature boundaries.
Allow interrupted-run recovery to skip malformed JSONL records while retaining strict I/O failure handling. Readable damaged transcripts now produce the missing interruption notices and settle stale running state; missing or short source reads remain retryable. Preserve the existing storage index and append repairs.
Validation: the torn-transcript recovery and strict-I/O regression fail against the previous runtime. The complete affected storage, strict readers, indexes, conversation recovery and message edit suites pass after repair, including visible interruption notices, cleared journals, parallel actors, write failure, repeated startup and short reads. Main/core-agent typechecks and startup smoke pass. No account, provider, prompt, dependency or cloud synchronization capability changes.
Preserve public local behavior and recovery with focused regression coverage. Keep the existing open-source provider, API-key and hosted-feature boundaries.
Exclude files owned by live user tasks from the pending attachment pool until their existing cancellation or history lifecycle releases them. Keep independent drafts, attachment limits, re-selection, queued edits, blocked work and restart recovery intact.
Validation: three attachment regressions fail before the repair, and a real Electron navigation reproduction restores a queued attachment incorrectly before this fix. Owning attachment, task-board, bus and renderer suites pass after repair, alongside focused Electron navigation, reload, edit and cancellation journeys. Main/core-agent and E2E typechecks pass. No cloud synchronization, account or hosted feature is introduced.
Orkas