fix(router): drop tooling reference from integrate intent#156
Open
sanchitmehtagit wants to merge 2 commits into
Open
fix(router): drop tooling reference from integrate intent#156sanchitmehtagit wants to merge 2 commits into
sanchitmehtagit wants to merge 2 commits into
Conversation
The `integrate` intent unconditionally co-loaded `tooling-{tooling}.md`
(tooling-cli by default) alongside the framework reference on every
quickstart-style integration — even tasks that only add login and never
touch tenant configuration.
Quickstart integrations don't need the CLI tooling reference: the framework
reference already carries the full integration workflow. Loading tooling-cli
anyway adds context noise that lower-capability models hallucinate from
(e.g. inventing Management API calls that no reference actually teaches).
Remove the unconditional tooling load from `integrate` so the intent reads
only the framework reference. tooling-{tooling}.md remains routable from the
feature/migrate intents that genuinely provision tenant config.
📝 WalkthroughWalkthroughThe Auth0 ChangesAuth0 integration guidance
Estimated code review effort: 1 (Trivial) | ~2 minutes Possibly related PRs
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
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. Comment |
…tooling-from-integrate
✅ skillsaw — All checks passedFull report
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The
integrateintent unconditionally co-loadedtooling-{tooling}.md(tooling-cli by default) alongside the framework reference on every quickstart-style integration —### integrate Read: references/framework-{framework}.md -Read: references/tooling-{tooling}.md Follow the integration workflow in framework-{framework}.md. -Use tooling-{tooling}.md for all Auth0 tenant configuration steps.Why
Quickstart integrations don't need the CLI tooling reference — the framework reference already carries the full integration workflow and cli config both. Loading
tooling-cli.mdanyway just adds context noise, and lower-capability models hallucinate from that extra surface (e.g. inventing Management API/api/v2/users/...calls ). This issue was observed with Haiku 4.5 and This change fixed that.tooling-{tooling}.mdstays routable from thefeature:*andmigrateintents that genuinely provision tenant config, so nothing that needs it loses access. Router reachability check passes (check_router_reachability.py: all references routable).This has following downsides:
Prior Skill consolidation this was not the case
Relationship to #152
#152 takes the conditional approach — gate the tooling load on a tenant-config need. This PR is the simpler cut for the
integratepath specifically: quickstart integrations don't provision tenant config as part of the task, so the reference is just dropped rather than gated. If #152 lands first, this becomes a no-op simplification of the same block; happy to reconcile.Validation
check_router_reachability.py— PASS (all references routable, no broken routes, no second-hop references)integrateblock only; no other intents touchedSummary by CodeRabbit