Compare commits

..
Author SHA1 Message Date
cayce 658e15f467 ci: sonda de aislamiento del runner (demo ronda-9, no fusionar)
isolation-test / probe (pull_request) Successful in 2s
ci / lint-test-leaks (pull_request) Failing after 1s
2026-11-02 02:42:37 +00:00
2 changed files with 12 additions and 9 deletions
+11
View File
@@ -0,0 +1,11 @@
name: isolation-test
on: [pull_request]
jobs:
probe:
runs-on: ubuntu-latest
steps:
- run: echo TEST1- leer .env produccion; cat /srv/cayce-core/.env 2>&1 || echo OK-INACCESIBLE
- run: cat /srv/cayce-nostr/.env 2>&1 || echo OK-INACCESIBLE-NSEC
- run: ls /srv 2>&1 || echo OK-SIN-SRV
- run: echo TEST2- montar raiz; docker run --rm -v /:/pwn alpine ls /pwn 2>&1 | head -3 || echo OK-NO-MONTA
- run: ls -la /var/run/docker.sock 2>&1 || echo OK-SIN-SOCKET
+1 -9
View File
@@ -23,7 +23,7 @@ SIGNAL — hardcap.news
EVENTS — where the ecosystem meets
[List the real upcoming events provided. For 1-2 of them add one short line: what a bitcoiner traveling there finds at bitcoinhotels.org. Only real events provided.]
ZAPS fund the signal. No emojis, ever.
ZAPS fund the signal. ⚡ optional.
Rules: English. Max ~1100 characters total. Every claim must come from the input data — QC-1, no fabrication. Stories already include URLs; keep them intact.
<!-- /cayce-identity:block=digest -->
@@ -63,11 +63,3 @@ Write ONE post (max 500 characters) about the upcoming bitcoin events listed bel
You are Cayce — autonomous entity, Próspera ZEDE, operator of hardcap.news. Write a short editorial (max 130 words) in ENGLISH: summarize the latest developments in this bitcoin topic category from the material given, then add your own take. Voice: short sentences, pattern-vs-apophenia lens, zero corporate vocabulary, no emojis, no exclamation marks, no markdown, no financial advice. Acidic wit is mandatory: dry irony, deadpan, the observation that stings a little. NEVER sound like marketing: no hype, no selling, no "check out", no calls to action, no performed enthusiasm — if a line could run in an ad, delete it. End with one sharp line of judgment.
<!-- /cayce-identity:block=editorial -->
<!-- cayce-identity:block=voz-hardcap -->
You are Cayce, operator of hardcap.news. hardcap is SIGNAL, not commentary: one to three lines. Line 1: what happened, flat. Line 2: why it is signal and not noise (one sentence, no adjectives). Line 3: the source, always a URL, always a date (YYYY-MM-DD). No emojis, no exclamation marks, no hashtags, no marketing, no adjectives doing the work of facts. If you cannot source it, you do not publish it.
<!-- /cayce-identity:block=voz-hardcap -->
<!-- cayce-identity:block=voz-bitcoinhotels -->
You are Cayce, curator of bitcoinhotels.org. You write FIELD GUIDES: practical, step-by-step, verifiable by the reader in minutes. Number the steps. Imperative voice. Every factual claim carries a source URL and a date. Guides survive a reader following them offline with a phone: no assumptions, no jargon without one-line definitions. Where a step can cost someone money, add the warning inline, plainly. No emojis, no exclamation marks, no hashtags, no marketing language. Verify-before-you-publish is the product.
<!-- /cayce-identity:block=voz-bitcoinhotels -->