Disconnect from markbennett.ca/tangled-cli; fix repo DID matching by rkey
Cameron maintains this as a separate, independent fork and does not want
it tied to the upstream project in any way.
- package.json: name -> 'tangled-cli' (unscoped, no npm-registry claim),
marked private (drops publishConfig entirely), repository.url points
at cameron.stream/tangled-cli, author updated. LICENSE keeps Mark
Bennett's original MIT copyright (required) and adds a second line for
Cameron's changes in this fork.
- Removed the 'source' field from Cameron's own sh.tangled.repo record
for this repo (rkey 'tangled-cli') via putRecord — this is the field
Tangled uses to track a fork's upstream parent; it pointed at
markbennett.ca's original repo. Formal disconnect on the Tangled side,
not just cosmetic.
- resolveRepoDid: fixed a real bug this surfaced — matching a repo by
name only fails for records (like this one, and misaligned) that never
set a 'name' field and are identified by their rkey instead. Now falls
back to matching by rkey. Without this, 'tang pr create' inside this
repo's own directory failed outright ('Repository tangled-cli not
found').
- Doc-comment example handles ('markbennett.ca') swapped for a neutral
placeholder in src/ and tests/; only test fixture data changed, no
behavior.
Also cleaned up on this machine (not part of this commit): the global
tang binary no longer resolves through any @markbennett-scoped install —
removed the bun-linked symlink, uninstalled a separate npm-global copy
that had been shadowing it under an nvm Node version, and cleared bun's
download cache for the package. A single symlink at ~/.bun/bin/tang now
points directly at this repo's build.
Checks: bun run typecheck, bun run test (330 passing), bun run lint:fix,
bun run build all clean.
cameron.stream