282085b · hyperident · pear-git-v3

hyperident commits / 282085b

README: fix stale production install to pgh content-addressed URL

Line 53 still advertised the retired pear-runtime install key
(pear://bdkaq…) and Hyperdrive OTA path, both removed in 0.2.2
(16a5ee3). Point install at pgh://<reg>/hyperident (matches
package.json pgh.upgrade) and describe the real OTA mechanism
(backgrounded `pgh app update`, gated by --no-updates).

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

282085b8f8c09a9c0be4f4cc9702cc1b98a62f3d

by plankatron <fleeky@gmail.com> · 2026-07-01T15:21:44.000Z

Changed files (1) +8 -3

README.md +8 -3

…	…	@@ -50,12 +50,17 @@ bare index.js list-profiles
50	50	### Pear app install (production)
51	51
52	52	```bash
53		pgh app install pear://bdkaqufc8o6h75cbxrkzxjqadzqkyq11bws3iuxsb8kk5jjpuado --name hyperident
	53	pgh app install pgh://1dd36bdfa9cb7f7d84adbd07f017e7200f7f90a3a546cd0761fac2a1f8a13e86/hyperident --name hyperident
54	54	hyperident init
55	55	```
56	56
57		The `pear run pear://...` flow that older docs mention is being
58		removed from the Pear runtime. Use `pgh app install` instead.
	57	This fetches the content-addressed release tree from the publisher's
	58	pgh registry (the same key as `pgh.upgrade` in `package.json`). OTA
	59	updates are automatic: each CLI invocation kicks off a best-effort
	60	backgrounded `pgh app update hyperident` (pass `--no-updates` to
	61	suppress). The old `pear run pear://...` flow and the pear-runtime
	62	(Hyperdrive) OTA path were retired in 0.2.2 — don't use a `pear://`
	63	key here.
59	64
60	65	## Commands
61	66