docs: rename guides to canonical cross-SDK filenames (1/3)

[ambiorix2099]

First of three PRs aligning this SDK's documentation information architecture with the Java and Python SDKs.

This PR is mechanical only. No prose was edited; every judgment call is deferred to PR #274 / #275.

Commit	Change
462d0d8	four git mvs — 0 insertions / 0 deletions
6dedeb6	the internal links those renames affected, plus the first redirect stub
2241f21	three further redirect stubs (see correction below)

Renames

Before	After
docs/workers_sdk.md	docs/workers.md
docs/workflow_sdk.md	docs/workflows.md
docs/migration_guide.md	docs/upgrading.md
docs/api_client/tls_configuration.md	docs/security.md

Redirect stubs — corrected count

An earlier revision of this description said only two paths in the whole rename set were referenced externally. That was wrong. It came from gh search code, which truncates results and is not an exhaustive index. Reading conductor-oss/conductor's docs/documentation/clientsdks/go-sdk.md directly shows nine links into this repository's docs/ tree, covering six retired paths.

Four of those are renamed by this PR, so all four keep a pointer-only stub at the old path:

Stub kept at	Points to	Upstream line(s)
docs/workers_sdk.md	docs/workers.md	147, 255
docs/workflow_sdk.md	docs/workflows.md	256
docs/migration_guide.md	docs/upgrading.md	252, 258
docs/api_client/tls_configuration.md	docs/security.md	260

Without them, five links in the published OSS documentation would 404 the moment this merges. The remaining two upstream-referenced paths are handled in #274.

Repointing the upstream links is tracked in conductor-oss/conductor#1417; all six stubs are deleted together once that lands. PR #275 adds a test asserting they stay pointer-only in the meantime, so they cannot quietly grow back into guides.

Note for reviewers: the diff stat is badly misleading

GitHub reports roughly +1192/-1152, which looks like wholesale content rewriting. It is not. Every one of the four old paths is reoccupied by its stub, so at the PR's end state both the old and new file exist and Git's rename detection has nothing to pair. Locally, with copy detection enabled:

$ git diff --stat -C --find-copies-harder main...HEAD
 10 files changed, 37 insertions(+), 1153 deletions(-)

Review commit-by-commit, not the squashed diff. 462d0d8 is 0/0 and shows the renames cleanly; the real changes are 37 lines across 6dedeb6 and 2241f21.

Why rename at all

The value of canonical filenames is that a reader — or a tool — following the Java/Python convention finds the same page name in any Conductor SDK. Today docs/observability.md and friends simply aren't there.

Worth stating plainly, since it motivated the original request: the Python docs_cleanup PR also renamed AGENTSPAN_* environment variables to CONDUCTOR_AGENT_*. That half does not apply here — this repo has zero occurrences of agentspan in any casing, and sdk/settings/env.go is already uniformly CONDUCTOR_*. No runtime behaviour changes anywhere in this series.

Verification

• All 55 relative .md links across README.md, CHANGELOG.md, and docs/ resolve on disk
• All four stubs are 10 lines, contain no code fences, and link to their replacement
• CHANGELOG.md's anchored links into docs/metrics.md are untouched here; that file is renamed in docs: merge sibling guides, add hub and meta pages, restructure README (2/3) #274, where its headings are preserved verbatim so the anchors survive

What follows

• docs: merge sibling guides, add hub and meta pages, restructure README (2/3) #274 (content) — the two merges, docs/README.md hub, compatibility.md, documentation-parity.md, documentation-standard.md, core-quickstart.md, README restructure, ADR 0001
• test: assert documentation structure, add link validation to CI (3/3) #275 (validation) — docs_test.go, Dockerfile COPY /docs, lychee link-check workflow

Backlog for the pages Go still lacks: #266 #267 #268 #269 #270 #271 #272

🤖 Generated with Claude Code

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

Flag	Coverage Δ
integration-tests-v4	56.35% <ø> (-0.15%)	⬇️
integration-tests-v5	30.99% <ø> (+1.94%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.
see 3 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.