docs: purge stale lamassu naming; fix the hal-check skill's provenance boundary

- @lamassu/clink import examples → @bitSpire/clink, the package's real name.
- machine-installation.md: the service user is `bitspire`, not `lamassu`
  (renamed in configuration.nix long ago; the doc never followed).
- README: clone aiolabs/bitspire, not lamassu-next; the fleet sentence
  claiming batm3/douro run `main` against Lightning.Pub was stale.
- nostr-check skill: table headers say bitSpire.
- hal-check skill: the boundary is c0b69d1, not v8.1.5 (CLAUDE.md corrected
  this 2026-07-04; the skill kept asserting the wrong tag), and the
  "forbidden operations" now reflect the recorded permission —
  reference over port, name the source commit — plus a rule born of the
  GTQ window: no value table without a test over it.

Deliberately kept: every `aiolabs/lamassu-next#NN` issue citation, the
provenance sections, "Ported from lamassu-machine" driver headers, and
the hardware names "Lamassu Sintra/Tejo/Douro" — those are the machines.

.claude/skills/nostr-check.md

@@ -17,7 +17,7 @@ Where `target` can be:
 ## Relevant NIPs for bitSpire
 
 ### Core NIPs (Must Implement)
-| NIP | Description | Usage in Lamassu |
+| NIP | Description | Usage in bitSpire |
 |-----|-------------|------------------|
 | NIP-01 | Basic protocol | Event structure, relay communication |
 | NIP-19 | bech32 entities | npub, nsec, nprofile encoding |
@@ -26,7 +26,7 @@ Where `target` can be:
 | NIP-59 | Gift wrapping | Anonymous message delivery |
 
 ### Application NIPs
-| NIP | Description | Usage in Lamassu |
+| NIP | Description | Usage in bitSpire |
 |-----|-------------|------------------|
 | NIP-17 | Private DMs | Receipt delivery |
 | NIP-47 | Nostr Wallet Connect | Potential wallet integration |