Skip to content

docs(site): repair acquisition, 404 links, lane-leak, and audience-separation findings - #90

Merged
ShixiangWang merged 1 commit into
mainfrom
docs/site-remediation
Nov 8, 2026
Merged

ShixiangWang merged 1 commit into
mainfrom
docs/site-remediation

Conversation

@ShixiangWang

Copy link
Copy Markdown
Contributor

Summary

Repairs the CRITICAL and HIGH findings from the dual-lens (junior-user + senior-expert) review of the docs system and pkgdown site.

CRITICAL-1 — acquisition path dead end-to-end

  • README: removed the r-universe badge and install block (r-universe serves no msuiter binary — verified against the live PACKAGES index); install now points at remotes::install_github("WangLabCSU/msuiter") plus the real v0.1.0 release assets.
  • get-started article: added the install face (pak/remotes/GitHub + release tarball paths) — the page previously had zero install tokens.

CRITICAL-2 — three 404 cross-links + LICENSE 404

  • tour, extending, scenarios articles: sibling hrefs switched to the bare form (tour.html), which is the form that resolves from pages rendered under /articles/.
  • README LICENSE link switched to an absolute URL (relative link 404s from repo root renderers).

HIGH-1 — lane-identifier / environment-leak hygiene

  • Banned agent-<hex8+> lane identifiers and prose /tmp/ pointers across the article corpus; ~20 devlog/qmd files scrubbed. [GATED:] tokens and the bare word "lane" are expressly out of scope (amended-law scope note).
  • Enforced by a new unit in test-docs-extending-surface.R.

HIGH-2 — audience separation (the 63-file devlog at user-facing weight)

  • tools/extending-face.R: roster hrefs no longer carry the articles/ prefix (91 entries become auditable by the link law; prefix now = violation).
  • _pkgdown.yml: 6 tier navbar keys rewritten for the user-facing face + 25 article descriptions; devlog demoted behind the specialist tiers; both-faces comment added.
  • New audience law in test-pkgdown-coherence.R (.coh_navbar_audience_law, bijective), kept out of the synthetic-yml law path by design.

Local gate

  • All 7 consumer test files: 0 fail / 0 error (per-file test_dir runs).
  • Full devtools::check: 0 errors ✔ | 2 warnings ✖ | 0 notes ✔ (Duration 21m 16.4s; testthat 17m OK; vignette re-build 190s OK). The 2 WARNINGs are the known baseline class (checkbashisms advisory, Rust crate download advisory) — below the PR fix(ci): repair the three scheduled-gate defects behind audit #74 and #76 #89 attested WARN-7 baseline.
  • Post-fix leak grep: agent-[0-9a-f]{8,} across vignettes/, README.md, _pkgdown.yml → 0 hits.

Test plan

  • 7 consumer test files green locally
  • devtools::check green (baseline-class warnings only)
  • CI confirmation on this PR (fanout + site legs)
  • pkgdown redeploy after merge; live-site spot-check (get-started install tokens, navbar tiers, link census)

…tion

- README: drop dead r-universe badge and install block; keep
  remotes::install_github plus the v0.1.0 release-attached packages path;
  point the license link at the GitHub file so the homepage resolves
- get-started: teach a reachable install method on the published page
  (install_github face + prebuilt-release paragraph) and gate it with an
  acquisition law (positive control fires on a checkout-only face)
- tour/extending/scenarios: write bare sibling hrefs so they resolve under
  /articles/ (the articles/-prefixed forms 404 at render time)
- extending-face.R: articles/-prefixed sibling hrefs are a violation; strip
  the roster prefix so all 91 article entries join the auditable set
- test-docs-extending-surface: flip the link-law assertion to the fixed
  hrefs and add the too-deep and roster-auditability units
- pkgdown-coherence: article-tier navbar audience law (bijective, keyed vs
  internal allowlist), exercised by its own blocks plus firing controls;
  fix the descending-range idiom in both navbar parsers
- _pkgdown.yml: navbar keys on the six user-facing tiers, descs for the
  four sections missing them, both build faces documented at the config
- devlogs/ADRs: scrub /tmp/ scratch pointers and worktree agent-<hex>
  identifiers from published articles; documented build commands keep
  their paths
@ShixiangWang
ShixiangWang merged commit 99ec130 into main Nov 8, 2026
9 checks passed
@ShixiangWang

Copy link
Copy Markdown
Contributor Author

Post-merge attestation (docs-remediation closure):

  • Push runs on main@99ec130 both green: CI 42498312255 (success) and pkgdown 42498312254 (success).
  • Check-run-level rollup on 99ec130: 10/10 SUCCESS (build-deploy, guard-prep, guards-shards, guards, msrv ubuntu+windows, R-CMD-check-fanout macos/ubuntu/windows, rust).
  • PR-arm run 42427545349-equivalent on this PR's head was also fully green before merge.

Test-plan items resolved:

  • CI confirmation on this PR (fanout + site legs)
  • pkgdown redeploy after merge; live-site spot-check (get-started install tokens, navbar tiers, link census)

Closing out: the CRITICAL/HIGH docs findings are repaired and attested on main. Remaining follow-ups live in the docs backlog: the four thin vignettes (scenarios-gallery, peer-evidence, quality-control, signature-extraction) as a task-guide pass, CITATION.cff, and devlog index/title normalization.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant