> ## Documentation Index
> Fetch the complete documentation index at: https://docs.agentlinkops.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Documentation changelog

> Track changes to the documentation structure and distinguish documentation updates from locally implemented product capabilities and hosted releases.

This page tracks documentation changes. Product availability has its own [status page](/capability-status); publishing an operation reference does not deploy that operation.

## September 13, 2026: documentation revision

The documentation now groups guides by the task you want to complete and reference pages by capability. Shared operation pages place MCP, CLI and HTTP requests together, with dedicated sections for local commands and repository context.

* Added connection paths for [MCP](/guides/connect-mcp), [CLI](/guides/connect-cli) and [HTTP](/guides/connect-http).
* Added a [first-result tutorial](/guides/first-result), workflow guides and [troubleshooting](/guides/troubleshooting).
* Added [common schemas](/reference/schemas), [error recovery](/reference/errors) and detailed reference coverage.
* Preserved the earlier introduction, quickstart, campaign, ledger, evidence and capability-status URLs. Existing tool-category routes remain entry points to individual operations.

Start with the [overview](/introduction) to choose a task. Existing customers can continue using their saved guide URLs.

## Development capabilities described by this revision

The current source supports the shared authenticated operations through MCP, generic HTTP commands and CLI `tools` / `call`, plus one anonymous check. The generic HTTP command catalog and execution routes are development capabilities pending their matching hosted release. An authenticated production request to `GET /v1/commands` returned 404 during this documentation review.

Newly registered shared bindings include `get_project`, `list_check_jobs`, `get_link_reports`, `get_link_evidence`, `get_target_evidence`, `delete_webhook` and `list_workspace_events`. Registration and documentation do not establish their presence in the hosted MCP catalog; existing resource routes have their own release history.

Batch candidate verification and explicit candidate enrollment have local validation and need their matching server migrations and release. Their guides show the sequence and the available single-candidate path where batch admission is unavailable.

No product release is claimed by this changelog entry. Confirm the connected catalog, required scopes and [availability boundaries](/capability-status) before adopting a newly documented operation. Use [error recovery](/reference/errors) when the connected server rejects it.