Start with seeded docs issues.

Docs issue type: Good-first-docs
Seed ID: GFD-001
Title: Clarify ObjectDB quickstart cleanup wording
Product: ObjectDB
Public route: /products/objectdb/quickstart/
Content type: quickstart
Labels: good-first-docs, product:objectdb, type:quickstart
Why this is good first: The work is wording-only and can be validated against the existing quickstart flow.
Expected docs outcome: Cleanup language tells readers what resource names are deleted, what success looks like, and which limits remain linked.
Review routing: ObjectDB product SME and docs QA
Guardrail: Do not change S3 Core support claims or add durability, availability, or AWS parity wording.
Sensitive details removed: yes
Private source paths needed before triage: no

Docs issue type: Good-first-docs
Seed ID: GFD-002
Title: Add ObjectDB limits cross-links from S3 SDK examples
Product: ObjectDB
Public route: /products/objectdb/guides/s3-sdk-examples/
Content type: guide
Labels: good-first-docs, product:objectdb, type:guide
Why this is good first: The change only adds nearby links to existing limits and compatibility pages.
Expected docs outcome: SDK examples make the unsupported S3 families easier to find before readers copy sample code.
Review routing: ObjectDB docs owner
Guardrail: Keep the examples illustrative unless docs QA accepts a stronger validation status.
Sensitive details removed: yes
Private source paths needed before triage: no

Docs issue type: Good-first-docs
Seed ID: GFD-003
Title: Improve ObjectDB evidence index scan labels
Product: ObjectDB
Public route: /products/objectdb/evidence/
Content type: evidence
Labels: good-first-docs, product:objectdb, type:evidence
Why this is good first: The work is table-copy cleanup around existing evidence records.
Expected docs outcome: Readers can distinguish route evidence, local adapter caveats, limits, examples, and operator runbooks at a glance.
Review routing: ObjectDB product SME and docs lead
Guardrail: Do not mark pending evidence accepted or promote verification-required claims.
Sensitive details removed: yes
Private source paths needed before triage: no

Docs issue type: Good-first-docs
Seed ID: GFD-004
Title: Add Message Broker queue glossary cross-links
Product: Message Broker
Public route: /products/message-broker/quickstart/
Content type: quickstart
Labels: good-first-docs, product:message-broker, type:quickstart
Why this is good first: The work links existing queue, cursor, replay, and worker terms without changing behavior.
Expected docs outcome: New readers can jump from queue-worker steps to the glossary and reference pages.
Review routing: Message Broker product SME
Guardrail: Do not imply Kafka wire compatibility or production replication guarantees.
Sensitive details removed: yes
Private source paths needed before triage: no

Docs issue type: Good-first-docs
Seed ID: GFD-005
Title: Tighten Message Broker runbook evidence handoff copy
Product: Message Broker
Public route: /products/message-broker/operations/operator-runbooks/
Content type: runbook
Labels: good-first-docs, product:message-broker, type:runbook
Why this is good first: The change improves support-package wording while staying inside the current runbook evidence table.
Expected docs outcome: The runbook names which route, status, tenant, stream, and redaction details belong in a support handoff.
Review routing: Support reviewer and Message Broker docs owner
Guardrail: Do not add support response-time, SLA, failover, or cross-site durability promises.
Sensitive details removed: yes
Private source paths needed before triage: no

Docs issue type: Good-first-docs
Seed ID: GFD-006
Title: Add Message Broker SDK example labels for validation mode
Product: Message Broker
Public route: /products/message-broker/guides/rust-sdk-examples/
Content type: guide
Labels: good-first-docs, product:message-broker, type:guide
Why this is good first: The page already separates example status; the issue asks for clearer labels and next-step links.
Expected docs outcome: Each example section makes compile/run status and reviewer-run rationale easier to scan.
Review routing: Docs QA and Message Broker product SME
Guardrail: Do not convert controlled-beta SDK examples into general production guidance.
Sensitive details removed: yes
Private source paths needed before triage: no

Docs issue type: Good-first-docs
Seed ID: GFD-007
Title: Clarify Concordia local token language
Product: Concordia
Public route: /products/concordia/quickstart/
Content type: quickstart
Labels: good-first-docs, product:concordia, type:quickstart
Why this is good first: The issue is a narrow wording pass around existing local bearer-token boundaries.
Expected docs outcome: Readers understand that local bearer tokens are development admission only and not production identity.
Review routing: Concordia product SME and security reviewer if wording changes
Guardrail: Do not add production JWT, identity-provider, or security assurance claims.
Sensitive details removed: yes
Private source paths needed before triage: no

Docs issue type: Good-first-docs
Seed ID: GFD-008
Title: Add Concordia validation runbook next-step links
Product: Concordia
Public route: /products/concordia/operations/validation-runbooks/
Content type: runbook
Labels: good-first-docs, product:concordia, type:runbook
Why this is good first: The change adds existing reference, compatibility, and limits links to completed runbook sections.
Expected docs outcome: Validation failures route readers to the right Cache, Gateway, Storage, TSDB, or compatibility reference.
Review routing: Concordia docs owner
Guardrail: Do not treat validation-script acceptance as production runtime proof.
Sensitive details removed: yes
Private source paths needed before triage: no

Docs issue type: Good-first-docs
Seed ID: GFD-009
Title: Make Concordia local curl examples easier to skim
Product: Concordia
Public route: /products/concordia/guides/local-curl-examples/
Content type: guide
Labels: good-first-docs, product:concordia, type:guide
Why this is good first: The work improves headings and expected-output scanability without changing commands.
Expected docs outcome: Each curl example clearly names service, local-only maturity, expected result, and cleanup notes.
Review routing: Docs QA and Concordia product SME
Guardrail: Keep Gateway alpha, local Cache, local Time Series, and Storage validation boundaries visible.
Sensitive details removed: yes
Private source paths needed before triage: no

Docs issue type: Good-first-docs
Seed ID: GFD-010
Title: Clarify LogDB tenant header troubleshooting
Product: LogDB
Public route: /products/logdb/quickstart/
Content type: quickstart
Labels: good-first-docs, product:logdb, type:quickstart
Why this is good first: The issue improves one common troubleshooting path already documented in the quickstart.
Expected docs outcome: Readers can tell when `x-logdb-tenant` and OTLP resource tenant attributes disagree.
Review routing: LogDB product SME
Guardrail: Do not add multi-tenant isolation, compliance, or external auth guarantees.
Sensitive details removed: yes
Private source paths needed before triage: no

Docs issue type: Good-first-docs
Seed ID: GFD-011
Title: Improve LogDB collector example expected-output labels
Product: LogDB
Public route: /products/logdb/guides/otel-collector-examples/
Content type: guide
Labels: good-first-docs, product:logdb, type:guide
Why this is good first: The page already has examples; this issue asks for clearer section labels and validation notes.
Expected docs outcome: Collector and curl examples make ingest, query, tenant header, and cleanup expectations easier to compare.
Review routing: Docs QA and LogDB docs owner
Guardrail: Keep local-dev policy warnings and live-route boundaries visible.
Sensitive details removed: yes
Private source paths needed before triage: no

Docs issue type: Good-first-docs
Seed ID: GFD-012
Title: Add LogDB limits links near S3 query-read wording
Product: LogDB
Public route: /products/logdb/reference/otlp-query/
Content type: reference
Labels: good-first-docs, product:logdb, type:reference
Why this is good first: The work links existing limits and compatibility rows from current S3 query-read copy.
Expected docs outcome: Readers understand the difference between retained segment query, S3 query-read, BYOC notes, and future live S3 publication.
Review routing: LogDB product SME and docs lead
Guardrail: Do not imply S3-backed publication or BYOC availability beyond the current status labels.
Sensitive details removed: yes
Private source paths needed before triage: no

Docs issue type: Good-first-docs
Seed ID: GFD-013
Title: Add glossary terms for maturity and evidence language
Product: Cross-product
Public route: /glossary/
Content type: glossary
Labels: good-first-docs, product:cross-product, type:glossary
Why this is good first: The issue adds or tightens definitions without changing product-specific behavior.
Expected docs outcome: Glossary entries help readers distinguish Live, Controlled Beta, Preview Contract, Future, and Verification Required language.
Review routing: Docs lead
Guardrail: Keep definitions aligned with the maturity label source of truth.
Sensitive details removed: yes
Private source paths needed before triage: no

Docs issue type: Good-first-docs
Seed ID: GFD-014
Title: Seed search synonyms for community starter tasks
Product: Cross-product
Public route: /search/
Content type: search
Labels: good-first-docs, product:cross-product, type:search
Why this is good first: The issue is a low-risk search-index keyword update tied to existing public routes.
Expected docs outcome: Searches for starter issue, good first docs, missing docs, and contribution help return the Community routes.
Review routing: Docs platform reviewer
Guardrail: Do not add hidden routes, private tracker names, or source-edit workflow keywords.
Sensitive details removed: yes
Private source paths needed before triage: no

Docs issue type: Good-first-docs
Seed ID: GFD-015
Title: Add troubleshooting index links from support entry points
Product: Cross-product
Public route: /support/
Content type: operations
Labels: good-first-docs, product:cross-product, type:support
Why this is good first: The work adds links between existing support, troubleshooting, and privacy-safe handoff pages.
Expected docs outcome: Readers with docs gaps, operational symptoms, or support evidence questions can choose the right next route.
Review routing: Support reviewer and docs lead
Guardrail: Do not add support SLA, escalation-time, or product bug intake promises.
Sensitive details removed: yes
Private source paths needed before triage: no