We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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.