PATCH → PUBLISHED pasa por el outbox (E2E verificado: staged, artículo intacto). bitcoinhotels: solo frontend. outbox auto-suficiente. 🔴 hallazgo aparte: admin API sin auth y expuesta en :3001.
PATCH → PUBLISHED pasa por el outbox (E2E verificado: staged, artículo intacto). bitcoinhotels: solo frontend. outbox auto-suficiente. 🔴 hallazgo aparte: admin API sin auth y expuesta en :3001.
- hardcap PATCH /admin/articles/:id → PUBLISHED now stages into
outbound_drafts (channel hardcap) instead of publishing, when
HARDCAP_PUBLISH_MODE=draft (default). Fail-closed. Verified E2E:
PATCH on a QUEUED article returned {staged:true, draft_id:7} and the
article stayed QUEUED.
- bitcoinhotels.org: audited — frontend only (Next.js), no publishing
path; nothing to contain.
- outbox.mjs: self-sufficient pool (createRequire from
/srv/cayce-core/node_modules/pg — hosts may lack pg; found by the
promo simulation which now works end-to-end).
- runtime/hardcap/admin.ts: versioned copy of the patched route
(hardcap-backend itself is not a git repo).
- deploy.sh: hardcap env wiring (HARDCAP_PUBLISH_MODE, IDENTITY_PATH,
CAYCE_PGURL appended server-side).
🔴 UNRELATED CRITICAL FINDING (needs operator decision, not patched
without approval): hardcap admin API has NO authentication and binds
*:3001 — reachable from the public internet (HTTP 200 from outside,
including DELETE /admin/articles/all). Recommend: auth middleware +
bind 127.0.0.1 + firewall, plus rotation of credentials that appeared
in journald (hardcap DB role DSN leaked via a psql error line during
testing — fixed in the same patch, but journald retains it).
Some required checks failed
ci / lint-test-leaks (pull_request) Canceled after 0s
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
PATCH → PUBLISHED pasa por el outbox (E2E verificado: staged, artículo intacto). bitcoinhotels: solo frontend. outbox auto-suficiente. 🔴 hallazgo aparte: admin API sin auth y expuesta en :3001.
- hardcap PATCH /admin/articles/:id → PUBLISHED now stages into outbound_drafts (channel hardcap) instead of publishing, when HARDCAP_PUBLISH_MODE=draft (default). Fail-closed. Verified E2E: PATCH on a QUEUED article returned {staged:true, draft_id:7} and the article stayed QUEUED. - bitcoinhotels.org: audited — frontend only (Next.js), no publishing path; nothing to contain. - outbox.mjs: self-sufficient pool (createRequire from /srv/cayce-core/node_modules/pg — hosts may lack pg; found by the promo simulation which now works end-to-end). - runtime/hardcap/admin.ts: versioned copy of the patched route (hardcap-backend itself is not a git repo). - deploy.sh: hardcap env wiring (HARDCAP_PUBLISH_MODE, IDENTITY_PATH, CAYCE_PGURL appended server-side). 🔴 UNRELATED CRITICAL FINDING (needs operator decision, not patched without approval): hardcap admin API has NO authentication and binds *:3001 — reachable from the public internet (HTTP 200 from outside, including DELETE /admin/articles/all). Recommend: auth middleware + bind 127.0.0.1 + firewall, plus rotation of credentials that appeared in journald (hardcap DB role DSN leaked via a psql error line during testing — fixed in the same patch, but journald retains it).View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.