25d19f4f8f
## What changed? In `docs/architecture/history-service.md`, links pointed at `service/history/workflow_task_handler_callbacks.go`. That file no longer exists on `main` — its handlers were extracted into `service/history/api/respondworkflowtaskcompleted/` (PRs #5902, #5904, #5905, #5908, #5931, May 2024). Repointed the dead links to the current code in `service/history/api/respondworkflowtaskcompleted/api.go`, pinned to commit `28dd23a` (current `main`), consistent with the doc's pinned-commit convention: **Line 171 — "Code entrypoints":** | Anchor text | Old (`workflow_task_handler_callbacks.go`) | New (`respondworkflowtaskcompleted/api.go`) | | --- | --- | --- | | handler | `handleWorkflowTaskCompleted` L371 | `Invoke` L110 | | accumulates updates | `handleCommands` call L562 | `handleCommands` call L416 | | calls | `UpdateWorkflowExecutionWithNewAsActive` L690 | `UpdateWorkflowExecutionWithNewAsActive` L623 | **Line 310 — "Call sites":** | Anchor text | Old | New | | --- | --- | --- | | `handleWorkflowTaskCompleted` → `Invoke` | `workflow_task_handler_callbacks.go` L690 | `respondworkflowtaskcompleted/api.go` L623 | ## Why? The old blob links were stale link-rot pointing at code that has since moved, so readers following them landed on a deleted file path on `main`. ## How did you test it? - [x] verified each new anchor resolves to the intended symbol at the pinned commit (`git show origin/main:.../api.go` lines 110/416/623) - [x] covered by existing tests (docs-only change) ## Potential risks Docs-only change. Links are pinned to a commit SHA, so line numbers stay stable, but they will drift from `HEAD` over time like the rest of the doc's pinned links. 🤖 Generated with [Claude Code](https://claude.com/claude-code) --------- Co-authored-by: Gokhan Tekkaya Co-authored-by: Claude Opus 4.8
Temporal Server Documentation
This folder contains docs for those working closely with the Temporal server. If you are more interested in just authoring workflows, see our Getting Started Guide.
Core Documentation Sections
Architectural Diagrams (/architecture)
This section contains high-level explanations of Temporal's architecture and core concepts. It is designed to be useful for both server developers and those interested in understanding the technological underpinnings of Temporal. Detailed diagrams and descriptions can be found there.
Development Instructions (/development)
Here, you'll find guides to setting up a local development environment, along with potentially more advanced topics such as adding migrations or new Remote Procedure Calls (RPCs). This section is essential for developers looking to contribute to the Temporal codebase or understand its inner workings.
Operational Guides (/admin)
This section provides reference materials for administrators responsible for deploying Temporal in a production environment. It is pretty bare for now, but it is intended to covers topics like spinning up a production environment, configuring it, and monitoring it with metrics and dynamic configurations. For now, you can find this info on the Temporal docs website at https://docs.temporal.io/self-hosted-guide.