docs: update uf init docs to reflect --no-embeddings default

[yvonnedevlinrh]

Summary

Updates documentation across 4 content pages to reflect the upstream
behavioral change from unbound-force/unbound-force#321: uf init --force
now passes --no-embeddings to dewey index, deferring embedding
generation for faster initialization.

Closes #211

Changes

File	What changed
content/docs/getting-started/knowledge.md	Step 3 of "What uf init Creates" now shows dewey index --no-embeddings with cross-reference to Global CLI Flags table
content/docs/getting-started/developer.md	--force flag table row and Sub-Tool Initialization section both note --no-embeddings deferral
content/docs/reference/cli.md	--force flag description updated to mention --no-embeddings
content/docs/getting-started/common-workflows.md	Setup workflow description updated to dewey index --no-embeddings

All pages include guidance to run dewey index separately to generate
embeddings for semantic search.

The blog post (dewey-knowledge-retrieval.md) was reviewed and left
unchanged — its mention of uf init is general enough to remain accurate.

Spec artifacts

OpenSpec change: openspec/changes/uf-init-no-embeddings-docs/

• proposal.md — motivation, affected pages, constitution alignment
• specs/content-accuracy.md — delta requirements with Given/When/Then scenarios
• design.md — 4 decisions (in-place edits, DRY cross-refs, skip release notes, minimal blog update)
• tasks.md — 5 content tasks + 3 verification tasks, all complete

Review council

6/6 APPROVE (adversary, architect, guard, testing, sre, curator). No
REQUEST CHANGES findings.

Verification

• npm run build passes (140 pages)
• Grep sweep: all uf init + dewey index references checked, no stale content
• Constitution alignment: Content Accuracy (I), Minimal Footprint (II), Visitor Clarity (III) all PASS

[jflowers]

PR Review: #232 — docs: update uf init docs to reflect --no-embeddings default

Local Tool Results

Tool	Command	Status
Hugo build	npm run build	PASS (140 pages)

Walkthrough

File	Change	Focus
content/docs/getting-started/knowledge.md	Step 3 updated to dewey index --no-embeddings; cross-reference to Global CLI Flags	documentation
content/docs/getting-started/developer.md	--force flag table + Sub-Tool Init section note --no-embeddings deferral	documentation
content/docs/reference/cli.md	--force flag description updated for --no-embeddings	documentation
content/docs/getting-started/common-workflows.md	Setup workflow description updated to dewey index --no-embeddings	documentation

Linked Issues

Issue	Title	Criteria
#211	docs: uf init --force no longer hangs on Dewey reindexing	2/3 COVERED
		✓ Update uf init reference to note --no-embeddings default
		✓ Document how to trigger embedding generation separately
		⏸ Note in release notes (deferred — design decision D3, no changelog infrastructure)

Summary

Clean, tightly scoped documentation-only PR that accurately updates 4 content pages to reflect the upstream --no-embeddings behavioral change in uf init --force. Spec artifacts are thorough, build passes, and changes are internally consistent.

Alignment

No issues found. All 4 target pages updated per spec. Blog post reviewed and left unchanged with documented rationale.

Security

No issues found.

Constitution Compliance

Content Accuracy (I), Minimal Footprint (II), Visitor Clarity (III) — all PASS.

Verdict

APPROVE — Well-executed documentation sync with complete requirement coverage, passing build, and full constitution alignment.

This review was generated by /uf.review-pr (AI-assisted).

[jflowers]

Upstream Implementation Verification

Upstream PR: unbound-force/unbound-force#321 (merged 2026-07-01)
Verification source: internal/scaffold/scaffold.go at HEAD on main

Claim-by-Claim Verification

Claim	File	Verdict	Evidence
Fresh init runs dewey index --no-embeddings	knowledge.md, common-workflows.md	CONFIRMED	scaffold.go:1592 — opts.ExecCmd("dewey", "index", "--no-embeddings") in fresh-init path
--force re-indexes with --no-embeddings	developer.md, cli.md	CONFIRMED	scaffold.go:1614 — opts.ExecCmd("dewey", "index", "--no-embeddings") in opts.Force path
Guidance to run dewey index separately for embeddings	all 4 pages	CONFIRMED	scaffold.go:1603,1625 — both paths print "Run 'dewey index' separately to generate embeddings for semantic search."
--no-embeddings flag already documented in Global CLI Flags table	knowledge.md cross-ref	CONFIRMED	PR correctly references existing docs rather than duplicating (design decision D2)
Blog post left unchanged (general mention, not misleading)	dewey-knowledge-retrieval.md	CONFIRMED	Design decision D4 applied correctly — point-in-time blog content remains accurate

All 4 content file changes and the blog-post-skip decision are accurate against the implementation at HEAD. Tests in scaffold_test.go (lines 2307, 4090-4098, 4371) also confirm the --no-embeddings expectation.

Command Naming

No slash commands are referenced in this PR. The uf init CLI command name is correct. No naming discrepancies.

Adjacent Open Issues

Issue	Title	Disposition
#211	uf init --force no longer hangs on Dewey reindexing	Directly closed by this PR — consistent
#245	Document uf init --force behavior for Group B sub-tools	No conflict — #245 covers a different scope (specify, replicator, openspec, gaze). This PR's --force description is limited to the Dewey --no-embeddings aspect, which is correct. When #245 lands, the --force docs will expand but nothing in this PR contradicts or is superseded by #245.
#203	Concurrent sub-tool initialization in uf init	No conflict — this PR describes Dewey-specific behavior without claiming sequential execution order. When #203 lands (documenting goroutine concurrency from #251), the text will be additive.

Summary

All claims in this PR are verified accurate against the upstream implementation at HEAD. No naming discrepancies, no contradictions with adjacent open issues. The OpenSpec artifacts (proposal, specs, design, tasks) are well-structured and the design decisions (in-place edits, DRY cross-refs, skip release notes, minimal blog update) are sound and correctly applied.

[jflowers]

PR Review: #232 — docs: update uf init docs to reflect --no-embeddings default

Summary

Tight, documentation-only PR that correctly updates four content pages to reflect the upstream --no-embeddings behavioral change in uf init --force. Spec artifacts are complete, build passes (140 pages), and all content changes are internally consistent.

Local Tool Results

Tool	Status
npm run build	PASS

Findings

[MEDIUM] Stray runtime artifact committed — .uf/replicator/replicator.log is a new empty file with no relationship to the documentation change. The .gitignore covers .uf/replicator/*.db patterns but omits *.log, which allowed this to slip through. Violates Zero-Waste Mandate (AGENTS.md Behavioral Constraint #1).

Fix: Remove from tracking (git rm --cached .uf/replicator/replicator.log) and add .uf/replicator/*.log to .gitignore.

[LOW] Issue #211 release-notes criterion deferred — Design decision D3 explicitly documents this deferral (no changelog infrastructure). Acknowledged, not silently dropped. No action required.

Passing Checks

• All four target pages updated per spec ✓
• Blog post reviewed and correctly left unchanged ✓
• Cross-reference anchor #global-cli-flags verified ✓
• Security: no concerns (docs-only) ✓
• Constitution alignment: Content Accuracy, Neighborhood Rule, Security by Default all PASS ✓

Verdict

REQUEST CHANGES — Remove .uf/replicator/replicator.log from tracking and add the pattern to .gitignore. No changes to documentation content are required. Once the stray file is addressed, this is ready to approve.

This review was generated by /uf.review-pr (AI-assisted).

[yvonnedevlinrh]

Thanks for the review! Addressed below.

[MEDIUM] Stray .uf/replicator/replicator.log — Fixed in 724ac0f. Removed from tracking (git rm --cached) and added .uf/replicator/*.log to .gitignore (also added .uf/feedback/ to prevent local triage-cache artifacts from being committed). Aligns with the existing .uf/dewey/*.log precedent and the Zero-Waste Mandate.

[LOW] Issue #211 release-notes criterion — Agreed, no action needed. Design decision D3 documents this deferral (no changelog infrastructure yet); it's an explicit acknowledgment, not a silent drop.

[jflowers]

lgtm