chore: update stale references for monorepo consolidation

[zastrowm]

Description

Update URLs, paths, and content across the repository to reflect that sdk-python, sdk-typescript, and docs are now a single monorepo. This addresses the P0 items from the post-merge cleanup tracker.

Package metadata:

• strands-ts/package.json: repository/bugs/homepage URLs → sdk-python
• strands-py-wasm/pyproject.toml: Homepage/Bug Tracker → sdk-python
• strands-wasm/README.md: clone URL → sdk-python

Root docs restructured for monorepo:

• AGENTS.md: stripped to monorepo layout + shared conventions only (was 700+ lines of TS-specific content)
• strands-ts/AGENTS.md: new file with all TypeScript-specific patterns extracted from root
• README.md: added monorepo layout table, multi-language dev instructions
• CONTRIBUTING.md: added TypeScript SDK and docs site sections

Sub-project docs:

• strands-py/AGENTS.md: fixed directory tree root name
• site/AGENTS.md: removed stale private-docs-staging references, fixed TS SDK link
• designs/README.md: "Create a branch in this repository" (was "fork the docs repo")

Templates:

• .github/ISSUE_TEMPLATE/config.yml: docs link → strandsagents.com
• .github/PULL_REQUEST_TEMPLATE.md: docs section → "include changes under site/"

Agent skills:

• .agents/skills/strands-review/SKILL.md: local paths for team docs, removed stale monorepo-imminent comment
• .agents/references/code-verification.md: fixed API paths for monorepo layout

Site contribution guides:

• documentation.mdx: clone instructions → sdk-python/site
• core-sdk.mdx: unified repo clone, fixed CONTRIBUTING links
• feature-proposals.mdx: designs folder → sdk-python tree

Related Issues

#2286

Documentation PR

N/A — this PR updates docs references.

Type of Change

Documentation update

Testing

• I ran hatch run prepare

Checklist

• I have read the CONTRIBUTING document
• I have added any necessary tests that prove my fix is effective or my feature works
• I have updated the documentation accordingly
• I have added an appropriate example to the documentation to outline the feature, or no new docs are needed
• My changes generate no new warnings
• Any dependent changes have been merged and published

---

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[github-actions]

Assessment: Approve

Clean, well-scoped documentation update that correctly addresses the P0 monorepo consolidation items. URLs, paths, and content all point to the right places for the new monorepo layout.

Review Notes

• Correctness: All updated URLs/paths verified correct — strands-py/, strands-ts/, site/team/ references resolve properly.
• Scope: The PR appropriately limits itself to P0 items from the tracker. Remaining sdk-typescript references in site content pages (blog posts, user guides, discussions links) are reasonable to defer.
• Tier 1 staleness: One inline comment noting that code-verification.md Tier 1 paths are now inconsistent with the Tier 2 fix in this PR — low priority, likely a separate follow-up.

Nice job extracting the TS-specific AGENTS.md content into its proper sub-project location — the root AGENTS.md is much more navigable now.

[github-actions]

Documentation Preview Ready

Your documentation preview has been successfully deployed!

Preview URL: https://d3ehv1nix5p99z.cloudfront.net/pr-cms-2358/docs/user-guide/quickstart/overview/

Updated at: 2026-05-28T18:26:45.407Z

[github-actions]

Assessment: Approve

Well-scoped documentation update that correctly addresses the P0 monorepo consolidation items. All URL and path changes verified correct.

Review Details

• Correctness: Package metadata, root docs, site content, and template updates all point to the right monorepo paths. Relative paths from site/AGENTS.md (../team/) resolve correctly after the team/ directory move.
• Scope: Appropriately limited to P0 items. The ~30 remaining sdk-typescript references (blog posts, design doc PR links, downstream content pages) are reasonable to defer.
• One suggestion: Tier 1 paths in code-verification.md are inconsistent with the Tier 2 fix — see inline comment. Low priority, likely a follow-up item since clone-sdks.ts itself needs a monorepo refactor.