From 5bcac0bac1d489d6a8b40360def40e006618b1c9 Mon Sep 17 00:00:00 2001
From: Will-thom <116388885+Will-thom@users.noreply.github.com>
Date: Sun, 31 May 2026 02:00:53 -0300
Subject: [PATCH] docs: keep first contribution labels

---
 ROADMAP.md                 | 1 +
 docs/labels.md             | 1 +
 docs/project-visual-map.md | 4 ++--
 3 files changed, 4 insertions(+), 2 deletions(-)

diff --git a/ROADMAP.md b/ROADMAP.md
index 68a629f..6792372 100644
--- a/ROADMAP.md
+++ b/ROADMAP.md
@@ -137,6 +137,7 @@ Issue quality standard:
 
 Preferred labels:
 
+- `good first issue`
 - `good first contribution`
 - `help wanted`
 - `area: parser`
diff --git a/docs/labels.md b/docs/labels.md
index f1ec819..66405b5 100644
--- a/docs/labels.md
+++ b/docs/labels.md
@@ -42,6 +42,7 @@ Use area labels to show the affected surface:
 
 Use these labels to signal contribution fit:
 
+- `good first issue`: GitHub-standard newcomer discovery label. Keep it alongside `good first contribution` so new contributors can find approachable work through GitHub search and issue filters.
 - `good first contribution`: low-context contribution with clear acceptance criteria.
 - `oss first friendly`: suitable for a first OSS pull request.
 - `help wanted`: maintainers are actively inviting implementation help.
diff --git a/docs/project-visual-map.md b/docs/project-visual-map.md
index 6ade29c..8fa92aa 100644
--- a/docs/project-visual-map.md
+++ b/docs/project-visual-map.md
@@ -150,13 +150,13 @@ flowchart LR
     READY["status: ready\nContributor can start"] --> PR["Focused PR\nTests/docs included"]
     BLOCKED["status: blocked\nNeeds dependency or design decision"] --> GATE["Wait for gate issue or dependency"]
     HELP["help wanted / need help\nMaintainer wants contributions"] --> READY
-    FIRST["good first contribution / oss first friendly\nLow context contribution"] --> READY
+    FIRST["good first issue / good first contribution / oss first friendly\nLow context contribution"] --> READY
 ```
 
 When in doubt:
 
 - Prefer `status: ready` issues for immediate work.
-- Prefer `good first contribution` or `oss first friendly` issues for new contributors.
+- Prefer `good first issue`, `good first contribution`, or `oss first friendly` issues for new contributors.
 - Avoid implementation-heavy Stage 3 issues until the related design contract issues are done.
 - Keep every issue tied to a stage label, area label, and status label.