OKF v0.2.6 — onboarding, section search and Markdown setup

Changes

• Rewrite English and Russian README, landing pages and quickstarts around concrete tasks. Preserve detailed contracts in the reference pages and provide a complete clone-to-demo, own-note and MCP-client path.
• Add okf search and MCP search_sections, using the same deterministic lexical section retrieval layer. Results include original snippets, physical line ranges, locators and source/snapshot digests. Existing literal search_concepts remains compatible.
• Add okf setup for ordinary Markdown: preview first, explicit type policy, digest-confirmed apply, source preservation and atomic publication to a new target. Provenance and verification are not inferred.
• Fix legacy citations display, concept IDs that resemble footnotes, Unicode routes and repeated footnote backlinks. Store regression templates with Windows-safe filenames.

The document contract remains okf_version: "0.2"; this release tag versions the Go toolkit separately.

Verification

Two independent reviewers reached 100% of the fixed 20 acceptance criteria and no open confirmed findings. Local full Go tests, vet, whitespace, skill-package checks, Jekyll build, a clean quickstart, a real Codex MCP client and Chrome desktop/narrow flows passed. GitHub CI verifies supported platforms, race detection, module integrity, skill packages and the generated viewer.

On a frozen synthetic dataset, document Hit@5 and MRR@5 improved from 0.10 to 0.95 (20 answerable queries; 4 no-answer queries returned no hits in either arm). Equal five-hit wire budgets and source attribution were checked. This does not establish LLM answer-quality gains or general performance improvements.

Traceability

• Issue #9, PR #10.
• Acceptance and independent reports: .cursor/tasks/evidence/016/ in the release tree; detailed client session logs remain local.
• Repository rulesets are empty; required status checks are not configured on main; green checks are verified explicitly by the release operator.

Install with go install github.com/skosovsky/okf/cmd/okf@v0.2.6 or go install github.com/skosovsky/okf/cmd/okf-mcp@v0.2.6.

• Main commit: 61e75e9; existing annotated tag: v0.2.6.
• Successful PR CI and PR Action integration.
• Successful full tag CI on the exact release/main commit, main Action integration, and Pages deployment. Main CI attempt 1 passed all jobs except the false cancellation assertion described below; its failed race job was rerun. Publication relies on the full green PR/tag gates rather than treating that failure as success.

Hosted verification: nine primary EN/RU pages returned HTTP 200, including quickstarts, MCP guides, reference pages and demo. Demo SHA256 matches the release tree. Chrome verified architecture direct loading, related mutation navigation, the repeated fnref1:3 backlink retaining the selected concept, Back and reload. Site and Russian quickstart.

Tagged-install smoke: both CLI binaries installed from the Go module proxy with @v0.2.6; go version -m identifies the expected module version. Installed okf search returned the expected architecture section with original line/digest evidence. The installed MCP server initialized, advertised 14 tools and completed a search_sections call returning that section.

Known test follow-up: #11. Main CI attempt 1 falsely failed the pre-existing high-cardinality attribution cancellation test because map/sort-dependent context-check counts changed between probes; no DATA RACE warning. Independent reproduction showed the fake context never reached its cancellation threshold. Production cancellation failure was not confirmed. The identical release commit passed PR and tag CI. The failed main job is being rerun; its original failure remains part of the release record.