Skip to content

refactor(lambda): move term_kind.mbt to meta/ to align with json layout#695

Merged
dowdiness merged 1 commit into
mainfrom
feat/570-lambda-meta-layout
Jul 11, 2026
Merged

refactor(lambda): move term_kind.mbt to meta/ to align with json layout#695
dowdiness merged 1 commit into
mainfrom
feat/570-lambda-meta-layout

Conversation

@dowdiness

Copy link
Copy Markdown
Owner

Closes #570

Move examples/lambda/term_kind.mbt -> examples/lambda/meta/term_kind.mbt to match examples/json/meta/term_kind.mbt layout.

Updated all references (CI, regression tests, docs). File is not part of any package (no moon.pkg in meta/), consumed via loomgen --term at generation time.

moon test --target native: 3309/3309 pass

@coderabbitai

coderabbitai Bot commented Jul 11, 2026

Copy link
Copy Markdown

Warning

Review limit reached

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

Next review available in: 19 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: defaults

Review profile: CHILL

Plan: Pro

Run ID: d0322820-0ffb-4684-922c-790d6403c458

📥 Commits

Reviewing files that changed from the base of the PR and between 1af41fb and 8533c96.

📒 Files selected for processing (6)
  • .github/workflows/ci.yml
  • examples/lambda/meta/term_kind.mbt
  • examples/lambda/pkg.generated.mbti
  • loomgen/HANDOFF.md
  • loomgen/README.md
  • loomgen/regression_wbtest.mbt
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch feat/570-lambda-meta-layout

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.

…ut (#570)

examples/lambda/term_kind.mbt is the only remaining example with term_kind
at the package root. Move it to examples/lambda/meta/term_kind.mbt to match
the json layout (examples/json/meta/term_kind.mbt).

File is not part of any package (no moon.pkg in meta/), consumed via
loomgen --term at generation time.

Updated all references:
- .github/workflows/ci.yml (3 occurrences)
- loomgen/regression_wbtest.mbt
- loomgen/README.md
- loomgen/HANDOFF.md

Closes #570
@dowdiness dowdiness force-pushed the feat/570-lambda-meta-layout branch from 7181c1e to 8533c96 Compare July 11, 2026 05:11
@dowdiness dowdiness merged commit b256ad8 into main Jul 11, 2026
38 checks passed
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.

loomgen: examples/lambda/term_kind.mbt is compiled into the lambda package; align to json's non-package meta/ layout

1 participant