feat(client): display fork identity for Phase C / P4 (no forks yet)
Merged
TO
2mo ago+103+103+012345678901234567890123456789-4-4-0123456789
Summary
Tooling-only groundwork for the selective fork policy (P4). No forks created ā this is display/parsing plumbing so that when a fork is eventually created (after satisfying ADR 0001's Lane 3 checklist in full: license, bounded scope, build/release capability, ownership, stewardship record, upstreaming-default, exit condition), the client already knows how to show it honestly.
SourceInfogains optionalupstream: Option<String>(original repo URL, set only for numan-maintained fork versions).numan info: addsDistribution: numan-maintained fork -- see 'upstream' under each version belowwhen a package's owner isnuman-maintained, and anupstream:line under any version whosesource.upstreamis set.numan search: appends a[fork]marker to rows owned bynuman-maintained(extracted as a small purefork_marker()helper, mirroringformat_row_status()'s existing style for testability).
Test plan
-
cargo buildā clean -
cargo testā 665+ passed across lib and all integration binaries, 0 failed -
cargo fmt --checkā clean - New tests:
format_infofork-distribution note (present/absent),format_infoupstream line (present/absent),fork_marker()(numan-maintained / normal owner)
Ref: docs/plans/2026-08-09-intake-process-reform.md (P4), docs/adr/0001-ecosystem-trust-upstream-contribution-fork-stewardship.md, numan-registry/numan-plugins companion PRs.
š¤ Generated with Claude Code