Community/labels audit

[EbukaMoses]

Description

Audit of the issue backlog and addition of "good first issue" labels for easy, newcomer-friendly tasks. Adds an audit document and a script so maintainers can apply the label to 10 selected issues. No application code changes; lowers the entry barrier for new contributors.

Related Issue

Closes #131

Changes Made

• docs/community/LABELS_AUDIT.md – Audit doc with criteria, list of 10 issues to label (with rationale), verification link, and instructions for applying labels (UI or script).
• scripts/label-good-first-issue.sh – Script to add the "good first issue" label to those 10 issues via the GitHub API (uses GITHUB_TOKEN; default repo dotandev/hintents).

List of updated issues (non-code change):

#	Title
32	Source ID/Link
81	29. [Decoder] Implement Trace visualization in CLI
84	32. [Decoder] Suggestion engine for common errors
86	34. [UX] Create Dockerfile for reproducible environment
87	35. [UX] Add doctor command for environment verification
114	62. [QA] Implement static analysis for Rust simulator
116	64. [QA] Implement dead code detection for Go codebase
130	78. [Docs] Add "Cookbook" for common debugging scenarios
131	79. [Community] Add "Good First Issue" labels
162	59. [Test] Add unit tests for ledger entry hashing

Testing

• Confirmed docs/community/LABELS_AUDIT.md lists 10 issues and criteria.
• Confirmed scripts/label-good-first-issue.sh contains the same 10 issue numbers and is executable.
• Labels can be verified after merge by filtering: good first issue (apply via UI or by running the script with GITHUB_TOKEN).

Checklist

• Documentation updated
• Tests passing
• Code follows project style guidelines

[dotandev]

fix conflicts.