Document organization and project spending caps - #520
Conversation
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
There was a problem hiding this comment.
Stale comment
Risk assessment: Very Low (re-evaluated after push)
Previous approval remains in effect. This run does not re-approve.
Verified from the current diff only (4 files, +151 / −0 vs
main; 1-line change since the prior approval onab83382).What changed (full PR)
- New Mintlify page
info/spending-caps.mdx(product docs for organization vs project spending caps)- One nav entry in
docs.json(info/spending-caps)- Two cross-links from existing docs (
info/pricing.mdx,info/projects.mdx)What changed since last approval
- In
info/spending-caps.mdx, the limited-preview note now uses amailto:support@kernel.shlink instead of/info/support. Still documentation-only.Why this remains Very Low
- Documentation-only on a docs site; no application logic, APIs, auth, billing enforcement, CI, or infrastructure
docs.jsonchange is a sidebar path addition, not runtime/infra config- No CODEOWNERS file and branch ruleset has
require_code_owner_review: false- Risk did not increase, so the existing approval is not dismissed
No production codepaths or shared systems are modified.
Sent by Cursor Automation: Assign PR reviewers
There was a problem hiding this comment.
Stale comment
Risk assessment: Very Low (re-evaluated after push)
Previous approval remains in effect. This run does not re-approve.
Verified from the current diff only (4 files, +156 / −0 vs
main).What changed (full PR)
- New Mintlify page
info/spending-caps.mdx(product docs for organization vs project spending caps)- One nav entry in
docs.json(info/spending-caps)- Two cross-links from existing docs (
info/pricing.mdx,info/projects.mdx)What changed since last approval (
ab83382→eb4fc50)
- Availability note in
info/spending-caps.mdxnow splits organization vs project preview access and uses amailto:support@kernel.shrequest link. Still documentation-only.Why this remains Very Low
- Documentation-only on a docs site; no application logic, APIs, auth, billing enforcement, CI, or infrastructure
docs.jsonchange is a sidebar path addition, not runtime/infra config- No CODEOWNERS file in the repo
- Risk did not increase, so the existing approval is not dismissed
No production codepaths or shared systems are modified.
Sent by Cursor Automation: Assign PR reviewers
There was a problem hiding this comment.
Risk assessment: Very Low (re-evaluated after push)
Previous approval remains in effect. This run does not re-approve.
Verified from the current diff only (4 files, +177 / −0 vs main).
What changed (full PR)
- New Mintlify page
info/spending-caps.mdx(product docs for organization vs project spending caps) - One nav entry in
docs.json(info/spending-caps) - Two cross-links from existing docs (
info/pricing.mdx,info/projects.mdx)
What changed since last assessment (eb4fc50 → b639f53)
- Organization and project cards in
info/spending-caps.mdxnow use inline SVGs instead of named icon strings. Cosmetic docs markup only.
Why this remains Very Low
- Documentation-only on a docs site; no application logic, APIs, auth, billing enforcement, CI, or infrastructure
docs.jsonchange is a sidebar path addition, not runtime/infra config- No CODEOWNERS file in the repo
- Risk did not increase, so the existing approval is not dismissed
No production codepaths or shared systems are modified.
Sent by Cursor Automation: Assign PR reviewers


summary
testing
mint validatemint broken-links/info/spending-capslocally in chromiumgit diff --check main...HEAD