Cut Home.md's inline "How you get access" paragraph back to a link #222

Dependency

• Replace the TBD stub on the Permission Levels for Team Members wiki page #196 — Replace the TBD stub on the Permission Levels for Team Members wiki page

Overview

We need to cut the wiki landing page's inline "How you get access" paragraph back to a link once the Permission Levels page has real content, because that paragraph is only carried inline as a stopgap and will otherwise become a second source of truth that drifts from the page it duplicates.

Action Items

• Wait for Replace the TBD stub on the Permission Levels for Team Members wiki page #196 to land, then read the result before editing anything. Confirm Permission Levels for Team Members actually answers how someone gets added, not only what the levels are. If it does not, this ticket has nothing to point at — raise that on Replace the TBD stub on the Permission Levels for Team Members wiki page #196 rather than working around it here.
• Replace the How you get access paragraph in Home.md, in the "Joining the DevOps team" section, with a one-line pointer to that page. The paragraph to remove begins "Write access is not something you request on its own".
• Keep the bullet list directly beneath it. Permission levels for Team Members is already its first entry, so check whether the new pointer duplicates that bullet and keep only one of the two.
• Leave the rest of the section alone. The do-not-fork statement, the automatic-close warning and the "Why" paragraph are separate content, agreed as-is on Say on the wiki that contributors do not fork #211.
• Check CONTRIBUTING.md's "Getting write access" section at the same time. It is being rewritten separately to describe how access is obtained; once both land, the wiki page should be the one statement and the other two should link to it rather than restate it.
• After pushing, load the live rendered wiki and walk the path a new member takes — landing page → "Joining the DevOps team" → Permission Levels — and confirm the question is answered exactly once, with no dead end. A wiki change has no pull request and no diff for anyone to review, so this check is the only review it gets.

Resources/Instructions

• The page to edit: Home — the paragraph is in the "Joining the DevOps team" section
• The page it should point at: Permission Levels for Team Members — three lines reading TBD as of 2026-09-07
• Why the paragraph exists at all: writing it inline was a deliberate deviation from #211's third action item, agreed 2026-09-06, precisely because linking a new member to a TBD stub would have sent them to a dead end. This ticket is the other half of that decision, which is why it is blocked rather than merely related.
• The wiki is a separate git repo (devops.wiki), not part of hackforla/devops. git pull immediately before starting and again immediately before pushing — other people edit it through the web UI and a push can be rejected mid-task.