[pulsingSignal]

Description

Google Drive and Google Docs now open .md files natively in Markdown mode, where inline HTML formatting (<strong>, <a href='...'>, <br/>) is displayed as raw text instead of rendered formatting. Because operators copy docs/ddg.md into Google Docs to fill out the Variables table, those inline HTML tags appear literally in the table cells.

This change replaces the inline HTML in the docs/ddg.md header table (lines 5–9) and Variables table (lines 66–78) with standard Markdown:

• Replaces all 23 <strong>...</strong> tags with **...**
• Replaces the two <a href='...'>...</a> links (Console Link and compliance regime) with Markdown links [...](...)
• Replaces <br/> in the Customer ID description with a space, matching the adjacent gcloud organizations list rows

Fixes #397

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update

Deployment & Compliance Impact

• Applicable Regimes:
  • US Region Restricted (e.g., Access Policy constraint)
  • FedRAMP Moderate
  • FedRAMP High
  • DoD IL4
  • DoD IL5
  • General / All
• NIST 800-53r5 Controls: None (formatting-only documentation update).

Checklist

Code Quality & Reusability

• My code adheres to the Maximize Reusability principle. I have not redefined common elements and have reused existing base configurations and modules where possible.
• I have checked that no existing module or configuration in modules/ or fast/stages-aw/ can be leveraged for this change.
• My code follows the established naming conventions outlined in docs/naming-convention.md.

Documentation

• I have updated the README.md of the modified module or blueprint.
• I have added/updated documentation for inputs (variables) and outputs.

Security

• My change adheres to GCP security best practices and the principle of least privilege.
• I have ensured compliance with the targeted regime (FedRAMP Moderate, FedRAMP High, IL4, IL5, etc.).

Testing

• I have tested my changes locally.
• I have included details of my testing in this PR.

Testing Performed

• Verified no inline <strong>, <a>, or <br> HTML tags remain in docs/ddg.md (! grep -nE '</?(strong|a|br)\b' docs/ddg.md)
• Verified Markdown link validity with uv run --locked python tools/check_links.py docs (all 28 links in docs/ddg.md pass)
• Ran repository and CLI documentation sync tests (uv run pytest in cli/tests/test_repo.py)

[google-cla]

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

[aghassemlouei]

Verified docs/ddg.md with tools/check_links.py, GFM AST parsing, and cli/tests/test_repo.py. All 23 <strong> replacements, both Markdown link conversions, and the Customer ID <br/> cleanup render cleanly with all six CI checks passing.

Before merging, cla/google is failing on b20011f3 because 352168058+pulsingSignal@users.noreply.github.com is not matched to an active CLA record at cla.developers.google.com. Amending the commit author email to a CLA-covered address attached to @pulsingSignal, or adding this noreply address to the CLA group and running a rescan, will clear the check.

[aghassemlouei]

On line 44, the unmatched double backtick causes CommonMark and Google Docs Markdown mode to parse <stage-name> as the sole remaining raw InlineHTML tag in docs/ddg.md while GitHub strips <stage-name> from the rendered page, and Stages 0 through 3 write <stage-name>.auto.tfvars.json without -tfvar:

-completion of a stage, the Terraform code will write out a **``<stage-name>`-tfvar.auto.tfvars.json`** file to the Google Cloud Storage
+completion of a stage, the Terraform code will write out a **`<stage-name>.auto.tfvars.json`** file to the Google Cloud Storage