docs: update README.adoc for current build tooling

- Fix prerequisites: Node.js + Podman (not asciidoctor)
- Note that build includes lychee and CQA automatically
- Fix lychee section: clarify manual vs automatic, remove false claim
  that orchestrator downloads lychee
- Fix [code,terminal] to [source,terminal]
- Fix missing link: prefix on RHDHPAI URL
- Add link to architecture documentation
- Remove redundant ccutil preference note

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

Author: themr0c

README.adoc

@@ -10,9 +10,9 @@ Before submitting a pull request (PR), create a Jira issue associated with your
 
 There are currently three Jira projects related to RHDH:
 
-* link:https://issues.redhat.com/projects/RHDHBUGS[RHDHBUGS] - For issues related to existing content.
-* link:https://issues.redhat.com/projects/RHIDP[RHIDP] - For new features related to the core platform, including security mechanisms.
-* https://issues.redhat.com/projects/RHDHPAI[RHDHPAI] - For new features related to plugins and AI.
+* link:https://redhat.atlassian.net/jira/software/c/projects/RHDHBUGS/issues[RHDHBUGS] - Red Hat Developer Hub Bugs.
+* link:https://redhat.atlassian.net/jira/software/c/projects/RHIDP/issues[RHIDP] - Red Hat Internal Developer Platform.
+* link:https://redhat.atlassian.net/jira/software/c/projects/RHDHPLAN/issues[RHDHPLAN] - RH Developer Hub Planning.
 
 Choose a Jira project that matches your contribution and create a new issue:
 
@@ -23,9 +23,8 @@ Choose a Jira project that matches your contribution and create a new issue:
 
 [IMPORTANT]
 ====
-RHDH release notes are single-sourced from the *Release Notes Text* field in the Jira Epic.
-If you want to make changes to release notes, you must make them in Jira.
-Check the link:https://docs.google.com/document/d/1X2CrrU9K3ZqbxN7DXmU6P1mY7inLD32qs3rpOUHz6Vw/edit?tab=t.0#heading=h.yqxd252ryhua[RHDH Release Notes process document] for more information.
+RHDH release notes are single-sourced from Jira.
+See the link:https://docs.google.com/document/d/1X2CrrU9K3ZqbxN7DXmU6P1mY7inLD32qs3rpOUHz6Vw/edit?tab=t.0#heading=h.yqxd252ryhua[RHDH Release Notes process document] and the link:https://gitlab.cee.redhat.com/red-hat-developers-documentation/red-hat-developer-hub-release-notes[release notes repository] (VPN required) for details.
 ====
 
 ## Style and formatting
@@ -46,36 +45,64 @@ to modularize your content.
 
 ## Building locally
 
-. Install `asciidoctor` - see https://docs.asciidoctor.org/asciidoctor/latest/install/linux-packaging/
-. Install Podman - see https://podman.io.
-. Run the following command to generate html with images in titles-generated/ folders by using `ccutil` in a container.
-The `ccutil` CLI tool reproduces the behavior of the production publication chain (Pantheon), including its limitations, and is therefore preferred over using a more recent `asciidoctor` CLI version.
+.Prerequisites
+
+* link:https://nodejs.org[Node.js]
+* link:https://podman.io[Podman]
+* link:https://github.com/errata-ai/vale[Vale]
+* link:https://github.com/lycheeverse/lychee[Lychee] (downloaded automatically by the build script if not installed)
+* Optional: A `GITHUB_TOKEN` environment variable to avoid GitHub API rate limiting during lychee link validation. Use link:https://cli.github.com[GitHub CLI] (`gh`) to get and refresh the token: `export GITHUB_TOKEN=$(gh auth token)`
+
+.Procedure
+
+. Sync the Vale style rules:
++
+[source,terminal]
+----
+$ vale sync
+----
+
+. Build HTML with images in `titles-generated/` using `ccutil` in a container, then run lychee link validation and CQA content quality checks:
 +
 [source,terminal]
 ----
-$  build/scripts/build-ccutil.sh
+$ ./build/scripts/build-ccutil.sh
 ----
++
+The `ccutil` CLI tool reproduces the behavior of the production publication chain (Pantheon), including its limitations, and is therefore preferred over `asciidoctor`.
+
+Results are written to `build-report.json`.
 
 ## Checking for broken links
 
-You can run `lychee` locally to check for broken links in your PR.
+The build command above includes lychee link validation automatically.
+To run lychee separately on already-built HTML:
 
-. Build the documentation first (see above).
-. Run lychee on the generated HTML:
+.Prerequisites
+
+* link:https://github.com/lycheeverse/lychee[Lychee]
+* Optional: A `GITHUB_TOKEN` environment variable to avoid GitHub API rate limiting. Use link:https://cli.github.com[GitHub CLI] (`gh`) to get and refresh the token: `export GITHUB_TOKEN=$(gh auth token)`
+
+.Procedure
+
+. Run lychee on the built HTML:
 +
 [source,terminal]
 ----
-$ GITHUB_TOKEN=$(gh auth token) lychee titles-generated/
+$ lychee titles-generated/
 ----
-+
-Install lychee from https://github.com/lycheeverse/lychee or the build orchestrator downloads it automatically.
 
-You can run `linkchecker` to check for broken links in the published RHDH docs.
+To check for broken links in the published RHDH docs, use `linkchecker`:
+
+.Prerequisites
+
+* link:https://github.com/linkchecker/linkchecker[linkchecker]
+
+.Procedure
 
-. Install `linkchecker` from https://github.com/linkchecker/linkchecker.
 . Run the following command to create a .txt file with a list of detected broken links:
 +
-[code,terminal]
+[source,terminal]
 ----
 $ linkchecker --check-extern --output failures --file-output failures/broken-links.txt https://docs.redhat.com/en/documentation/red_hat_developer_hub/<version>
 ----
@@ -93,6 +120,8 @@ The publication workflow has two stages:
 . The link:.github/workflows/pr.yml[PR workflow] and link:.github/workflows/build-asciidoc.yml[GitHub Pages workflow] build HTML from AsciiDoc sources and push the output to the `gh-pages` branch using `build/scripts/deploy-gh-pages.js`, which handles concurrent pushes with automatic retry, cleanup of stale PR/branch directories, and index regeneration.
 . The link:https://github.com/redhat-developer/red-hat-developers-documentation-rhdh/actions/workflows/pages/pages-build-deployment[GitHub Pages build and deployment] workflow, managed by GitHub, detects pushes to the `gh-pages` branch and publishes the content to GitHub Pages.
 
+See link:docs/github-publication-workflow.md[GitHub Publication Workflow Architecture] for the full technical reference.
+
 ## Reviews
 
 All PRs are reviewed for technical accuracy by an SME and writing quality by another tech writer.