The GitLab Orbit docs have the following issues that need to be addressed before GA. ## Content issues - Style and language issues. - Information is sometimes vague or lacking necessary detail for how to use the feature. - Contradictory statements: "you never write JSON queries by hand" vs. "edit this JSON" - No documentation about the following: - The [Orbit dashboard](https://gitlab.com/dashboard/orbit) or how to use any of the components: - Query editor - Filter - Explore tab - Schema tab - Show labels toggle - Orbit toggles in Duo Chat window. - Orbit foundational agent. ## Documentation gaps Claude Code (with Orbit) checked for accuracy with the code base and found the following gaps. These could be simply due to drift, but highlights the importance of documentation being updated by engineering when code changes. [Docs automation](https://docs.gitlab.com/development/documentation/site_architecture/automation/) is a possible solution for reference information that can be discussed with the TW team. <details> <summary>Click for docs gaps report</summary> | \# | Doc location | Documented claim | Actual (code/config) | |----|--------------|------------------|----------------------| | 1 | `troubleshooting.md:75-86` | `orbit mcp serve` is "not yet implemented"; `mcp` subcommand errors with `unrecognized subcommand 'mcp'`. | Fully implemented: `crates/orbit-local/src/main.rs:216-223,261-265,310-324` + `mcp.rs`. Entry is entirely obsolete. | | 2 | `remote/indexing.md:63-81`, `local/indexing.md:52-73`, `local/how-it-works.md:70-74`, `local/access/mcp.md:122` | 11/13 supported languages; Swift and Terraform explicitly _not_ indexed. | 18 languages defined and registered: `crates/code-graph/src/v2/config/lang.rs:107-229`, `registry.rs:89-109`. Missing from docs: Elixir, Scala, Lua, Swift, HCL/Terraform. Swift and Terraform **are** indexed. | | 3 | `remote/schema.md:5,29` | "Full reference for all 27 node types across 6 domains." | 32 node types across 8 domains (`config/ontology/schema.yaml`). Undocumented: `packages` domain (`Package`, `PackageFile`, `Dependency`), `container_registry` domain (`ContainerRepository`), and `Commit`. | | 4 | `api.md:175-198` | `GET /api/v4/orbit/status` returns indexing coverage: `{status:"indexed", domains:{sdlc,code}, projects:{total,indexed}}`. | Path maps to `GetClusterHealth` returning component health `{status,timestamp,version,components[]}` (`crates/gkg-server/src/proto/gkg.v1.rs:1059`). Coverage shape belongs to a different RPC (`GetGraphStatus`), and even there fields differ (`projects.total_known`, `domains` is an array). Contradicted by `glab.md:71`. | | 5 | `remote/how-it-works.md:96-97` | Compiled SQL shown to "instance administrators and direct GitLab organization members with Reporter or higher." | SaaS requires `is_gitlab_team_member` (GitLab staff); self-managed/Dedicated requires admin (`crates/query-engine/shared/src/stages/output.rs:63-78`). No "Reporter+ org member" path. | | 6 | `remote/getting-started.md:122`, `remote/schema.md:29`, `remote/_index.md:44`, `local/schema.md:57`, `remote/indexing.md:39-45` | Node/domain counts stated as "28"/"27" node types and "6 domains" (pages disagree with each other). | 32 node types across 8 domains. Packages and Container-registry domains omitted from indexed-data list. | | 7 | `remote/access/mcp.md:5,29,43-49` | Two MCP tools: `query_graph`, `get_graph_schema`. | Registry serves four: also `list_commands`, `invoke_command` (`crates/gkg-server/src/tools/v2_registry.rs:11-18`; `grpc/service.rs:165`). Invokable `get_query_dsl`/`get_response_format` also exist. | | 8 | `api.md:5,48-55` | Reference for "all four endpoints." | At least six REST endpoints; also `GET /api/v4/orbit/dsl` (proto `:971`) and `GET /api/v4/orbit/templates` (proto `:1001`). | | 9 | `api.md:64-65,73,107` vs `glab.md:113` | `api.md` uses body field `"format"`; `glab.md` says `--format` maps to `response_format`. | Proto field is `format` (`ExecuteQueryRequest.format`, proto `:30`); no `response_format` exists. `glab.md` is wrong. | | 10 | `local/access/cli.md` | Documents `index`/`schema`/`sql`/`list`/`mcp serve` only. | Also has `version`, `skill [PATH]`, and `repo-map` (subcommands `overview`/`tree`/`api`/`class`/`extends`/`imports`) — `crates/orbit-local/src/main.rs:146-259`. | | 11 | `remote/schema.md:41-42` | Group/Project key property `visibility`. | Property is `visibility_level` (`config/ontology/nodes/core/{project,group}.yaml`); `visibility` would fail. | | 12 | `remote/queries/query-language.md:104` | `order_by` type is `object`. | Deserialized as a string `"[-]node.property"` (`crates/query-engine/compiler/src/input.rs:861-892`); the doc's own example at :401 uses the string form. | | 13 | `local/how-it-works.md:33` | Lists "rust-analyzer" as a parser. | No rust-analyzer dependency; Rust uses a custom tree-sitter pipeline, JS/TS use OXC. | | 14 | `local/indexing.md:34` | Local indexing has "no group, project, or branch concept." | Contradicts `local/how-it-works.md:66`; code writes `project_id`+`branch` to the manifest (`crates/orbit-local/src/main.rs:458-478`). | | 15 | `query-language.md:451-461`; various | Undocumented features/params. | Time-bucketing `transform`/`truncate` (`input.rs:634-691`); 6 predefined named queries (`config/named_queries/`); 5 MB per-file cap (`main.rs:27`); optional `db` param on local MCP tools; `format`/`expand_nodes` params on remote tools. | | 16 | `troubleshooting.md:35-36` | "no local graph found" error text. | Wording no longer matches `crates/orbit-local/src/sql.rs:16-20`. | </details> ## Information architecture issues - Organized around syntax, not setup. Users don't have a clear path to follow to use Orbit. The flow should be Get started → Use GitLab Orbit → Connect your tools, _before_ any querying. - No page that explains nodes, entities, edges, domains, and the relationship between prompts, queries, and the graph. Vocabulary is assumed throughout. Readers view feature pages without the concepts to understand them. - No in-product UI docs. - Getting started is not persona-based, readers don't know which applies to them. - Cookbook is one collapsible page. - Orphaned page: ai_coding_agents. ## IA Proposal GitLab Orbit's documentation is organized around query syntax instead of getting set up. Information about how to use Orbit is buried in reference documentation about the DSL (domain-specific language, JSON). This restructured IA: - Reorganizes the IA around giving users a more clear path to using Orbit. - Conceptual information to orient the user is in a level above the two products, Remote and Local. - Places the query DSL in a reference section for the audiences who might use it to build integrations. {width="212" height="600"} <details> <summary>Click to see folder structure</summary> ```text docs/source/ ├── _index.md # GitLab Orbit (overview + Remote-vs-Local comparison + brief security note) ├── concepts.md # Key concepts ├── indexed-data.md # Indexed data ├── remote/ # GitLab Orbit Remote [section] │ ├── _index.md │ ├── getting-started.md │ ├── use.md # Use in GitLab │ ├── access/ # Connect your tools [section] │ │ ├── _index.md │ │ ├── ai-coding-agents.md │ │ ├── mcp.md │ │ ├── duo.md │ │ ├── glab.md │ │ └── api.md │ ├── examples/ # [section] individual example pages │ │ └── _index.md │ ├── reference/ # [section] │ │ ├── _index.md │ │ ├── query-dsl.md # Query DSL (JSON) — demoted │ │ └── schema.md │ ├── permissions.md │ ├── data-and-compliance.md # Data and compliance │ ├── billing.md # Billing and credits │ └── troubleshooting.md └── local/ # GitLab Orbit Local [section] ├── _index.md ├── get-started.md ├── access/ # Connect your tools [section] │ ├── _index.md │ ├── cli.md # orbit CLI │ ├── mcp.md │ └── glab.md ├── queries.md # Query with SQL ├── examples/ # [section] individual example pages │ └── _index.md ├── reference/ # [section] │ ├── _index.md │ ├── schema.md │ └── cli.md # orbit CLI reference (generated) └── troubleshooting.md ``` </details> ### Page content | Content file | Title | Purpose | |--------------|-------|---------| | `_index.md` | GitLab Orbit | Overview landing: what it is, a Remote-vs-Local comparison table, content about Security before the tiles. | | `concepts.md` | Key concepts | Foundational grounding: nodes/entities/edges/domains + prompt→query relationship. Shared. | | `indexed-data.md` | Indexed data | What's indexed vs not; per-product indexing detail; language list generated. | | `remote/_index.md` | GitLab Orbit Remote | Remote product landing. | | `remote/get-started.md` | Get started | Persona-structured setup (AI tool / UI / API). | | `remote/use.md` | Use in GitLab | Single page, H2 sections: turn on GitLab Orbit Remote (old "Orbit \> Configuration" is wrong), dashboard, query editor & filters, explore the schema, Chat UI toggles, Orbit as a foundational agent. | | `remote/access/_index.md` | Connect your tools | Remote access section landing. | | `remote/access/ai-coding-agents.md` | AI coding agents | Using Remote with AI coding agents (was orphaned). | | `remote/access/mcp.md` | MCP server | Remote MCP tools + setup. | | `remote/access/duo.md` | GitLab Duo | Duo integration. | | `remote/access/glab.md` | glab CLI | `glab orbit` remote commands (links to CLI nav). | | `remote/access/api.md` | REST API | Endpoints + auth (links to API nav). | | `remote/examples/_index.md` | Examples | Example pages (former cookbook, no collapsibles). | | `remote/reference/_index.md` | Reference | Remote reference landing (builder/power-user). | | `remote/reference/query-dsl.md` | Query DSL (JSON) | Full DSL grammar. | | `remote/reference/schema.md` | Schema reference | 32 node types / 8 domains, generated from ontology. | | `remote/permissions.md` | Permissions | Roles, visibility, corrected `include_debug_sql` rule. | | `remote/data-and-compliance.md` | data handling, retention, compliance | | | `remote/billing.md` | Billing and credits | Metered source types (`mcp`, `rest`); credits terminology. | | `remote/troubleshooting.md` | Troubleshooting | Remote errors; CI-checked error strings. | | `local/_index.md` | GitLab Orbit Local | Local product landing. | | `local/get-started.md` | Get started | Install `orbit` → index → first query. | | `local/access/_index.md` | Connect your tools | Local access section landing. | | `local/access/cli.md` | orbit CLI | CLI usage (incl. `repo-map`, `skill`, `version`). | | `local/access/mcp.md` | MCP server | Local MCP tools (`run_sql`, `get_graph_schema`, `index`). | | `local/access/glab.md` | glab CLI | `glab orbit local` commands. | | `local/queries.md` | Query with SQL | DuckDB SQL; first-class (humans write this). | | `local/examples/_index.md` | Examples | Local example pages. | | `local/reference/_index.md` | Reference | Local reference landing. | | `local/reference/schema.md` | Schema reference | 4 node types, generated. | | `local/reference/cli.md` | orbit CLI reference | Every subcommand/flag | | `local/troubleshooting.md` | Troubleshooting | Local errors. | ## Implementation ### File mapping | Current file | New file | |--------------|----------| | `remote/getting-started.md` | `remote/getting-started.md` | | `remote/how-it-works.md` + `local/how-it-works.md` | `concepts.md` (shared; internals removed) | | `remote/indexing.md` + `local/indexing.md` | `indexed-data.md` (shared comparison) | | (new) | `remote/use.md` (one page with sections: turn on, dashboard, query editor & filters, schema explorer) | | (new) | `remote/data-and-compliance.md` (data handling, retention, compliance) | | `remote/queries/query-language.md` | `remote/reference/query-dsl.md` (demoted) | | `remote/schema.md` | `remote/reference/schema.md` | | `remote/cookbook.md` | `remote/examples/_index.md` (section; individual example pages as children) | | `remote/security.md` | `remote/permissions.md` (Remote role/visibility specifics) | | `remote/access/{duo,mcp,glab,api}.md` | `remote/access/{duo,mcp,glab,api}.md` (+ `remote/access/ai-coding-agents.md`), under `remote/access/_index.md` | | `local/getting-started.md` | `local/getting-started.md` | | `local/access/{cli,glab,mcp}.md` | `local/access/{cli,glab,mcp}.md`, under `local/access/_index.md` | | (implied local SQL) | `local/queries.md` (Query with SQL) | | `local/schema.md` | `local/reference/schema.md` | | `local/access/cli.md` (flags) | `local/reference/cli.md` | ## Audit <details> <summary>Audit of a sample of pages</summary> ## Page audit <table> <tr> <th>Page</th> <th>Notes and changes required</th> </tr> <tr> <td> [index.md](https://gitlab.com/gitlab-org/orbit/knowledge-graph/-/blob/main/docs/source/_index.md) </td> <td> Page doesn't follow [top level page standard](https://docs.gitlab.com/development/documentation/topic_types/top_level_page/#format). </td> </tr> <tr> <td> [remote/\_index.md](https://gitlab.com/gitlab-org/orbit/knowledge-graph/-/blob/main/docs/source/remote/_index.md) </td> <td> * Refactor wording (remove em dashes, improve punctuation, etc) * Remove "In this section" * **Billing:** * Remove and add info to general intro. * Clarify what "GitLab Duo Agent Platform queries are zero-rated." means (we don't use that term in any of the [billing related docs](https://docs.gitlab.com/subscriptions/gitlab_credits/)). * Check wording about MCP and REST API using GitLab Credits. According to https://docs.gitlab.com/user/duo_agent_platform/#beta-and-experiment-features, MCP doesn't use credits. * Move content from `security.md` and refactor content and heading titles. </td> </tr> <tr> <td> [remote/getting-started.md](https://gitlab.com/gitlab-org/orbit/knowledge-graph/-/blob/main/docs/source/remote/getting-started.md) </td> <td> * Overall this page is not usable and doesn't tell me anything about how or where to run the query. No mention of the Orbit dashboard or the query editor. * Need to reframe so that it suits specific audience. Is it for a Reporter who indexes or for an Owner who turns on Orbit, then indexes. If the former then reconsider "Step 1" section. * Functional info is buried between prerequisites and Step 1: * Orbit indexes top-level groups only. Subgroups and projects inherit indexing automatically. * What does this mean: "Subgroups and projects inherit indexing automatically." Requires more detail, too vague. * **Step 1 is incorrect**: * There is no **Orbit \> Configuration** and no **Indexes** list. * If you can only query a group after it's been indexed, how to know when it's been indexed, what does the indexing? **"Step 2 Run your first query":** * Doesn't actually tell you how to run a query. Do I run the query? If yes, where do I run it? Do I configure DAP, MCP, REST API to run a query? This section has vague conceptual information that doesn't give me any info. * **Install the Orbit skill for AI agents** doesn't really fit in Step 2, which is about running your first query. Should be in another section called, maybe 'Optimize your queries', or something like that...Possible on another page maybe. </td> </tr> <tr> <td> [remote/how-it-works.md](https://gitlab.com/gitlab-org/orbit/knowledge-graph/-/blob/main/docs/source/remote/how-it-works.md) </td> <td>Mixes user-relevant behavior (freshness, authorization scoping, retention) with internal implementation details (ClickHouse, CDC pipeline, JSON-to-SQL compilation) that has no user-facing benefit and is at risk of going stale.</td> </tr> <tr> <td> [ai_coding_agents.md](https://gitlab.com/gitlab-org/orbit/knowledge-graph/-/blob/main/docs/source/ai_coding_agents.md) </td> <td> * Needs TW review, no TWs on original review and no post-merge review according to file history. * Needs to be added to navigation.yml </td> </tr> <tr> <td> [remote/indexing.md](https://gitlab.com/gitlab-org/orbit/knowledge-graph/-/blob/main/docs/source/remote/indexing.md) </td> <td> Reference page that gives an overview of what's indexed. A couple of edits will bring this page up to align with docs guidelines and standards: * Top of page needs a short intro * Merge **What is not indexed** into this section. Consider using a reference table with yes/no Hugo shortcodes. * **Source code:** * Refactor wording to align with style guide. * **Supported languages:** * Needs a short intro to explain what the table describes. * Remove "Languages not currently indexed: Swift, COBOL, Terraform, YAML.". Docs only describe what's in the product. </td> </tr> <tr> <td> [remote/security.md](https://gitlab.com/gitlab-org/orbit/knowledge-graph/-/blob/main/docs/source/remote/security.md) </td> <td> The information in this page could be merged into a general landing page for Orbit remote (see note above). After merging content we can redirect then remove this page. </td> </tr> <tr> <td> [remote/cookbook.md](https://gitlab.com/gitlab-org/orbit/knowledge-graph/-/blob/main/docs/source/remote/cookbook.md) </td> <td> Information in the page is vague and difficult to follow. Content needs to be separated into separate pages and restructured. * **Intro paragraph**: "You do not write graph queries by hand. You ask an AI agent a question in plain language, and the agent uses Orbit to traverse the graph and answer." - This contradicts the instructions below, which tells users to edit JSON responses. **How to use this page - not a descriptive title and doesn't align with doc standards** * Information is vague and goal of section isn't clear * "Pick the outcome you want and copy its prompt". What is an outcome? Is it the content in code blocks in the rest of the page? * "Replace the values in `<angle brackets>` with your own group, project, file, or time window." This should be with each example, doesn't make sense on its own in a separate section. * We can remove this section entirely except for the first step, which is a requirement. Users know how to copy-paste content in code blocks. * Queries in each section are hidden in collapsible sections that violate standards in the [style guide](https://gitlab.com/gitlab-org/gitlab/-/blob/master/doc/development/documentation/styleguide/_index.md#collapsible-panels). **Changes required:** * Rename to "Prompt examples" or "Query examples". Use this [top-level page format](https://docs.gitlab.com/user/gitlab_duo/prompt_examples/) and link to each example page. * Check with engineering/PM if this should really be "Query examples"? If the prompt is what generates the query, and "query" is the established verb when talking about using Orbit, "Query examples" seems more aligned. * Create a page for each prompt example. Implement this [IA](https://docs.gitlab.com/user/gitlab_duo/prompt_examples/). * For each prompt example page: * Add a prerequisite that if the user wants to use external agents they need to connect through MCP or the CLI (provide links). No need to mention the default of using GitLab Duo Agent Platform. * Remove collapsible sections (_See the Orbit queries behind this_) and put content in page. * Work with engineering team to address these problems in the page: * Readers are told they never need to open the query JSON, then instructs them to edit values inside it (timestamp, merge request ID, file path). Clarify whether the JSON is read-only reference or something the reader edits mid-workflow, and add instructional text. * This page is providing for two readers at once: users typing plain-language prompts, and users who want the underlying query for the REST API. Decide whether query-reference content stays inline (unhidden, per style guide) or moves to link out to API/query-reference docs. This is an IA decision that we can figure out together when we know more. * See [this page](https://docs.gitlab.com/user/gitlab_duo/prompt_examples/refactor_legacy_code/) for inspiration (you don't have to follow this structure verbatim, adjust it where needed). * Needs more detail about prompts: * Where does the user enter the prompts? In Duo Chat? In the terminal? * **"prompt" vs. "query."** Terms are used as if their relationship is obvious, but it's never stated. Add a short explanation of whether the prompt generates the query, whether they're the same thing, or whether they're separate steps. * Prompts have the text 'Using Orbit'. Need to be clear that this is the way to instruct the agent to use Orbit, rather than standard indexing. Check if this a verbatim requirement or is there room for variation (probably the latter). Some of the information we learn here can feed into **Run a query** in the new Use Orbit page (mentioned above) </td> </tr> <tr> <td> [remote/schema.md](https://gitlab.com/gitlab-org/orbit/knowledge-graph/-/blob/main/docs/source/remote/schema.md) </td> <td> * Instruction to fetch live scheme is out of context without any indication of why or when the user would do this. * "Use these as entity names in your queries." Is this in the prompt, or in the JSON query? * Needs a query example of how to use entity name, node type, and key properties. * Requires explanation of what is in each entity: it includes the node type and key properties. </td> </tr> <tr> <td> [remote/queries/\_index.md](https://gitlab.com/gitlab-org/orbit/knowledge-graph/-/blob/main/docs/source/remote/queries/_index.md) </td> <td> * [Choose a query shape](https://docs.gitlab.com/orbit/remote/queries/#choose-a-query-shape) * Assumes the reader already knows what "traverse," "single- node and "bounded endpoint" mean in this system. But there are no docs anywhere about how the graph works. * No clear criteria for choosing between rows. "Follow relationships between known entity types" (multi-node traversal) vs. "Ask what is connected to one bounded node" (`neighbors`) seem like the same task described two ways. * Not all of the examples describe what's in the table. The three examples below all happen to use `traversal` — there's no example of `aggregation`, `path_finding`, or `neighbors`, so a reader can't check their understanding of the table against a concrete case for the shapes they're less sure about. * All the query info is in Query language Changes needed: * Remove this page. It has a lot of content that's confusing without the context from Query language, and there's nothing that connects the reader between the two pages. * Check if the examples repeat what's in https://docs.gitlab.com/orbit/remote/queries/query-language/#traversal-examples. If it repeats then don't move these over to https://docs.gitlab.com/orbit/remote/queries/query-language * For "Choose a query shape" section, update use cases so that there's less ambiguity. Rename to 'Use cases for query shapes' or something similar. </td> </tr> <tr> <td> [remote/queries/query-language.md](https://gitlab.com/gitlab-org/orbit/knowledge-graph/-/blob/main/docs/source/remote/queries/query-language.md) </td> <td> * **Text on the page needs more detail:** * Not clear what the difference is between REST API or `glab orbit remote query` * In general each section needs an introductory line before the table. For example, Query shapes, what makes it a shape? * Some sections have large walls of text that need to be refactored. Since this was AI generated need to confirm accuracy. </td> </tr> <tr> <td> [remote/access/duo.md](https://gitlab.com/gitlab-org/orbit/knowledge-graph/-/blob/main/docs/source/remote/access/duo.md) </td> <td>No useful information about how to use Orbit. Just general descriptions.</td> </tr> <tr> <td> [remote/access/mcp.md](https://gitlab.com/gitlab-org/orbit/knowledge-graph/-/blob/main/docs/source/remote/access/mcp.md) </td> <td> * **Connect your MCP client** * Poor structure, mass wall of text interspersed with code blocks that's difficult to read. * Several different applications that can be connected but these are buried, no heading hierarchy. * </td> </tr> </table> </details> MR checklist to implement the restructure: - [ ] Move `remote/getting-started.md` → `remote/getting-started.md` --\> No nav changes. Zach to refactor content; requires eng review and TW approval/merge. - [ ] Add `remote/billing.md`. - [ ] MR: https://gitlab.com/gitlab-org/orbit/knowledge-graph/-/merge_requests/2556 - [ ] Merge `remote/how-it-works.md` + `local/how-it-works.md` → `concepts.md` (shared; internals removed) --\> Adds a new page, redirects 2 pages to the new one, updates navigation.md - [x] Merge `remote/indexing.md` + `local/indexing.md` → `indexed-data.md` (shared comparison) --\> Adds a new page, redirects 2 pages to the new one, updates navigation.md; MR: https://gitlab.com/gitlab-org/orbit/knowledge-graph/-/merge_requests/2284 - [ ] Create (new) → `remote/use.md` (one page with sections: turn on, dashboard, query editor & filters, schema explorer) --\> New page, reuses some existing content, adds net new content for in-product UI - [ ] Move `remote/queries/query-language.md` → `remote/reference/query-dsl.md` (demoted) --\> Moves files in the repo, requires a redirect, updates navigation.md - [ ] Move `remote/schema.md` → `remote/reference/schema.md` --\> Moves files in the repo, requires a redirect, updates navigation.md - [ ] Move `remote/cookbook.md` → `remote/examples/_index.md` (section; individual example pages as children) --\> Creates a new page, redirects old to new, updates navigation.md - [ ] https://gitlab.com/gitlab-org/orbit/knowledge-graph/-/merge_requests/2561 - [ ] Move `remote/security.md` → `remote/permissions.md` (Remote role/visibility specifics) --\> Requires redirect, nav update - [ ] Move `remote/access/{duo,mcp,glab,api}.md` → `remote/access/{duo,mcp,glab,api}.md` (+ `remote/access/ai-coding-agents.md`), under `remote/access/_index.md` --\> Requires redirects, and nested pages for duo, mcp, glab, and api, nav changes - [ ] Move `local/getting-started.md` → `local/getting-started.md` --\> stays the same - [x] Move `local/access/{cli,glab,mcp}.md` → `local/access/{cli,glab,mcp}.md`, under `local/access/_index.md` --\> Requires redirects, nested subpages for cli, glab, mcp, nav updates - [x] MCP docs update: https://gitlab.com/gitlab-org/orbit/knowledge-graph/-/merge_requests/2303 - [x] Access _index page: https://gitlab.com/gitlab-org/orbit/knowledge-graph/-/merge_requests/2306 - [x] Adds _index page to nav, nests tooling pages: https://gitlab.com/gitlab-org/technical-writing/docs-gitlab-com/-/merge_requests/2552 - [ ] Adds a new `ai_coding_agents.md` file for the Local skill: https://gitlab.com/gitlab-org/orbit/knowledge-graph/-/merge_requests/2319 - [ ] Create (implied local SQL) → `local/queries.md` (Query with SQL) --\> New page - [ ] Move `local/schema.md` → `local/reference/schema.md` --\> Redirect and nav update - [x] Moves `schema.md` under `/reference` directory, refactors schema page content: https://gitlab.com/gitlab-org/orbit/knowledge-graph/-/merge_requests/2333 - [ ] Move `local/access/cli.md` (flags) → `local/reference/cli.md` --\> Redirect and nav update