# pear-git-v3 is published ONLY via the canonical local `pgh publish .`.
#
# WHY (incident 2026-07-18, pear-git org #3): pgv3 depends on WORKSPACE packages
# via `file:../` symlinks (hyper-svc, git-remote-punch, hyper-identity, hyper-rooms,
# ...). The forge CI runs `npm install` in an isolated `git archive` export where
# those sibling symlinks do NOT resolve, so npm silently drops them and any
# `pgh publish` run HERE ships an INCOMPLETE closure (missing hyper-svc →
# `MODULE_NOT_FOUND` at boot) that CLOBBERS the correct local publish as the
# authoritative release. That is exactly what happened: CI tree 36d33016 (no
# hyper-svc) overwrote the good local tree 8315d33e and crash-looped ashatron.
#
# So this ci.yaml intentionally does NOT publish. The post-receive hook stays
# (it drives ref-update-observed → mirror replication); only the publish is moved
# to the local working tree, where the file:../ symlinks resolve. Publish pgv3 with:
# pgh publish . (from hyper-fleeky/pear-git-v3, version bumped)
# See memory feedback_pgv3-deploy-publish-then-install.
steps:
- name: no-op (pgv3 publishes locally — never from CI; see comment above)
run: "true"
timeout: 30