Skip to content

fix(skill-view): record a view's source agent before its sidecar is deleted - #16073

Merged
bolichen97 merged 2 commits into
mainfrom
fix/skill-view-sidecar-ledger
Oct 3, 2026
Merged

bolichen97 merged 2 commits into
mainfrom
fix/skill-view-sidecar-ledger

Conversation

@bolichen97

@bolichen97 bolichen97 commented Oct 2, 2026 •

Copy link
Copy Markdown
Contributor

Problem / Motivation

Goal: A chat stored under a generated kirocrew-skill-view-<digest> agent name keeps resuming after the boot drain retires that view's alias and ownership sidecar.

A conversation recorded while the native skill projection was on can carry a view name as its agent. source_agent_name maps it back through the view's ownership sidecar, then the view ledger (view-sources.json). The ledger is written only at publication, and only for the aliases that run publishes, so a view published before the ledger existed has the sidecar as its only record. The boot drain deletes exactly that record:

  • the orphan-sidecar sweep (_sweep_orphan_sidecars) retires a sidecar whose alias a cleanup outside the core, or an operator, already removed;
  • the prune (_reclaim_prune_candidate) retires the alias and its sidecar together, both for an intact pair and for a re-serialized one.

None of the three paths writes the ledger first. After the next boot the stored chat is refused with Crew Member 'kirocrew-skill-view-…' is unavailable; restore it or choose a member, even though the agent it was built from is installed. A pod smoke test reproduced this on a real tree: alias removed, then drain_stale_aliases(), then the resume refused.

Why it matters

Every conversation recorded under a view name before the ledger existed stops resuming at the first boot that drains it. The refusal points at a "Crew Member" the user never created and cannot restore, so there is no way forward from the message.

Not a goal

  • Recovering mappings that a drain already deleted. Nothing else records them, and the view name is a one-way digest over values that are no longer reproducible (see Manual verification). This PR only makes the refusal say what to do.
  • Changing the ledger's bound (_VIEW_SOURCES_MAX), its format, or what the drain deletes.
  • Changing which aliases or sidecars count as reclaimable.

What changed (motivation → approach → change)

Symptom: a stored view name stops resolving once the drain runs. Root cause: every sidecar deletion drops the last record of the view's source agent without copying it into the ledger. Change: record the mapping before deleting.

  • _record_view_ledger_entries(metadata_dir, views) is now the single ledger writer. It takes alias → agent, because a retired backlog holds many views of one agent. It reuses the existing rules: the same admission, an atomic owner-only write, and no rewrite when nothing changed. Each write makes its whole batch the newest entries, including pairs the ledger already holds, so the same write cannot evict a pair whose sidecar is about to go. Past the bound (_VIEW_SOURCES_MAX), entries a sidecar still answers for go first, oldest first. After that the oldest retired names go; they stop resolving, and the loss is counted in a warning. A full ledger therefore never stops the sweep from retiring sidecars. A batch larger than the bound cannot all be held, so none of its sidecars go. _record_view_ledger (agent → alias, for a publication) delegates to it.
  • _ViewLedgerWrites keeps the ledger for the duration of one locked prune or sweep. Every path that deletes a sidecar calls it before unlinking:
    • sweep: collects its batch, records every pair in one write, then unlinks. The time budget covers the unlinks too. If the ledger refuses the write, the whole batch is kept for a later run.
    • prune, both pair paths (intact and re-serialized): retain() runs before _unlink_alias_if_unchanged. The first pair that needs recording also records the next 64 candidates' sidecars (this home only) in the same write. A drain over thousands of pairs therefore costs one write per window instead of one per pair, and a walk that reclaims nothing does no extra reads. If the ledger refuses, the alias still goes. The sidecar stays and answers for the view on its own, so a full disk or a read-only metadata directory does not stop alias reclamation. After one refused write, the rest of that prune or sweep keeps sidecars without retrying the write for each candidate. _reclaim_prune_candidate now takes the ledger as a required argument.
  • All of this runs under the publication lock that each deletion already holds.
  • Impact. This change is defensive. At the core that the internal 0.8.0.1/0.8.0.2 builds shipped, no real path stored a view name, because every recorder refuses an unresolvable name first (see the impact comment on this PR). The change keeps any stored view name resolvable through the drain.
  • For a view that nothing records, the refusal now says so and gives the remedy that works: chat_runner.unavailable_agent_message() reads "This chat was recorded under a generated skill view from an earlier version (…), and the agent it was built from is not recorded. Pick the agent for this chat again, or start a new chat." The RetiredSkillView text that the ACP spawn path raises gets the same "or start a new chat".

Backwards compatibility

Compatible. The ledger file keeps its format and its bound, and older builds read it unchanged. A deletion that would previously have happened is deferred only when the ledger write fails. _record_view_ledger keeps its signature. The only other change is the message text for a non-view name, which is identical.

Tests

  • test_resume_retired_agent_names.py::test_a_view_the_real_boot_drain_retired_still_resumes[alias-removed|pair-kept|alias-rewritten]: publishes a real view and deletes the ledger, as a pre-ledger tree would look. It then runs the real drain_stale_aliases(), asserts that the alias and the sidecar are really gone, and resumes the stored name through resolve_session_agent_bindings. Each parametrization drives one of the three deletion paths. All three FAIL on main.
  • test_skill_view_mode_recovery.py::test_the_boot_drain_records_a_backlog_in_one_ledger_write: a backlog of 7 views of one agent, half with their alias already removed. The drain retires them all with exactly 2 ledger writes (one for the prune, one for the sweep), and every name still resolves.
  • test_skill_view_mode_recovery.py::test_a_sidecar_the_ledger_cannot_take_is_kept_and_its_alias_goes[True|False] and test_a_reserialized_pair_the_ledger_cannot_take_keeps_its_sidecar: when a ledger write raises, the sidecar is kept and the alias is removed, and the name still resolves through the sidecar.
  • test_the_bound_drops_redundant_entries_then_the_oldest_retired_ones: redundant entries go first, then the oldest retired name (with a warning), new pairs are always held, and an over-bound file is trimmed.
  • test_a_batch_rewrites_its_held_pairs_so_the_bound_cannot_evict_them: a held pair in a batch is not evicted by that batch's own write, and a batch larger than the bound is refused.
  • test_a_refused_write_is_not_retried_for_every_candidate.
  • test_the_orphan_sweep_unlinks_nothing_past_its_deadline: a deadline that runs out during the ledger write stops the unlinks; the batch stays recorded.
  • test_resume_retired_agent_names.py::test_an_unrecoverable_view_tells_the_user_to_pick_again_or_start_new.
  • test_skill_view_mode_recovery.py::test_the_look_ahead_records_only_this_homes_views: one look-ahead write covers its window, and another home's view takes no ledger slot.
  • test_skill_view_mode_recovery.py::test_a_ledger_that_already_holds_the_views_is_not_rewritten: views the ledger already holds, and records with no admissible agent, cause no write.

Regression proof, with each site disabled in turn:

Mutation Result
Sweep skips the ledger 3 FAIL
Intact-pair prune skips it 3 FAIL
Re-serialized-pair prune skips it 1 FAIL
Look-ahead removed (one write per pair) the write-count test FAILs
Whole fix reverted 6 FAIL
Bound refuses new pairs instead of evicting the bound test FAILs
Batch writes only its missing pairs the batch test FAILs
No latch after a refused write the latch test FAILs
Sweep unlinks past its deadline the deadline test FAILs
A refused write keeps the alias as well the refused-write test FAILs

Gate: check_black_formatting, check_subprocess_encoding, isort, flake8 and mypy src/kiro_crew are clean (0 issues in 2046 files). The backend lane of scripts/local-gate.py passes (17499 passed, 7 skipped). Its related frontend lane could not run locally because npm authentication failed (E401). The diff touches no frontend file.

Manual verification

  • Tested on an isolated kirocrew pod tree. I published 11 real views and deleted the ledger, so the tree looked like it predated the ledger. A distribution's boot cleanup then removed only the aliases (11 aliases, 11 sidecars left), and the real drain_stale_aliases() ran after it. On the base: 0 sidecars and 0 ledger entries remained, and 0 of 11 stored names resolved through resolve_session_agent_bindings. With this branch: 0 sidecars, 11 ledger entries, and 11 of 11 resolved to their source agent.
  • Checked whether a mapping that was already deleted can be recovered. It cannot. The session record's template_id and selection_name both hold the view name. kiro-cli's sessions/cli/<sid>.json stores only session_state.agent_name, which is the alias. Lease records hold alias names only. The digest covers the agent, the home, the source path and the full view, including MCP env values that changed on every launch at the time, so it cannot be recomputed from installed agents.

Related Issues

Closes #16545

Follows #16024 and #16033, which map a stored view name back through source_agent_name. The deleting sweep came from #15150 (via #15295).

Pattern harvest

Rule candidate: review-prompt
Pattern: "deleting a record that a fallback resolver reads, without first writing the fallback": every path that unlinks a file which a lookup reads must write the lookup's durable fallback first, in the same locked section.

Checklist

  • At most two commits (one is the norm), with a Conventional Commits title (feat|fix|docs|style|refactor|perf|test|chore|ci|build|revert: ...)
  • Existing tests pass and new tests added for new functionality
  • Self-review completed; code follows project style guidelines
  • Documentation updated (if applicable)
  • No secrets, credentials, or internal references in the diff

Contribution License Agreement

@bolichen97
bolichen97 requested a review from a team as a code owner October 2, 2026 06:00
@github-actions github-actions Bot added the readiness: checking Automated validation is still running label Oct 2, 2026
@github-actions

github-actions Bot commented Oct 2, 2026 •

Copy link
Copy Markdown
Contributor

Design Review (Opus 5.5) — ✅ PASS

Design-level review of 9816ff65e2bc242a1d2c999f4116592c712f9d86 — updated in place on each push. A BLOCK verdict blocks PR readiness; PASS/CONCERNS are advisory.

Design-Verdict: PASS

Check that the impact comment's "no shipped path stored a view name" still holds. If it does, this is about 200 lines of batching code guarding a case no user has hit.

Suggestions

  • A simpler shape to weigh: before the drain walks anything, a single locked pass could copy every surviving sidecar's alias → agent pair into the ledger. That would make the per-candidate look_ahead/retain window state in _ViewLedgerWrites unnecessary. Only a backlog larger than _VIEW_SOURCES_MAX would still need the per-deletion path.

[DESIGN-REVIEWED] 9816ff6

Description read

[DESCRIPTION-READ] 80be777169a50dc8303dbbcc363d0bc01d4517c36d156f01ebfa4aa84bd2100d

That sha256 names everything this verdict read: the PR description, plus the 1 evidence file(s) the workflow collected from it and handed this review. It covers that evidence because the media strip replaces every attachment URL with the same placeholder, so an edit swapping one attachment for another would leave the description's captured text identical while what this review judged changed. Recompute it with .github/scripts/pr-description-capture.sh over the same inputs; if it differs, the description or that evidence changed after this verdict was formed and any finding drawn from either is unproven.

@github-actions github-actions Bot added readiness: action required A blocking check or review needs attention and removed readiness: checking Automated validation is still running labels Oct 2, 2026
@github-actions

github-actions Bot commented Oct 2, 2026 •

Copy link
Copy Markdown
Contributor

First Principles Review (Opus 5.5) — 🟡 CONCERNS

Premise-level review of 9816ff65e2bc242a1d2c999f4116592c712f9d86 — why this exists and whether the shipped surface is the smallest honest version. Updated in place on each push. A BLOCK verdict blocks PR readiness; PASS/CONCERNS are advisory.

First-Principles-Verdict: CONCERNS

The prune's 64-candidate look-ahead is justified by "thousands of pairs" per drain, but the prune already stops at 64 reclaims per run.

Not justified as shipped

  • Item 3 — oversized: the description says "A drain over thousands of pairs therefore costs one write per window instead of one per pair". But _prune_stale_managed_aliases stops at cap = _PRUNE_MAX_RECLAIMS_PER_RUN + len(keep), and _PRUNE_MAX_RECLAIMS_PER_RUN = 64 (skill_projection.py:99). So one prune makes at most 64 small ledger writes. The look-ahead saves at most 63 of them, and no cost was measured.
    Subtraction: delete _LEDGER_PREFETCH_WINDOW, look_ahead, _upcoming_views, _ahead/_ahead_from and the ledger.look_ahead(candidates, index) call. retain then records only its own pair.
    Clears when: the look-ahead is removed, or a measured per-run write cost shows it is needed.
  • Item 1 — inherited: "Why it matters" says "Every conversation recorded under a view name before the ledger existed stops resuming". The description's own Impact bullet says "no real path stored a view name" in the builds that shipped before the ledger, and calls the change "defensive". The defect is shown only by a constructed tree.
    Clears when: someone names a shipped path that stored a view name before the ledger existed (the ledger landed in e3309cd on 2026-09-30).

What this change ships

Inventory (5 items) — 3 justified

Intent: keep chats stored under a skill-view name resumable after the boot drain deletes that view's sidecar. This is a FIX.

  1. Pre-ledger views keep resolving after the sweep and prune delete their sidecars — inherited: the description's own impact note says shipped builds never stored view names
  2. When the ledger can't be written, the alias goes and the sidecar stays — justified
  3. The prune records up to 64 upcoming sidecars in the same ledger write — oversized
  4. A full ledger drops entries a sidecar still covers first, then the oldest retired names, with a warning — justified
  5. The refusal for an unrecoverable view says to pick the agent again or start a new chat — justified

[FIRST-PRINCIPLES-REVIEWED] 9816ff6

Description read

[DESCRIPTION-READ] 6af7dc69bd3b2ec70c2c9ad42683e12415b95eae804aae1fa5f4de82fb512381

That sha256 names the PR description this verdict read. Recompute it with .github/scripts/pr-description-capture.sh; if it differs, the description changed after this verdict was formed and any finding drawn from the description is unproven.

@github-actions

github-actions Bot commented Oct 2, 2026 •

Copy link
Copy Markdown
Contributor

GPT 6.1 Review — ✅ no blocking findings

GPT 6.1 completed its review of 9816ff65e2bc242a1d2c999f4116592c712f9d86 and found no blocking issues.

This comment is updated in place on each push.

Review details

No findings.
[GPT-REVIEWED] 9816ff6

False positive or not applicable? A repository writer can comment:
/ai-review override gpt 9816ff65e2bc242a1d2c999f4116592c712f9d86: <one-sentence reason>

@bolichen97
bolichen97 force-pushed the fix/skill-view-sidecar-ledger branch from 646f49d to 385c942 Compare October 2, 2026 06:15
@github-actions github-actions Bot added readiness: checking Automated validation is still running and removed readiness: action required A blocking check or review needs attention labels Oct 2, 2026
@bolichen97

Copy link
Copy Markdown
Contributor Author

Impact, traced against the core the internal 0.8.0.1/0.8.0.2 builds shipped (0.8.0-rc.1, which predates #15202 and 74cefff): this fix is defensive.

At that core, no real code path persists a kirocrew-skill-view-* name as any of the following: a session's agent, slot.agent, an execution record's template_id/selection_name, agent_override, or a crew-log/cron/crewmate record.

  • An untranslated alias can reach the client. The shared runtime rebuilds its projection before set_mode, while kiro-cli keeps its spawn-time alias, and frame translation only knows the current projection's aliases.
  • Every recorder refuses it first. chat_runner calls record_provider_agent_switch before it sets slot.agent. That call raises UnknownMemoryStore for an unresolvable name, because alias files never resolve (iter_agent_spec_files drops them). The handler then restores the prior selection.
  • Member slots veto the switch outright.
  • /agent is refused while the projection is on.
  • set_mode records the authored name.

So users of that build saw failed session starts or failed switches, not stored view names. The pod repro in the description wrote its session record by hand.

This PR still closes a real hole. Any stored view name, whether from a hand edit, an older record, or a future path, stays resolvable after the boot drain retires its sidecar. The refusal for a name nothing records now gives the remedy that works. It is not a P0, so please merge it on the normal schedule.

@github-actions

github-actions Bot commented Oct 2, 2026 •

Copy link
Copy Markdown
Contributor

Opus 5.5 Review — ✅ no blocking findings

Reviewed 9816ff65e2bc242a1d2c999f4116592c712f9d86 — this comment is updated in place on each push.

Review details

Advisory only: one misleading error message, nothing blocks the merge.

FINDING — src/kiro_crew/dashboard/chat_runner.py:360 — In some resumed chats the error message is wrong. The chat's stored view name maps back to its source agent through the sidecar or ledger, but that agent was later deleted. Here _source_of_view does find the agent, it just doesn't resolve, so requested_resolved is False. slot.agent still starts with NATIVE_SKILL_ALIAS_PREFIX, so the user is told "the agent it was built from is not recorded", which is false, and the message never names the agent they could restore. → Fix: in unavailable_agent_message, look up skill_view_source_agent(agent_name) first. Use the "not recorded" wording only when that returns None; otherwise name the source agent with the restore-or-choose wording.

[OPUS-REVIEWED] 9816ff6

Verdict parsed from the review's SHA-scoped output markers for commit 9816ff65e2bc242a1d2c999f4116592c712f9d86.

False positive or not applicable? A repository writer can comment:
/ai-review override fable 9816ff65e2bc242a1d2c999f4116592c712f9d86: <one-sentence reason>

@github-actions github-actions Bot added readiness: action required A blocking check or review needs attention and removed readiness: checking Automated validation is still running labels Oct 2, 2026
@bolichen97
bolichen97 force-pushed the fix/skill-view-sidecar-ledger branch from 385c942 to 12fc439 Compare October 2, 2026 06:41
@github-actions github-actions Bot added readiness: checking Automated validation is still running readiness: action required A blocking check or review needs attention and removed readiness: action required A blocking check or review needs attention readiness: checking Automated validation is still running labels Oct 2, 2026
@bolichen97
bolichen97 force-pushed the fix/skill-view-sidecar-ledger branch from 12fc439 to bb5a2a7 Compare October 2, 2026 07:12
@github-actions github-actions Bot added readiness: checking Automated validation is still running and removed readiness: action required A blocking check or review needs attention labels Oct 2, 2026
@bolichen97
bolichen97 force-pushed the fix/skill-view-sidecar-ledger branch from bb5a2a7 to 2319a1f Compare October 2, 2026 07:34
@bolichen97

Copy link
Copy Markdown
Contributor Author

Review findings on bb5a2a75ca are addressed in 2319a1feb2:

  • GPT 5.6 (blocking): retirement writes could evict newer ledger-only mappings. _record_view_ledger_entries no longer evicts an entry whose sidecar is gone. Over the bound, it drops entries a sidecar still answers for first, oldest first. Then it refuses the pairs being added, and retain reports them as not held, so their sidecar is kept. Covered by test_the_bound_never_evicts_a_view_whose_sidecar_is_gone; reverting to FIFO eviction fails it.
  • Opus 5: the sweep's unlinks ran past the deadline. The deletion loop now checks the deadline, and the recorded remainder goes on a later run. Covered by test_the_orphan_sweep_unlinks_nothing_past_its_deadline; removing the check fails it.
  • Opus 5: an unwritable ledger stopped alias reclamation. If retain fails, the alias still goes and only the sidecar is kept, on both prune pair paths. The refused-write tests cover both paths.
  • Opus 5: the owning spec was stale. docs/system-specs/modules/acp-client.md now states the ledger precondition, what the budget covers, and the eviction rule.
  • First Principles: the ledger=None default. ledger is now a required argument of _reclaim_prune_candidate, the fallback branch is gone, and the four test call sites pass a ledger.

#16074 carries the same two commits (head bfeced8061).

@github-actions github-actions Bot added readiness: action required A blocking check or review needs attention merge conflict Branch has merge conflicts with its base — author must resolve before merge and removed readiness: checking Automated validation is still running labels Oct 2, 2026
@bolichen97
bolichen97 force-pushed the fix/skill-view-sidecar-ledger branch from 2319a1f to e6590c0 Compare October 3, 2026 15:46
@github-actions github-actions Bot added readiness: checking Automated validation is still running and removed readiness: action required A blocking check or review needs attention labels Oct 3, 2026
@bolichen97

Copy link
Copy Markdown
Contributor Author

Review findings on 2319a1feb2 (#16073) and bfeced8061 (#16074) are addressed in e6590c01d4 (#16074: 6a94910747):

  • Opus 5 (blocking): the ledger latched once full. The bound now degrades instead of refusing. Past _VIEW_SOURCES_MAX, entries a sidecar still answers for go first. Then the oldest retired names go, counted in a warning (once, then debug). A full ledger never stops the sweep or the prune.
    • This also closes GPT 5.6's earlier finding on bb5a2a75: retiring a sidecar can no longer leave its mapping unwritten while the sidecar is deleted.
    • The remaining trade-off is that names older than the newest 2048 retired views stop resolving. This is the bounded loss the Not a goal section accepts by not changing the bound, and it is now logged.
  • GPT 5.6 (blocking, fix(skill-view): backport recording a view's source agent before its sidecar is deleted to release/0.8.0 #16074): partial admission. retain_many now writes and verifies the whole admissible batch, not only its missing pairs. A pair the ledger already held becomes newest in the same write, so that write cannot evict it while its sidecar is about to go. A batch larger than the bound is refused as a whole.
  • Opus advisory: a refused write was retried for every candidate. _ViewLedgerWrites latches the failure for the rest of the prune or sweep.
  • Opus advisory: docstrings and spec. The writer docstring, the _VIEW_SOURCES_MAX comment and acp-client.md now state the actual retention order.

Each new rule has a test, and reverting it fails that test. All added lines are covered.

@github-actions github-actions Bot added readiness: action required A blocking check or review needs attention and removed readiness: checking Automated validation is still running labels Oct 3, 2026
@github-actions github-actions Bot added readiness: checking Automated validation is still running and removed readiness: action required A blocking check or review needs attention labels Oct 3, 2026
…eleted

A conversation stored under a kirocrew-skill-view-<digest> name maps back to
its agent through the view's ownership sidecar, then the view ledger. The
ledger is written only at publication, for the aliases that run publishes, so
a view a pre-ledger build published is resolvable through its
sidecar alone. The boot drain deletes exactly that record: the orphan-sidecar
sweep retires a sidecar whose alias an outside cleanup or an operator already
removed, and the prune retires the alias and sidecar together. The stored
chat is then refused as "unavailable" although its agent is installed.

Every sidecar deletion now records the view's alias -> agent pair in the view
ledger first, under the publication lock the deletion already holds, through
the one bounded, atomic ledger writer. The sweep records its whole batch in
one write; the prune records a window of upcoming candidates the first time a
pair needs it, so a drain of thousands of pairs costs one write per window.
A sidecar the ledger cannot take is kept; the prune still removes its alias,
since the sidecar then answers for the view on its own. Both sweep halves stay
inside the time budget. Each write makes the whole batch the newest entries;
past the ledger's bound, entries a sidecar still answers for go first, then
the oldest retired names (counted in a warning), so a full ledger never stops
the sweep. A write the filesystem refuses is not retried per candidate.

The tests run the real drain over a real published view with no ledger, in
each of the three deletion paths, and resume the stored name through
resolve_session_agent_bindings.

The RetiredSkillView text the ACP spawn path raises for a view nothing
records also names "or start a new chat" as a remedy.
… view

A resumed chat whose recorded skill-view name nothing maps back was refused
as "Crew Member 'kirocrew-skill-view-...' is unavailable; restore it or choose
a member". A generated view is not a member anyone can restore, and the view
name is a one-way digest, so the agent cannot be recovered. Say what works
instead: pick the agent for this chat again, or start a new chat.
@bolichen97
bolichen97 force-pushed the fix/skill-view-sidecar-ledger branch from e6590c0 to 9816ff6 Compare October 3, 2026 16:09
@bolichen97

Copy link
Copy Markdown
Contributor Author

The GPT 5.6 finding on 6a94910747 ("Unreadable sidecars can evict the only valid mapping") is fixed in #16073 at 9816ff65e2 and in #16074 at 16f184a037.

Before this fix, a ledger entry counted as redundant whenever a file existed at its sidecar path. It now counts only when _sidecar_answers_for holds: the sidecar is a regular file with the managed marker, and it names the same agent the ledger entry names. This is the same reading _recorded_view_source uses. A sidecar that is unreadable, foreign, or names a different agent no longer makes its entry evictable.

test_the_bound_drops_redundant_entries_then_the_oldest_retired_ones now places an unreadable sidecar beside the oldest entry. If the check goes back to _path_exists, the test fails.

@github-actions github-actions Bot added readiness: action required A blocking check or review needs attention and removed merge conflict Branch has merge conflicts with its base — author must resolve before merge readiness: checking Automated validation is still running labels Oct 3, 2026
@bolichen97
bolichen97 merged commit cc57eeb into main Oct 3, 2026
97 of 99 checks passed
@bolichen97
bolichen97 deleted the fix/skill-view-sidecar-ledger branch October 3, 2026 16:40
@github-actions github-actions Bot removed the readiness: action required A blocking check or review needs attention label Oct 3, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Boot drain deletes skill-view ownership sidecars without recording the view's source agent

1 participant