docs: fix stale docs paths left over from the pre-Hugo site

AGENTS.md

@@ -77,5 +77,5 @@ Each substantial phase should leave behind beginner-friendly notes under `dev-no
 - how to test or use it
 
 When a phase adds or changes user-facing behavior, also update the published docs
-under `website/src/content/docs/` (the "Use Tau" guides and reference).
+under `website/content/` (the guides and reference).
 

CONTRIBUTING.md

@@ -109,7 +109,7 @@ For substantial architectural or phase-oriented work, add beginner-friendly note
 For user-facing behavior, update the published docs under:
 
 ```text
-website/src/content/docs/
+website/content/
 ```
 
 ## Release process

dev-notes/README.md

@@ -4,8 +4,8 @@ These are the internal, phase-by-phase build journals and design records for Tau
 They are **not** published on the docs site — they live here for contributors who
 want to trace how the system was assembled.
 
-User-facing documentation lives in `website/src/content/docs/` and is published at
-<https://alejandro-ao.github.io/tau/>.
+User-facing documentation lives in `website/content/` and is published at
+<https://twotimespi.dev/>.
 
 ## Contents
 

website/content/contributing.md

@@ -64,4 +64,4 @@ templates in `website/layouts/`.
 Each substantial phase should leave beginner-friendly notes in `dev-notes/`
 explaining what was added, why it exists, how it maps to [Pi](https://pi.dev)'s
 design, and how to test or use it. When a feature is user-facing, also update or
-add the relevant page under `website/src/content/docs/`.
+add the relevant page under `website/content/`.