Skip to content

(MOT-4187) fix(iii-directory): make explicit repo downloads visible - #588

Open
rohitg00 wants to merge 1 commit into
mainfrom
feat/repo-download-visibility
Open

(MOT-4187) fix(iii-directory): make explicit repo downloads visible#588
rohitg00 wants to merge 1 commit into
mainfrom
feat/repo-download-visibility

Conversation

@rohitg00

Copy link
Copy Markdown
Contributor

Problem

directory::skills::download with a repo source, the exact call this worker's README quickstart demonstrates, produces invisible knowledge under default config: the downloaded namespace matches no installed worker, so filter_unregistered: true hides it from list/get/index. The repo path also wrote no completion marker, so nothing on disk distinguished an intentional pull from an uninstalled worker's leftovers, and the reconcile had no provenance for it either. Reproduced live: a repo download returned skills_written and then get on the namespace failed and list omitted it.

Change

Two mechanisms, both marker-based:

  • Function-path downloads write the completion marker for both sources. Repo markers record source: "repo" and the branch; registry markers keep their existing shape. Registry function-path downloads previously wrote no marker at all (only auto-download did), so they gain provenance too.
  • The visibility filter keeps namespaces whose marker records an explicit repo download (repo_pinned_namespaces, read from disk per resolve). Leftover namespaces from removed workers keep their current hidden behavior: their markers say registry, and worker presence still governs those.

Tests

New unit tests: pinned namespace survives the filter while an unmarked orphan stays hidden; marker roundtrip unchanged for registry shape. cargo fmt --check, clippy --all-targets --all-features -- -D warnings, cargo test --lib (262) pass.

Overlaps download.rs with #573; whichever lands second rebases trivially (adjacent marker-code hunks).

Refs MOT-4187

directory::skills::download with a repo source (the README quickstart's
own example) wrote files that filter_unregistered then hid: the
namespace matches no installed worker, and the repo path wrote no
completion marker, so nothing distinguished an intentional pull from an
uninstalled worker's leftovers.

Function-path downloads now write the completion marker for both
sources (repo markers record source "repo" and the branch; registry
markers keep their existing shape), and the visibility filter keeps
namespaces whose marker records an explicit repo download. Registry
function-path downloads gain provenance markers too, matching the
auto-download path.
@vercel

vercel Bot commented Jul 24, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
workers Ready Ready Preview, Comment Jul 24, 2026 10:20am
workers-tech-spec Ready Ready Preview, Comment Jul 24, 2026 10:20am

Request Review

@coderabbitai

coderabbitai Bot commented Jul 24, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@rohitg00, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 33 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 3ec3a4f2-588f-4687-96cd-ddb313bff2f5

📥 Commits

Reviewing files that changed from the base of the PR and between a87aa81 and 491ec02.

📒 Files selected for processing (3)
  • iii-directory/README.md
  • iii-directory/src/functions/download.rs
  • iii-directory/src/functions/skills.rs
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch feat/repo-download-visibility

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@github-actions

Copy link
Copy Markdown
Contributor

skill-check — worker

0 verified, 48 skipped (no docs/).

Layer Result
structure
vale
ai
render

Four for four. Nicely done.

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.

1 participant