We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Link Issue #77 spike results from Home
Migrate docs/77-spike-does-rb-nogvl-offload-safe-obviate-thread-wrapper research to the wiki
Migrate issue #57 research to the wiki; make Home a cross-issue index Moves the 13 research docs from docs/57-stop-duckling-parse-from-blocking-async-reactor-fi/research/ into flat wiki pages (research-async-reactor-blocking + 12 topic/subtopic pages), following the existing research-<topic>[-<subtopic>] naming convention. The concrete implementation plan (previously two plan docs) moves to issue #64 instead, not the wiki, per how issue #1's stale plans were handled (executed plans get archived here; live plans become issues). Home.md's prior content (issue #1's reading-order/settled-decisions page) moves to home-issue-1.md; the new Home.md is a short cross-issue index covering both issue #1 (shipped) and issue #57 (in progress).
Link open Falcon-blocking PRs/issues (#38, #50, #57) in the risk-2 Falcon subsection
Use each target page's H1 as internal link text; drop wafer-inc-duckling references Link text throughout the wiki still showed the pre-flatten basenames (public-functions.md, ci-configuration.md, the bare page slug, etc.) even though the pages themselves render fine now. Replaced every internal link's visible text with the target page's actual H1 title. Also cleaned up "wafer-inc-duckling" mentions: headings now say "Duckling (Rust)" (matches how the crate is referred to elsewhere), and a table label lost its redundant "wafer-inc-" prefix to match its sibling rows. Left the literal test-method identifier and code-block comments/TOML that reference the crate by its old research-doc naming untouched, since those aren't prose references.
Flatten page files so wiki links resolve within the wiki, not raw content GitHub wiki routes pages by basename only, ignoring directory structure in the git tree — the earlier import (from PR #3) kept the nested research/ and plans/stale/ layout, so every relative link like ./research/build-wiring/README.md rendered as a literal filename with a .md extension. GitHub doesn't recognize that as a page slug, so it 302-redirected to raw.githubusercontent.com/wiki/... instead of rendering the page. Six README.md files at different paths also collided on the single flat "README" slug. Renamed every file to a flat, directory-prefixed slug (e.g. research/build-wiring/ci-configuration.md -> research-build-wiring-ci-configuration.md) and rewrote every internal link to the bare new slug (no ./, no .md). Verified every link target now matches an existing page filename.
Import research and stale plans from PR #3 Migrated everything except the live roadmap from docs/1-ship-duckling-gem-time-extraction-via-magnus-wafer/ in the main repo: the full research/ tree (wafer-inc-duckling API surface, build wiring, type-mapping strategy, test coverage, FFI risk analysis) and plans/stale/ (the fully-executed 0.2.0 implementation plans). The live plan stays in the repo as docs/2026-07-01-roadmap.md, linked from Home. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_012NxJNvep34DfmFT3aqNTVN
Initial Home page