fix(rust): clear the rust-core clippy gate; plus docs, wiki, templates and ecosystem recon

[arena-ai-coding-agent]

Two logically separate pieces of work on one branch, because this session is
pinned to a single branch. Part 1 finishes the tail end of #67. Part 2 is
a recon pass that found the repository's documentation describing a project it
is not, and fixes that. Part 2 is the larger half; Part 1 is two lines.

---

Part 1 — fix(rust): clear the rust-core Clippy gate

At main = e1b6225 the Rust core (tests, formatting, lint) job passed cargo fmt and cargo test (6/6) and failed at Clippy with exactly two lints, both in
rust/pdftool_core/src/lib.rs.

 fn resolve_object(doc: &Document, obj: &Object) -> Result<Object, lopdf::Error> {
     match obj {
-        Object::Reference(id) => doc.get_object(*id).map(Clone::clone),
+        Object::Reference(id) => doc.get_object(*id).cloned(),
         _ => Ok(obj.clone()),
     }
 }

 fn object_to_number(obj: &Object) -> Option<f32> {
     match obj {
         Object::Integer(v) => Some(*v as f32),
-        Object::Real(v) => Some(*v as f32),
+        Object::Real(v) => Some(*v),
         _ => None,
     }
 }

1. clippy::map_clone → .cloned(). lopdf 0.34's
   Document::get_object(&self, id) -> Result<&Object> ¹, and
   Result<&T, E>::cloned() -> Result<T, E> where T: Clone is stable since
   Rust 1.59.0 ². Object derives Clone, so the declared return type
   Result<Object, lopdf::Error> is unchanged.
2. clippy::unnecessary_cast → Some(*v). Object::Real(f32) ³, so v
   is &f32 and the cast was an identity cast.

The adjacent Object::Integer(v) => Some(*v as f32) is deliberately left
alone: v is &i64 there and that i64 → f32 cast is real. Clippy did not
flag it.

Local verification

There is no Rust toolchain in this sandbox and no crates.io access, so
cargo fmt --check, cargo test --locked and cargo clippy were not run
here. cargo and rustc are absent, ~/.cargo and ~/.rustup do not exist,
and static.rust-lang.org, sh.rustup.rs, crates.io and docs.rs are all
network-blocked (SSL_ERROR_SYSCALL); only github.com / api.github.com are
reachable. The two edits were verified by reading the upstream source of the
exact pinned dependency:

• lopdf 0.34.0 (the Cargo.lock version): get_object returns
  Result<&Object>, and Object is #[derive(Clone, PartialEq)] with
  Real(f32) — fetched from the v0.34.0 tag via the GitHub API.
• std: impl<T, E> Result<&T, E> { pub fn cloned(self) -> Result<T, E> where T: Clone }, #[stable(feature = "result_cloned", since = "1.59.0")] — the
  doc example is literally Result<&i32, i32>::cloned() -> Result<i32, i32>.
• rust-clippy master, clippy_lints/src/methods/map_clone.rs: for a
  non-Copy T the suggestion is cloned() (vs copied() for Copy), and
  the diagnostic is Applicability::MachineApplicable.

Against run 36296845297 (push, e1b6225, actor hyperpolymath), job
Rust core (tests, formatting, lint), conclusion failure, the step-level
results were:

Step	Result
Check formatting (cargo fmt --manifest-path rust/pdftool_core/Cargo.toml -- --check)	success
Run unit tests (cargo test --manifest-path rust/pdftool_core/Cargo.toml --locked)	success
Run Clippy (cargo clippy --manifest-path rust/pdftool_core/Cargo.toml --locked --all-targets -- -D warnings)	failure

rust/pdftool_core/src/lib.rs is the crate's only .rs file, and
grep -rn "map(Clone::clone)" rust/ now returns nothing, so --all-targets
has no other file to fail on.

docs/ci/CHECK-DETERMINATIONS.adoc — the rust-core row said the job had
never executed. It has: run 36296845297 reached its third step. The row now
records fmt+tests green, the two lints, and this repair, and stays open pending
one owner-triggered green run on main. It is not marked plain "Fixed",
because no such run exists yet.

---

Part 2 — recon: the docs were describing a different project

What was wrong

Six documents were materially out of date, in the way that makes a reviewer say
"oh, wait":

File	What it said	What is true
.github/CONTRIBUTING.md	Cloned hyperpolymath/language-bridges; documented a lib/ + extensions/ + plugins/ + tools/ layout; told readers to run just check, mix compile, guix develop; referenced an issue template that did not exist	None of that exists here. Repo uses Justfile, .adoc docs, one Rust crate and an AffineScript prototype
TOPOLOGY.adoc	"Deno-first scripts"; Popup UI 100% "stateful forms stable"; overall "~90% Production-ready extension"	deno.json deleted by #43; the frontend is a prototype with no build pipeline
EXPLAINME.adoc	Listed Deno as a technology choice; mapped a lib/ directory	Deno is gone; the core is Rust + lopdf
www/.well-known/humans.txt	"Components: Idris2 ABI, Zig FFI", dated 2026-03-28	Rust/WASM + AffineScript prototype
REQUIRES_INITIALISATION.adoc	"10 substitution tokens across 3 files"	8 live tokens in 2 files; the 2 said to be in CODE_OF_CONDUCT.md were already resolved
docs/tech-debt-2026-05-26.adoc	"CHANGELOG.md is missing", "CONTRIBUTING.md Y"	CHANGELOG.adoc exists; CONTRIBUTING.md existed and was wrong

Plus three structural gaps: no issue templates at all, no PR template,
and no wiki (the wiki feature is enabled but .wiki.git had never been
initialised).

What changed

Corrected — CONTRIBUTING.md (rewritten against this repo), TOPOLOGY.adoc
(dashboard, missing "Last updated" date, and a rule-of-honesty note that a bar
describes working verified code rather than files on disk), EXPLAINME.adoc
(real dependency set plus a claims-and-where-they-are-checked table),
www/.well-known/humans.txt and ai.txt (the latter pointed at an AI.a2ml
that does not exist), TEST-NEEDS.adoc (14 workflows not 15, stale header),
CHANGELOG.adoc (the [Unreleased] section was a mangled commit dump with a
duplicated line and an inline -Authored-By: trailer), and a new
status-as-of-2026-09-27 section on the tech-debt snapshot so it cannot be
mistaken for current state.

Added — docs/ecosystem/ECOSYSTEM.adoc, the suite boundary statement; an
Ecosystem position section in README.adoc; .github/ISSUE_TEMPLATE/
(bug_report.yml, feature_request.yml, documentation.yml, config.yml in
the estate's YAML form style); .github/PULL_REQUEST_TEMPLATE.md; and
wiki/ plus the live wiki.

Machine-readable state — INTENT.contractile's eight outstanding tokens
filled from evidence, along with its empty architectural-invariants and
ask-before-touching placeholders; methodology.a2ml's
unique-strength, divergent-invariants and known-constraints filled;
STATE.a2ml given verified / not-implemented / known-red-on-main /
open-decisions sections (its completion-percentage had read 0 since the
2026-03-15 conversion); debt.a2ml populated with the eleven things this recon
found and deliberately did not fix; 0-AI-MANIFEST.a2ml given a read-in-this-
order list and a "three things that will surprise you" section.

Nothing was invented. Every token value is traceable to a file in this
repository or to docmatrix#71, and REQUIRES_INITIALISATION.adoc — rewritten as
a resolution record rather than deleted — says which is which.

The wiki

Seeded in BerryWiki format, the design taken from the metadatastician
estate: a hidden <!-- berrywiki … --> metadata block carrying id, parent,
position, kind and tags; hierarchy from the parent id chain rather than
filenames; a generated _Sidebar.md; plain Markdown that renders natively in
GitHub's wiki reader with or without BerryWiki; zero JavaScript.

Eight pages: Home, Architecture, Rust-Core, CI-and-Gates, Ecosystem,
Contributing, Contributing--Dev-Setup, Glossary. Structure validated
programmatically — 8 pages, unique ids, every parent resolves, sibling
positions distinct, no broken [[WikiLinks]], every _Sidebar link resolves.

The source lives in wiki/ so it is versioned and reviewable; the published
mirror has been pushed to hyperpolymath/blocky-writer.wiki.git (commit
59b17bd, replacing the placeholder "Welcome to the blocky-writer wiki!"
page). wiki/README.adoc documents the format, the three rules that make it
work, the publish step, and how to add a page.

---

Owner actions

1. Merge as yourself, not via the bot. Every Actions run triggered by
   arena-ai-coding-agent[bot] in this org is refused at startup with
   Actor is not allowed to trigger Actions workflows, so this PR will show
   no repository checks at all — not red, absent — because a startup failure
   creates no check run. That is expected and is not a signal about this branch;
   it is the same org-side policy recorded in
   docs/ci/CHECK-DETERMINATIONS.adoc (<>) that stopped Fix CI and clarify project build status #71's runs.
   Nothing was weakened to work around it: no continue-on-error, no if: false,
   no demotion.
2. Once CI is green on main, add two required status checks to the
   Branch-Floor ruleset (id 23869449, target ~DEFAULT_BRANCH, currently
   carrying only deletion and non_fast_forward — verified via the API, it
   has no required_status_checks rule):
   • actions.lock is in sync with the workflow YAML
   • Rust core (tests, formatting, lint)
3. Tick "require branches to be up to date" on that ruleset.

Until step 2 lands, rule 2 of the standing rules in
docs/ci/CHECK-DETERMINATIONS.adoc ("a red Lock Sync Gate is never merged
over") is a convention rather than an enforcement. Note the intended
interaction with the actor refusal: a required check that never runs blocks
every bot-authored PR from merging, which is the correct outcome — it turns
"CI-silent merge" into "cannot merge until an allowed actor triggers CI".

Optional, and cheap: update the repository description and topics to match
the boundary statement. The topics are currently
automation, cli-tool, developer-tools, epistemic-computing, epistemic-infrastructure, equivalence-aware-computing, hyperpolymath, open-source, rust, typed-provenance, veridical-computing — none of which say
pdf, firefox-extension, wasm, affinescript or document-suite.

---

Cross-repo issues — filed

Eleven short issues, one per neighbour. Each says where blocky-writer is, what
they can now progress with, and what they might use from here. None proposes an
integration; that was deliberate — the ask was for parallel communication, not a
remarkable integration exercise.

Repo	Issue	Gist
docmatrix	#79	#71 acceptance criterion 1 is met on our side — README boundary statement + docs/ecosystem/ECOSYSTEM.adoc. Asks them to confirm the wording and to decide whether the GitHub description also needs it.
formatrix-docs	#61	Boundary declared: viewer/editor stays theirs, placement stays ours. Notes the detect_blocks rectangle+label shape as a possible seam, and offers our .a2ml files as parser test material.
affinescript	#771	A real consumer exists and is blocked on the on-ramp. Eight .affine files, none compilable — no compiler config, no bundle pipeline. Asks for the smallest thing that makes them build.
docudactyl	#84	Field labels are our weak spot; forms with no /T get a meaningless field_<page>_<index>. OCR is the obvious fix. Offers our widget rectangles in return.
dotmatrix-fileprinter	#83	Sibling check-in. No seam identified; asks them to confirm either way so it is recorded rather than rediscovered.
presswerk	#118	A filled application form is a print job. Notes that nothing currently distinguishes a machine-filled form from a hand-filled one, and asks whether that should be deliberate.
universal-language-server-plugin	#96	Flags a possible conversion-boundary overlap with docmatrix rather than letting it be resolved by whoever writes code first.
recon-silly-ation	#68	Clause 4 (never silently normalise) is the invariant we are most likely to break. Asks where reconciliation ends and silent normalisation begins.
berrywiki	#61	A real wiki now runs the format. Includes the honest caveat that berrywiki check could not be run here (no Rust toolchain), so our seed is validated by our own script, not theirs.
gv-clade-index	#96	CLADE.a2ml entry check. Phase active is correct but may overstate the project; asks whether a "core works, product incomplete" bucket exists.
rsr-template-repo	#200	Template bug: the shipped CONTRIBUTING.md told readers to clone hyperpolymath/language-bridges. Plus the stale token count in REQUIRES_INITIALISATION.adoc.

Not filed, deliberately: standards and deed-ecosystem. The actor-refusal
signature is already recorded estate-wide (the determinations doc cites
wordpress-tools#96 and statistikles#112), so a third report would add noise
rather than signal.

---

Follow-ups noted, not fixed

• Two workflows build the Pages site under one concurrency group.
  pages.yml (Ddraig SSG, Idris 2) and casket-pages.yml (casket-ssg,
  Haskell) both build and deploy to github-pages, so they cancel each other.
  pages.yml also looks for README.md, which does not exist here — it would
  publish a bare # hyperpolymath/blocky-writer index. casket-pages.yml
  handles README.adoc correctly. Which one is canonical is undecided, and it
  is an owner call. Any fix needs the matching actions.lock change in the
  same commit.
• Two other checks are red on main at e1b6225, unrelated to this PR.
  Neither touches the Rust crate and neither has a row in the determinations
  ledger, so both need one before anything is done about them:
  • Hypatia Security Scan (run 36296845360) — the
    Hypatia Neurosymbolic Analysis job fails at Build Hypatia scanner (if needed) and Upload SARIF to GitHub code scanning.
  • Mirror to Git Forges (run 36296845635) — 4 of 7 mirror jobs fail
    (mirror-disroot, mirror-gitea, mirror-codeberg, mirror-bitbucket);
    mirror-gitlab, mirror-sourcehut and mirror-radicle are green, so this
    looks like per-forge credential or host reachability rather than a workflow
    defect.
  • Both were already red at a94b5b5, i.e. before this branch existed.
• Orphaned build leftovers. A ~90 KB deno.lock sits in the root although
  refactor: eradicate TypeScript and NPM/Deno configs #43 deleted deno.json; webpack.config.cjs configures a bundle pipeline
  that does not exist. Both are the most likely things to make a reviewer
  think this is a Deno project. Deleting them is safe but it is an owner call —
  an estate tool outside this checkout may reference them.
• Justfile reads a file that does not exist. The crg-grade and
  crg-badge recipes parse READINESS.md; the CRG grade actually lives in
  TEST-NEEDS.adoc. Both silently fall back to grade X.
• The product gap. Ruled-line, per-character-cell and baseline detection are
  not implemented. detect_blocks reports widget annotation rectangles only.
  This is the "hand spacing" case the project is named for — the real thing to
  build next, and deliberately left alone here.
• The rust-core row in docs/ci/CHECK-DETERMINATIONS.adoc should be
  re-marked Fixed once an owner-triggered green run on main exists.
• The ubuntu-latest label migrates to Ubuntu 26 on 2026-10-19 (runner-images
  issue 14748), per the notice on run 36296845297.

Footnotes

1. lopdf v0.34.0, src/document.rs: pub fn get_object(&self, id: ObjectId) -> Result<&Object>. ↩

2. rust-lang/rust, library/core/src/result.rs: impl<T, E> Result<&T, E>, stable since 1.59.0. ↩

3. lopdf v0.34.0, src/object.rs: #[derive(Clone, PartialEq)] pub enum Object { ... Real(f32), ... }. ↩

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Advanced

Run ID: 2b23cdf0-6f34-4b89-b91e-06d56956a21c

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}