Skip to content

feat(apps): pin issue-radar and auto-improvement for adoption - #36446

Merged
bolichen97 merged 1 commit into
mainfrom
feat/w4-pins
Nov 15, 2026
Merged

bolichen97 merged 1 commit into
mainfrom
feat/w4-pins

Conversation

@bolichen97

@bolichen97 bolichen97 commented Nov 13, 2026 •

Copy link
Copy Markdown
Contributor

Problem / Motivation

Goal: A host that has Issue Radar or Auto-Improvement as a built-in moves onto the app's own repository at its next restart, keeping everything it had.

Both apps now live in their own repositories (KiroCrewCaptain/kirocrew-app-issue-radar and KiroCrewCaptain/kirocrew-app-auto-improvement), ported up to the current wheel copy, with green CI on ubuntu, macOS and Windows. The wheel's adoption pin table does not name them yet, so no host adopts them and every fix keeps having to land twice.

Why it matters

Until a pin row exists, these two apps cannot leave core: every host keeps running the wheel copy, and the removal of the built-ins in #26967 cannot start for them.

Not a goal

  • Pinning auto-research, aws-control or project-scaffolder in this batch (see What changed).
  • Changing the adoption machinery, the D12 equality rule or either app's declared permissions.
  • Deleting the wheel copies (src/kiro_crew/apps/builtins/<app>/, website/src/apps/<app>/); only their app.json version moves.

What changed (motivation → approach → change)

Each row is the output of scripts/adoption_pin.py compute, copied into adoption-pins.json and the _SHIPPED_PINS table:

App Version Pinned commit minAppSdkLevel
issue-radar 0.1.0 to 0.1.2 8e57db85e15e 2 (ctx.auto_approve, agentTools, workerAutoApprove)
auto-improvement 1.0.0 to 1.0.3 0e1a22d2e10b 2 (ctx.lifecycle)

Each wheel built-in app.json version moves to the pinned version: a first-adoption pin must equal it (D12), and compute refuses the row with version_mismatch until it does. Each repository's app.json declares the same permissions as the wheel copy (the same three agentTools for issue-radar; the same agents, skills and MCP server name and autoApprove list for auto-improvement), so E9 holds nothing back. The two module specs record the adoption.

Each pinned tree carries every runtime change the wheel copy has on main b81cf5a3acc0:

Held back from the batch that reported ready:

App repo: KiroCrewCaptain/kirocrew-app-issue-radar@8e57db8
App repo: KiroCrewCaptain/kirocrew-app-auto-improvement@0e1a22d

Backwards compatibility

Compatible: two rows are added and two versions move up (issue-radar 0.1.0 to 0.1.2, auto-improvement 1.0.0 to 1.0.3). A host whose record is builtin-owned adopts at the next restart and keeps data/, .app_secret, the grants and enabled; a host that cannot adopt keeps the wheel copy unchanged. No other row changes.

Removes nothing: the wheel copies, their routes and every existing pin row stay.

Tests

test/test_builtin_adoption_pins.py::test_the_shipped_pin_file_validates_and_pins_exactly_the_shipped_table takes the two new rows; test_every_shipped_pin_matches_its_wheel_built_in_version holds the version bumps.

Proof: PROVEN test/test_builtin_adoption_pins.py::test_the_shipped_pin_file_validates_and_pins_exactly_the_shipped_table (head 8e5f2a9)

Determinism: no test logic changes, only the pinned data table. Every test/test_builtin_adoption*.py and test/test_core_auto_improvement_decoupling.py on origin/main b81cf5a plus this commit: 361 passed, 1 skipped. Black (at the pinned 26.10.1), flake8, isort, the comment-history, brand-name and line-cap gates pass; the diff has no frontend change.

Manual verification

scripts/adoption_pin.py verify over the network on origin/main b81cf5a plus this commit, with a throwaway HOME and KIROCREW_HOME: all seven rows ok under main's current tree and seam-level checks. Each pinned commit is the head of its repository's main, and its pull request and main check runs are all green (Tests on ubuntu, macOS and Windows, the reproducible UI bundle, README, internal-content-scan with credentials present and every added line checked). Each repository's port was a three-way merge of the wheel copy's changes since its last sync, with every catalog value checked against the base wording first.

Related Issues

Part of #26967

Catalog rows: the kirodotdev/KiroCrewApps PR linked in a comment below switches both source rows to the same commits. It is not auto-merged: the driver merges it right after this PR lands.

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

@bolichen97

Copy link
Copy Markdown
Contributor Author

Catalog rows: kirodotdev/KiroCrewApps#77 switches the issue-radar and auto-improvement rows to git sources at the same two commits. It is not auto-merged; the driver merges it right after this PR lands.

@bolichen97

Copy link
Copy Markdown
Contributor Author

Rebased: main moved in docs/system-specs/modules/history.md since this head went green (6149be8 -> d4b588b); CI re-running. The previous head 7283a32 had its review lanes, Dependency License Gate and readiness red on the repo-wide installation-token rate limit (API rate limit exceeded for installation), not on this diff; the new head re-runs all of them.

@github-actions github-actions Bot added the readiness: checking Automated validation is still running label Nov 13, 2026
@github-actions

github-actions Bot commented Nov 13, 2026 •

Copy link
Copy Markdown
Contributor

UX Review (Opus 5.5) — ⏭️ skipped

Revision 8e5f2a969f831374c64cf4a61e2475a7d20e8787 touches no user-facing surface (no changes under website/ or committed screenshots), so the UX review was skipped. Does not block merge.

@github-actions

github-actions Bot commented Nov 13, 2026 •

Copy link
Copy Markdown
Contributor

Design Review (Opus 5.5) — ✅ PASS

Design-level review of 8e5f2a969f831374c64cf4a61e2475a7d20e8787 — updated in place on each push. A BLOCK verdict blocks PR readiness; PASS does not.

Design-Verdict: PASS

Nothing blocks: this adds two pin rows through the existing adoption machinery, and the wheel copies remain as the fallback.

Notes

  • After adoption, auto-improvement looks up private core names (llm_helpers._steer_host_deny, config.loader._session_work_dir and others) by name from the running gateway, and fails closed if one is missing. A later core rename would therefore switch the adopted app off on hosts without warning. Each of those names should get a public surface, or a core-side test that pins it, before the wheel copy is deleted.

[DESIGN-REVIEWED] 8e5f2a9

Description read

[DESCRIPTION-READ] dbc2f71b22a7863c7ef2e7ca7fd475cd24a50fdccb45fe9bb2a0e3507f030512

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 commented Nov 13, 2026 •

Copy link
Copy Markdown
Contributor

First Principles Review (Opus 5.5) — ✅ PASS

Premise-level review of 8e5f2a969f831374c64cf4a61e2475a7d20e8787 — 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 does not.

First-Principles-Verdict: PASS

Nothing blocks. Both rows reuse the existing adoption-pin mechanism to carry out the AGENTS.md "No built-in apps" move-out under #26967.

What this change ships

Inventory (5 items) — 5 justified

Intent: let hosts running Issue Radar or Auto-Improvement as built-ins move onto each app's own repository at the next restart, keeping their data. This is an ADDITION.

  1. Hosts with built-in Issue Radar adopt KiroCrewCaptain/kirocrew-app-issue-radar at restart, keeping /issue-radar and the Radar icon — justified
  2. Hosts with built-in Auto-Improvement adopt KiroCrewCaptain/kirocrew-app-auto-improvement at restart, keeping /auto-improvement and the Brain icon — justified
  3. Wheel Issue Radar version moves 0.1.0 → 0.1.2 (D12 equality) — justified
  4. Wheel Auto-Improvement version moves 1.0.0 → 1.0.3 (D12 equality) — justified
  5. The two module specs record the adoption and the private-name shim status — justified

[FIRST-PRINCIPLES-REVIEWED] 8e5f2a9

Description read

[DESCRIPTION-READ] c939e6e9bac117ddacb0f267daa69de46ddb544b3d2190bcc4ca67b78ac8db08

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 Nov 13, 2026 •

Copy link
Copy Markdown
Contributor

Opus 5.5 Review — ✅ no blocking findings

Reviewed 8e5f2a969f831374c64cf4a61e2475a7d20e8787 — this comment is updated in place on each push.

Review details

No findings.

[OPUS-REVIEWED] 8e5f2a9

Verdict parsed from the review's SHA-scoped output markers for commit 8e5f2a969f831374c64cf4a61e2475a7d20e8787.

False positive or not applicable? A repository writer can comment:
/ai-review override fable 8e5f2a969f831374c64cf4a61e2475a7d20e8787 false-positive: <reason, 20 to 500 characters>

@github-actions

github-actions Bot commented Nov 13, 2026 •

Copy link
Copy Markdown
Contributor

GPT 6.1 Review — ✅ no blocking findings

GPT 6.1 completed its review of 8e5f2a969f831374c64cf4a61e2475a7d20e8787 and found no blocking issues.

This comment is updated in place on each push.

Review details

No findings.
[GPT-REVIEWED] 8e5f2a9

False positive or not applicable? A repository writer can comment:
/ai-review override gpt 8e5f2a969f831374c64cf4a61e2475a7d20e8787 false-positive: <reason, 20 to 500 characters>

@bolichen97

Copy link
Copy Markdown
Contributor Author

Backend Lint & Type Check (3.12) (and the Coverage Gate that waits on it) is red on main, not on this diff: src/kiro_crew/cli_commands_memory.py:335: error: Incompatible types in assignment after #36114 + #36212. Tracked in #36458, fixed by #36457. This PR waits for that fix and rebases onto it; every review lane on 28398aa is PASS with no findings.

@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 Nov 13, 2026
@KiroCrewCaptain

KiroCrewCaptain commented Nov 13, 2026 •

Copy link
Copy Markdown
Collaborator

Code change approver recommendation: Approve

Why: the decider estimates a 10% chance that this change introduces a defect, within the 12% limit for approving on its own, and every check passes.

This PR only changes data. It adds two rows to the adoption pin table, issue-radar 0.1.1 and auto-improvement 1.0.2, in the same shape as the five apps already pinned. It moves each wheel app.json version up to match its pin, which the version-equality rule (D12) requires and test_every_shipped_pin_matches_its_wheel_built_in_version enforces. It also updates the shipped-table test (_SHIPPED_PINS) and the two module specs.

The table now has 7 rows, well under the 64-row cap (MAX_PINS). Core code has no imports of either app's built-in module and no app-name string literals outside the wheel copies, so adoption can't leave core seams calling unloaded modules. That problem is why aws-control was held back.

On a host, every adoption check runs again at restart and fails closed when it doesn't hold: the tree hash, identity and version, the MCP server shape, permission parity and the SDK level. If a check refuses, the host keeps the wheel copy. That limits the risk to mistakes in the pin values themselves, which can't be checked offline. The PR reports a network verify run that came back clean. Undoing the change means removing the two rows.

Several CI checks hadn't finished at deci

An automated recommendation, not a review: a maintainer still decides. It approves on its own only when the estimated chance of a defect is at most 12% and the change has at most 400 changed lines. Decider v3c (217fe607) · commit c9933672c9 · 79 changed lines. If this recommendation is wrong, reply here: replies are how the approver is evaluated.

@bolichen97

Copy link
Copy Markdown
Contributor Author

Holding the rebase push: the auto-improvement pin is missing a security fix that landed on main today.

Rebasing onto origin/main (which carries #36457, the mypy fix) is clean, and the gates pass on the rebased tree: mypy is clean, the related adoption and decoupling tests pass (362), and flake8, isort, black, comment-history, brand, docs-lint and the flake ratchet are all clean. I am not pushing it, though. Between this head's base (d4b588bf) and today's main, #30602 (6b23c7d935d, merged 2026-11-13T10:49Z) changed the wheel copy's spine/agent_runner_gate.py. It re-checks eval and quoted separators in the runner gate.

The pinned tree KiroCrewCaptain/kirocrew-app-auto-improvement@c11e47889833 was cut at 03:07Z, before that fix. Its agent_runner_gate.py still has the old for words in _segments(text): loop, and the repository has no later port PR. A host that adopts at restart would therefore swap a wheel copy that has the fix for an adopted tree that does not. That is a security regression, so it cannot be overridden. It also makes the body's line "No wheel-copy change since each repository's port base is missing from it" untrue on today's base. The issue-radar row is not affected: main has not touched its wheel copy since the base.

Proposed fix, which keeps the frozen goal:

  1. Port fix(auto-improvement): re-check eval and quoted separators in the runner gate #30602 into kirocrew-app-auto-improvement and release 1.0.2.
  2. Re-run scripts/adoption_pin.py compute for that commit and bump the wheel's auto_improvement/app.json to 1.0.2 (D12).
  3. Rebase this PR and push.

The other way out is to hold auto-improvement back from this PR. That changes the frozen Goal, so only a maintainer can choose it.

The current head 28398aa5381c stays red on mypy, so the armed auto-merge cannot land it in the meantime.

@bolichen97

Copy link
Copy Markdown
Contributor Author

Hold resolved: the auto-improvement pin now carries #30602.

Auto-merge stays armed. The KiroCrewApps catalog row moves to the same commit in kirodotdev/KiroCrewApps#77.

bolichen97 added a commit to kirodotdev/KiroCrewApps that referenced this pull request Nov 13, 2026
Flips both first-party apps from a builtin source to a git source in
KiroCrewCaptain, each pinned at the commit the Kiro Crew adoption pin
table names for it (kirodotdev/KiroCrew#36446). The Kiro Crew org row
(issue-radar) gains the KiroCrewCaptain author URL; auto-improvement
keeps its person attribution.
@bolichen97

Copy link
Copy Markdown
Contributor Author

Rebased: main moved in test/test_builtin_adoption_pins.py (#36344, #36356) and the adoption checks (#36325) since this head went green (6d61070 -> 02bad16); CI re-running.

The old head c993367 had no review finding; its only reds (Analyze (actions), Dependency License Gate, GPT 6.1 Review, Publish readiness signal) were the installation-token and Bedrock rate limits. On the rebased tree scripts/adoption_pin.py verify reports all seven rows ok and the adoption tests pass (354 passed, 1 skipped).

@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 Nov 14, 2026
@bolichen97

Copy link
Copy Markdown
Contributor Author

Rebased onto origin/main 205d08d to pick up #37063, which fixes the test_search_docs red that failed shard 6 on every OS for the previous head f57cab5 (main's red, #37060). The diff is unchanged: a3e63c6.

Analyze (python) on the previous head was an installation API rate-limit error during the SARIF upload, not a finding.

Re-verified on the new base:

  • scripts/adoption_pin.py verify (network, throwaway HOME/KIROCREW_HOME): all seven rows ok.
  • Both pinned commits are still the head of main in KiroCrewCaptain/kirocrew-app-issue-radar (8bc24aa29e71) and KiroCrewCaptain/kirocrew-app-auto-improvement (a20e767f7a06).
  • Since 02bad16, main changed only test fixtures in the wheel copies (test: use synthetic credentials in redaction test fixtures #31863), with no runtime change to either app.
  • test/test_builtin_adoption*.py and test/test_core_auto_improvement_decoupling.py: 354 passed, 1 skipped. Guide tests: 310 passed. prove.py: PROVEN at a3e63c6.

@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 Nov 14, 2026
@bolichen97

Copy link
Copy Markdown
Contributor Author

Head a3e63c6 has one remaining red, and it comes from main, not this diff: Backend Tests (3.12, 2) and Backend Tests (Windows) (2) fail the same two tests, and Coverage Gate folds that red in:

  • test/tracing/test_tracing_otlp.py::test_a_traced_turn_reaches_a_loopback_receiver_with_its_vault_header (extra kirocrew.step span)
  • test/tracing/test_tracing_otlp.py::test_the_exit_flush_sends_spans_still_queued (assert 5 == 4)

#37005 added SPAN_STEP = "kirocrew.step" (src/kiro_crew/tracing/turns.py), but the wire tests on main do not expect it yet. This PR touches no tracing code. Open fixes: #37171 and #37188. Every other check passes, including all AI review lanes (Design, First Principles, UX, GPT, Opus, Security Scope). Next step: rebase onto the fix once it merges. No rerun and no override for this red.

@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 Nov 14, 2026
@bolichen97

Copy link
Copy Markdown
Contributor Author

Hold: do not rebase-and-push this PR until the issue-radar pin is recomputed.

The shard 2 red on a3e63c6 is main's OTLP tracing red (test/tracing/test_tracing_otlp.py::test_a_traced_turn_reaches_a_loopback_receiver_with_its_vault_header, ::test_the_exit_flush_sends_spans_still_queued), fixed by #37171. A rebase onto origin/main (66dc266d) is clean and scripts/adoption_pin.py verify passes for every row, so CI would go green on it. It was not pushed, because the rebase showed a problem that verify does not check:

Pin Pinned tree Wheel fixes on main the tree is missing
issue-radar 0.1.1 @ 8bc24aa ported up to main 4e4bba39 #31713 (fix(issue-radar): a crew never merges or arms auto-merge on gitlab) and #32503 (bad-body 400s in http_routes/*, routes.py)
auto-improvement 1.0.2 @ a20e767 ports #30602 only #31863, which changes test fixtures, not runtime code

If this lands as it is, every host adopts issue-radar at its next restart and runs the 8bc24aa tree. That tree's backend/crew_runtime_prompt.py has no may_arm_auto_merge, so a GitLab crew can arm merge_when_pipeline_succeeds again and merge an MR with no human review. That is the defect #31713 fixed. It breaks ruling 4 of #26967 (no user impact).

What has to happen first (outside this PR's branch):

  1. Port fix(issue-radar): a crew never merges or arms auto-merge on gitlab #31713 and fix(dashboard): give every bad-body 400 a code #32503 into KiroCrewCaptain/kirocrew-app-issue-radar and release 0.1.2.
  2. Run scripts/adoption_pin.py compute https://github.com/KiroCrewCaptain/kirocrew-app-issue-radar <commit> --min-sdk-level 2 and swap the row into adoption-pins.json and test_builtin_adoption_pins.py.
  3. Set the wheel's issue_radar/app.json to 0.1.2 (D12).

After that, the next round rebases onto main, re-runs verify, and pushes. The current head stays red on shard 2, so auto-merge cannot fire before then.

Adds both former built-ins to the wheel's adoption pin table, each at
the main head of its own KiroCrewCaptain repository (CI green there),
with the row scripts/adoption_pin.py compute printed and verify
re-checked. A host whose record is builtin-owned swaps it in place onto
that tree at the next restart, keeping data, secret, grants and enabled.

Each wheel built-in app.json version moves to the pinned version, since
a first-adoption pin must equal it (D12). Both pins need App Kit level
2: issue-radar for ctx.auto_approve and agentTools, auto-improvement
for ctx.lifecycle.

Part of #26967
@bolichen97

Copy link
Copy Markdown
Contributor Author

Hold resolved. The issue-radar pin is recomputed, and auto-improvement was re-checked the same way.

Pin Now What the new tree carries
issue-radar 0.1.2 KiroCrewCaptain/kirocrew-app-issue-radar@8e57db85e15e (KiroCrewCaptain/kirocrew-app-issue-radar#3) every wheel-copy change since the old port base 4e4bba39: #31713 (may_arm_auto_merge decides the crew's merge rule, never arming on GitLab; the editor locks the toggle there), #32503 (coded bad-body 400s), #37301 (native crew noun in the pipeline strings), and the test-only #37262, #36562, #31863, #36062
auto-improvement 1.0.3 KiroCrewCaptain/kirocrew-app-auto-improvement@0e1a22d2e10b (KiroCrewCaptain/kirocrew-app-auto-improvement#12) #36083, which landed on main after the hold: the tests' sandbox mask leaves the kiro-cli permission-rule leaves out instead of hiding all of ~/.kiro. #31863 and #35994 are test-only

Both repositories' PR and main runs are green (Tests on ubuntu, macOS and Windows, the reproducible UI bundle, README, internal-content-scan with every added line checked).

The branch is rebased onto main b81cf5a3acc0 as one commit, 8e5f2a969f83: both rows come from scripts/adoption_pin.py compute ... --min-sdk-level 2, both wheel app.json versions match them, and verify reports all seven rows ok. test/test_builtin_adoption*.py plus test/test_core_auto_improvement_decoupling.py: 361 passed, 1 skipped; the adopted-wheel-copy check passes with the two App repo: lines. Auto-merge stays armed.

@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 Nov 14, 2026
bolichen97 added a commit to kirodotdev/KiroCrewApps that referenced this pull request Nov 14, 2026
The Kiro Crew pin PR (kirodotdev/KiroCrew#36446) now pins issue-radar
0.1.2 at KiroCrewCaptain/kirocrew-app-issue-radar@8e57db85e15e and
auto-improvement 1.0.3 at
KiroCrewCaptain/kirocrew-app-auto-improvement@0e1a22d2e10b, each
carrying the wheel-copy fixes that landed after the earlier commits.
Each source ref moves to the commit its pin row names.
@github-actions github-actions Bot added readiness: passed Eligible automated validation passed for the current revision and removed readiness: checking Automated validation is still running labels Nov 14, 2026
@bolichen97

Copy link
Copy Markdown
Contributor Author

Green-age check on head 8e5f2a9 (no push): green_age.py reports main +20 commits with 10 same-dir overlaps, none of them a file this PR edits.

  • git diff b81cf5a3 origin/main over the six PR files and every builtin_adoption*.py / adoption-pins.json consumer: empty. The only main change under a touched directory is docs: tighten apps comments #37370, comment-only edits in auto_improvement/spine/{driver,driver_publish,gate}.py, which the pinned app-repo tree does not read.
  • Cherry-picked 8e5f2a9 onto fresh origin/main (8b73a99) in a throwaway worktree, clean apply:
    • test/test_builtin_adoption_*.py, test/test_adopted_wheel_copy_check.py, test/test_app_agent_tools_adopted.py, test/integration/test_builtin_adoption_boot.py: 396 passed, 3 skipped.
    • test/test_core_{auto_improvement,issue_radar}_decoupling.py + both apps' tests/: 4443 passed, 3 skipped.

The green on this head still describes today's base for this PR's closure, so it is left un-rebased (re-sync budget kept at 2/3).

@KiroCrewCaptain KiroCrewCaptain left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approved. On this head the review reproduced the archiveSha256 and treeSha256 of both pinned trees (issue-radar at 8e57db85, auto-improvement at 0e1a22d2). It confirmed that each pin version equals the pinned manifest and the bumped wheel app.json, which test_every_shipped_pin_matches_its_wheel_built_in_version pins. It also checked that permissions, agentTools, agents, skills and the MCP autoApprove list match the wheel copies, and that the runner gate, may_arm_auto_merge and the owner gates carry the wheel-copy safety fixes behind host shims that fail closed.
Done well: you held the push twice when a pinned tree was missing a wheel-copy safety fix (#30602, then #31713 and #32503), ported the fixes, and recomputed both pins.

Optional:

  • Before merge, run the drift check again (git diff b81cf5a origin/main over both wheel-copy trees), because open PRs such as #30251 still edit these wheel copies. A short PR comment could also tell those authors that an App repo: line will be required once this lands.
  • The "Held back" list in the body is stale. #36321 and #36322 are already in this PR's base, and #37411 now pins auto-research and project-scaffolder. A body edit is enough.
  • docs/system-specs/modules/issue-radar.md:103 says the rail keeps the "Radar" glyph, but "Radar" is not a registered nav glyph, so the rail shows the app's own icon. Users see no change. Only the wording is off.

@bolichen97
bolichen97 merged commit 99dc8da into main Nov 15, 2026
101 of 106 checks passed
@bolichen97
bolichen97 deleted the feat/w4-pins branch November 15, 2026 00:23
@github-actions github-actions Bot removed the readiness: passed Eligible automated validation passed for the current revision label Nov 15, 2026
bolichen97 added a commit to kirodotdev/KiroCrewApps that referenced this pull request Nov 15, 2026
…es (#77)

* feat: list issue-radar and auto-improvement from their own repositories

Flips both first-party apps from a builtin source to a git source in
KiroCrewCaptain, each pinned at the commit the Kiro Crew adoption pin
table names for it (kirodotdev/KiroCrew#36446). The Kiro Crew org row
(issue-radar) gains the KiroCrewCaptain author URL; auto-improvement
keeps its person attribution.

* chore: move issue-radar and auto-improvement to their new pinned commits

The Kiro Crew pin PR (kirodotdev/KiroCrew#36446) now pins issue-radar
0.1.2 at KiroCrewCaptain/kirocrew-app-issue-radar@8e57db85e15e and
auto-improvement 1.0.3 at
KiroCrewCaptain/kirocrew-app-auto-improvement@0e1a22d2e10b, each
carrying the wheel-copy fixes that landed after the earlier commits.
Each source ref moves to the commit its pin row names.
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.

2 participants