Conversation
Mintlify root skill.md overrides the auto REST skill from Skill e780949; LICENSE is inlined. Co-authored-by: Cursor <cursoragent@cursor.com>
Rewrite the relative LICENSE link to the pinned raw GitHub URL instead of inlining MIT text. Keep static-key HTTP fallbacks, honest catalog 404s, and an offline export --check in CI. Co-authored-by: Cursor <cursoragent@cursor.com>
This was referenced Sep 14, 2026
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
1 participant
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.
Agents discovering AIsa through Mintlify previously received an automatically generated REST Skill that contradicted the canonical CLI/MCP Skill. A repo-root
skill.mdnow uses Mintlify's supported override and is exported from the immutable canonical Skill commit e780949. One documented transformation rewrites its relative LICENSE link to the same commit's public LICENSE URL.A focused offline export check runs in PR/main CI, including a mutated-export negative control. It verifies the pinned export; future canonical changes still require an intentional pin/export update. It does not silently track upstream main.
English/Chinese Quickstart and fallback guidance now match the existing CLI credential model. CLI-managed OAuth is not presented as a static key for raw HTTP; direct HTTP requires a separately configured static key/authorized secret. User-facing release chatter is removed, and the paid-approval XML remains unchanged.
Native discovery configuration
Both existing API Reference tabs now declare
openapi: "openapi.yaml", the documented Mintlify ingestion input. Removing only these two keys produces the previous navigation tree exactly. OfficialvalidateDocsConfigaccepts both configurations without warnings.This is a source configuration change, not a claim that the hosted api-catalog404 is already fixed. Local mint dev also404s known hosted AgentCard/OpenAPI resources, so it cannot certify the hosted metadata endpoint. No same-snapshot runtime sidebar comparison was performed; navigation evidence is structural. The discovery guide gives working OpenAPI/documentation index fallbacks until hosted verification passes.
Validation and release order
https://aisa.one/docs/.well-known/api-catalogandhttps://aisa.mintlify.dev/docs/.well-known/api-catalog. Generation may take up to24h. If the catalog remains404, retain the explicit fallback and investigate the hosted platform response.Companions: landing #108 and domain MCP #5.