> ## 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.

## September 14, 2026: refinement after the persona review

* [Get started](/quickstart), [introduction](/introduction) and the connection guides now lead with the hosted service. Local checks and the ledger are optional branches.
* Command pages state per-command availability from the deployed release instead of one global route caveat. [Release evidence](/release.json) separates deployed-source evidence from the dated live readback.
* Event feed pages and [HTTP conventions](/reference/http/conventions) explain that `next_cursor` is a checkpoint to keep even when `has_more` is false.
* [Import and verify](/guides/import-and-verify) leads with single-candidate verification; batch verification and candidate enrollment remain a labeled preview.
* Reference schema tables show compact field summaries with the complete table in an expandable section.

## September 15, 2026: AgentLinkOps naming and production version edbb3301

* Command pages, schemas, `commands.json`, `openapi.json` and [release evidence](/release.json) now come from production version `edbb3301`, deployed September 15, 2026 at 13:50 UTC from commit `fb95463`, which serves 73 authenticated commands. The MCP servers register as `agentlinkops` and `agentlinkops-free`.
* Every webhook delivery carries `AgentLinkOps-Signature`, `AgentLinkOps-Timestamp`, `AgentLinkOps-Delivery-Id` and `AgentLinkOps-Event-Type` alongside the `Linktrail-*` set with identical values. The [webhook reference](/reference/webhooks) and [guide](/guides/webhooks) document both sets and the signing procedure once.
* The CLI is `agentlinkops`, its variables are `AGENTLINKOPS_*`, and its ledger directory is `.agentlinkops/`; [migrate](/reference/local/migrate) renames an existing `.linktrail/`. The `linktrail` command, `LINKTRAIL_*` variables and `.linktrail/` directory remain compatibility aliases with a one-line notice until the dated cutover recorded under DP-0029-T05. [CLI configuration](/reference/local/configuration) lists the alias rules; [connect with the CLI](/guides/connect-cli) and the [ledger guide](/ledger) follow.
* The `setup` command page is gone: the released CLI has no such command.

## September 15, 2026: regenerated from production version 977394dd

* Command pages, schemas, `commands.json`, `openapi.json` and [release evidence](/release.json) now come from the source of production version `977394dd`, deployed September 15, 2026 at 13:33 UTC from commit `d3dac5f`. That release serves 73 authenticated commands.
* The audit corrections that earlier pages described ahead of release are live: configuration errors return `retryable: false`, secret rotation guidance covers the rotate-then-retire sequence, member errors name the fix, anchor reports use tokenizer version 2, vendor padding guidance left the domain-mix report, and the import commands document their row schemas. [Capability status](/capability-status) and [error recovery](/reference/errors) drop their dated caveats.
* Five competitor and discovery command descriptions follow the deployed wording.
* The [webhook reference](/reference/webhooks) labels the retained-history gap notification as a development preview. Version `977394dd` does not emit it; the authenticated feeds return `CURSOR_EXPIRED` instead. Its schema stays published without a fixture example.
* The three batch verification and enrollment preview commands leave the [command index](/reference/index) and navigation until their release. Their pages stay reachable by URL and keep the development label.
* [HTTP conventions](/reference/http/conventions) and the CLI `tools` / `call` pages date the September 14 catalog 404 and name the release that serves the routes.

## Development capabilities described by the September 13 revision

At the September 13 review, the current source supported 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 were development capabilities pending their matching hosted release. An authenticated production request to `GET /v1/commands` returned 404 on September 14, 2026 at 01:46 UTC. The September 14 parity release deployed those routes later that day; see the September 14 entry.

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.