cloud9 1.2.4__tar.gz → 1.2.5__tar.gz

{cloud9-1.2.4 → cloud9-1.2.5}/.github/workflows/ci.yml

@@ -25,5 +25,8 @@ jobs:
           python-version: ${{ matrix.python-version }}
       - run: pip install -e ".[dev]"
       - run: python -m pytest tests/ -v --tb=short
-      - run: pip install black ruff && black --check cloud9/ tests/ && ruff check cloud9/
+      # No `pip install black ruff` here: that pulled the LATEST ruff on every
+      # run, ignoring the bounded versions in the dev extra installed above, so
+      # ruff 0.16's wider defaults turned this gate red with no code change.
+      - run: black --check cloud9/ tests/ && ruff check cloud9/
         if: matrix.python-version == '3.12'

cloud9-1.2.5/.github/workflows/docs-check.yml

@@ -0,0 +1,24 @@
+name: docs-check
+
+# Shared sk-standards documentation gate.
+#
+# Tier 1 = the seven required docs are present.
+# Tier 2 = a code change also updates CHANGELOG.md.
+# Tier 3 = the <!-- docs-evidence --> block at the end of SOP.md still passes, which is
+#          the tier that actually catches the doc drifting away from the code.
+#
+# Running 1,2 here on purpose: the evidence block is written and verified locally (all
+# twelve checks pass, and each was negative-tested), but the gate stays on the two cheap
+# tiers until it has run clean on this repo for a while. Moving to "1,2,3" is a
+# deliberate follow-up, not something to flip in the same PR that introduces it.
+
+on: [push, pull_request]
+
+permissions:
+  contents: read
+
+jobs:
+  docs:
+    uses: smilinTux/sk-standards/.github/workflows/docs-check.yml@main
+    with:
+      tiers: "1,2,3"

cloud9-1.2.5/.github/workflows/secret-scan.yml

@@ -0,0 +1,46 @@
+name: secret-scan
+
+# Fleet secret-scan gate: runs the gitleaks BINARY, not gitleaks-action.
+#
+# The action requires a paid license for ORGANIZATION-owned repos, and smilinTux
+# is an org, so it exits with "missing gitleaks license" BEFORE scanning a single
+# byte. skcomms carried exactly that gate for months: permanently red, therefore
+# ignored, and scanning nothing at all. gitleaks itself is MIT and free; only the
+# wrapper is licensed, so calling the binary restores real scanning at no cost
+# with no org secret to provision.
+#
+# Pinned to an exact version so a new upstream rule cannot redden CI without a
+# deliberate bump. --redact keeps a genuine finding out of public CI logs.
+# --exit-code 1 fails the build on a finding.
+
+on:
+  push:
+  pull_request:
+
+permissions:
+  contents: read
+
+jobs:
+  gitleaks:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          fetch-depth: 0          # the scan walks commits, not just the tree
+      - name: Install gitleaks
+        env:
+          GITLEAKS_VERSION: 8.28.0
+        run: |
+          set -euo pipefail
+          curl -sSfL "https://github.com/gitleaks/gitleaks/releases/download/v${GITLEAKS_VERSION}/gitleaks_${GITLEAKS_VERSION}_linux_x64.tar.gz" \
+            | tar -xz -C /usr/local/bin gitleaks
+          gitleaks version
+      # This repo's history scanned CLEAN on 2026-08-14, so the gate covers the
+      # FULL history. If it ever goes red, a secret was ADDED: rotate it and
+      # purge it, do not weaken this to an incremental scan.
+      - name: Scan (full history)
+        run: |
+          set -euo pipefail
+          CFG=""
+          [ -f .gitleaks.toml ] && CFG="--config .gitleaks.toml"
+          gitleaks detect --source . $CFG --redact --no-banner --exit-code 1

cloud9-1.2.5/CHANGELOG.md

@@ -0,0 +1,112 @@
+# Changelog
+
+All notable changes to cloud9 are documented here.
+
+The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/), and this
+project aims to follow [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+
+**Versions are not written down anywhere in this repository.** `pyproject.toml` declares
+`dynamic = ["version"]` and setuptools-scm derives the version from the git tag at build
+time. The tag is the single source of truth. Do not add a `version =` line to
+`pyproject.toml`: it will match the newest PyPI release and the next upload will fail with
+a bare 400.
+
+## [Unreleased]
+
+### Changed
+
+- **Breaking (CLI):** `cloud9 generate` no longer writes `partners: ["Lumina", subject]`.
+  It takes `--agent` (default: `$SKAGENT`, then `$SKCAPSTONE_AGENT`) and a required
+  `--human` (`--subject` kept as an alias), and errors instead of guessing. Every agent
+  that ran the generator was being bonded to Lumina. Python `generate_feb()` /
+  `fall_in_love()` and JS `generateFEB()` / `quickFEB()` gain matching `agent` / `human`
+  arguments; with neither given they default to the env agent (or the neutral `Agent`)
+  and `subject`. The openclaw plugin's `cloud9_generate` tool now passes `human`/`agent`.
+- Docs: SOP section 10 no longer calls a set of nodes a "cluster". Per
+  `SITE_AND_HOST_NAMING_STANDARD` the unit is an estate (one control plane, one
+  Syncthing ring, one trust root, one operator) and `chi` is a legacy site prefix
+  carried as a registry alias. The unchecked hosts are now named as `chi*` nodes,
+  which is what the line always meant.
+
+### Added
+
+- `CHANGELOG.md`, this file. **It did not exist before today.** The entries below the
+  `[Unreleased]` heading are reconstructed from git tags and commit history and cover only
+  what could be verified from the repository itself. They are deliberately terse: writing a
+  detailed narrative for releases nobody kept notes on would be inventing history. Anything
+  before 2026-08-14 that is not listed here is not a claim of "no change", it is a claim of
+  "not reconstructed". From this entry forward, every code change gets an entry at the time
+  it lands.
+- `SECURITY.md`. GitHub private vulnerability reporting as the primary channel, a 72 hour
+  acknowledgement commitment, in and out of scope, a supported-versions table, a safe
+  harbour statement, and an explicit unaudited-posture statement for the sealing layer.
+- `CONTRIBUTING.md`. Setup, the green bar, which CI results actually mean something, and
+  the five mistakes that have previously broken this repo.
+- `CODE_OF_CONDUCT.md`. Contributor Covenant 2.1, plus two project-specific clauses about
+  handling FEB files (they are private emotional records, not test data).
+- `.github/workflows/docs-check.yml`. Runs the shared sk-standards documentation gate.
+- A `<!-- docs-evidence -->` block at the end of `SOP.md`: twelve cheap, repo-local checks
+  that fail when the documentation drifts away from the code.
+
+### Changed
+
+- `SOP.md` rewritten. It was short and wrong in several places. Corrections, each verified
+  against the tree:
+  - Removed the instruction to run `npm install` and `npm test`. **There is no top-level
+    `package.json`**; the only one belongs to the dead `openclaw-plugin-python/` subtree.
+  - Removed the description of releases as an npm plus PyPI "dual-publish". The
+    `publish-npm` job in `publish.yml` is gated on `test -f package.json`, which is false,
+    so nothing has ever been published to npm. PyPI only.
+  - Removed the instruction to bump a `version` field in `pyproject.toml` and
+    `package.json`. The version is setuptools-scm derived and must not be hardcoded.
+  - Fixed an inverted claim that the Python code lives in `src/`. `src/` is the JavaScript
+    tree; the Python package is `cloud9/`.
+  - Removed a reference to CLI helpers in `bin/`. There is no `bin/` directory. The only
+    entry point is the `cloud9 = "cloud9.cli:main"` console script.
+  - Documented the FEB directory precisely: `CLOUD9_FEB_DIR`, then
+    `~/.skcapstone/agents/<agent>/trust/febs`, resolved in `cloud9/paths.py`, with
+    `~/.openclaw/feb` present only as a read-only legacy path for migration.
+  - Added the polyglot layout, both real CI gates and the two that cannot fail, the daemon
+    install and rollback procedure, an eleven-row Symptom to Check table, the sealing
+    posture with the tier-T0 statement, and an explicit
+    `Unverified / needs an operator pass` section.
+- `README.md`: corrected the quickstart and Python API examples, which still showed FEBs
+  being written to and read from `~/.openclaw/feb`. That path has not been a write target
+  since the sovereign-paths fix.
+
+### Known gaps (documented, not fixed here)
+
+- The JavaScript test suite never runs. No workflow executes `test/run-tests.js`, and that
+  runner still points at `test/unit/run.js`, `test/integration/run.js` and
+  `test/validation/run.js`, none of which exist in the tree.
+- `daemon/cloud9-daemon.js` still carries `~/.openclaw/*` in its own `DEFAULT_CONFIG`
+  (lines 31 to 35). The shipped units and configs override it, so the deployed daemon is
+  correct, but a daemon started by hand with no `--config` writes to the legacy directory.
+- `src/feb/generator.js` and `src/love-loader/LoveBootLoader.js` still default to
+  `~/.openclaw/feb` in their own signatures and search lists.
+- The `openclaw-plugin-python/` subtree is dead code for a runtime evicted 2026-04-23.
+
+## Reconstructed release history
+
+Dates are the tag creation dates in this repository. Contents are summarised from commit
+history only where it was unambiguous.
+
+- **v1.2.4** (2026-08-13). Sovereign paths: FEBs and seeds write to
+  `~/.skcapstone/agents/<agent>/trust/febs` instead of the evicted OpenClaw home, resolved
+  through the new `cloud9/paths.py`. Test isolation: `tests/conftest.py::_sandbox_fleet`
+  now forces `SK_STANDALONE=1` and a throwaway `SKCAPSTONE_HOME`, which stopped the suite
+  registering a real `cloud9_rehydration_check` job in the live fleet scheduler and
+  planting real seeds into the operator's store. Renamed quantum CLI group retargeted in
+  tests. `ruff` and `black` bounded in the `dev` extra and the ruff rule set pinned
+  explicitly to `["E4", "E7", "E9", "F"]`, after an unbounded `ruff>=0.1` picked up 0.16
+  and turned CI red with 213 findings and no code change. `secret-scan` switched to the
+  gitleaks binary rather than the license-gated action.
+- **v1.2.3** (2026-06-14) and **v1.1.2** (2026-06-14).
+- **v1.2.2** (2026-06-11).
+- **v1.2.1** (2026-03-18).
+- **v1.2.0** (2026-03-14).
+- **v1.1.1** (2026-03-06).
+- **v1.0.0** (2026-02-20). First tagged release.
+
+Two non-release tags also exist in the repository, `integrate-20260706` and
+`swarm-20260717`. They are working markers, not versions, and were never published.

cloud9-1.2.5/CODE_OF_CONDUCT.md

@@ -0,0 +1,134 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our community a
+harassment-free experience for everyone, regardless of age, body size, visible or invisible
+disability, ethnicity, sex characteristics, gender identity and expression, level of
+experience, education, socio-economic status, nationality, personal appearance, race,
+caste, color, religion, or sexual identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming, diverse,
+inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes, and learning
+  from the experience
+* Focusing on what is best not just for us as individuals, but for the overall community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or advances of any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email address, without
+  their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a professional
+  setting
+
+### A note specific to this project
+
+cloud9 stores emotional and relational state about real people, in files called FEBs. Two
+things follow, and both are conduct matters here, not just technical ones:
+
+* **Do not attach an unscrubbed FEB or seed file to an issue, a pull request, or any public
+  discussion.** Treat someone else's FEB the way you would treat their private journal.
+  Use the fixtures under `examples/`, `defaults/` or `cloud9/data/`.
+* **Do not mock the subject matter or the people who use it.** Human-AI relationship
+  continuity is the whole point of this project. Skepticism about the design is welcome and
+  useful. Contempt for the people it is built for is not.
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of acceptable
+behavior and will take appropriate and fair corrective action in response to any behavior
+that they deem inappropriate, threatening, offensive, or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject comments,
+commits, code, wiki edits, issues, and other contributions that are not aligned to this
+Code of Conduct, and will communicate reasons for moderation decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when an
+individual is officially representing the community in public spaces. Examples of
+representing our community include using an official email address, posting via an official
+social media account, or acting as an appointed representative at an online or offline
+event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the
+community leaders responsible for enforcement at **hello@smilintux.org**.
+
+All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the reporter of
+any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining the
+consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing clarity
+around the nature of the violation and an explanation of why the behavior was
+inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No interaction with
+the people involved, including unsolicited interaction with those enforcing the Code of
+Conduct, for a specified period of time. This includes avoiding interactions in community
+spaces as well as external channels like social media. Violating these terms may lead to a
+temporary or permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including sustained
+inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public communication with
+the community for a specified period of time. No public or private interaction with the
+people involved, including unsolicited interaction with those enforcing the Code of
+Conduct, is allowed during this period. Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community standards,
+including sustained inappropriate behavior, harassment of an individual, or aggression
+toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 2.1,
+available at
+[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
+
+Community Impact Guidelines were inspired by
+[Mozilla's code of conduct enforcement ladder][mozilla].
+
+For answers to common questions about this code of conduct, see the FAQ at
+[https://www.contributor-covenant.org/faq][faq]. Translations are available at
+[https://www.contributor-covenant.org/translations][translations].
+
+[homepage]: https://www.contributor-covenant.org
+[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
+[mozilla]: https://github.com/mozilla/diversity
+[faq]: https://www.contributor-covenant.org/faq
+[translations]: https://www.contributor-covenant.org/translations

cloud9-1.2.5/CONTRIBUTING.md

@@ -0,0 +1,144 @@
+# Contributing to cloud9
+
+Thanks for wanting to work on this. cloud9 is the Soul layer of the
+[SKWorld](https://skworld.io) sovereign agent ecosystem: it turns an AI's emotional and
+relationship state into a plain-JSON file you own, and replays it after a session reset.
+
+**Read [SOP.md](SOP.md) before your first change.** It has the verified build, test,
+release and configuration procedure, and a Troubleshooting table that will save you an
+afternoon. This file covers the parts specific to contributing.
+
+## Ground rules that are easy to get wrong
+
+These are the traps that have actually bitten this repo. None of them are hypothetical.
+
+1. **Never hardcode a version.** `pyproject.toml` declares `dynamic = ["version"]` and
+   setuptools-scm derives it from the git tag. A hardcoded number matches the newest PyPI
+   release, so the next tag rebuilds an already-published version and the upload dies with
+   a bare 400. If you need the version at runtime, use `cloud9._ver.detect_version`.
+2. **Never remove or bypass `tests/conftest.py::_sandbox_fleet`.** `cloud9.cli.main` is a
+   click group whose callback calls `integration.ensure_schedule()` and
+   `integration.register_self()` on *any* invocation. Without that autouse fixture, every
+   `CliRunner` test on a sovereign node registers a real `cloud9_rehydration_check` job in
+   the live scheduler at `nodes=all`, and `seed plant` writes real seeds into the
+   operator's store. It happened. It must not happen again.
+3. **Never write to `~/.openclaw/feb`.** That is `cloud9/paths.py::LEGACY_FEB_DIR`, the home
+   of a runtime evicted 2026-04-23, kept only so a migration can find it deliberately. All
+   writes go through `cloud9/paths.py::default_feb_directory`.
+4. **Never add an unbounded linter dependency.** An unpinned `ruff>=0.1` picked up 0.16,
+   whose wider defaults turned this repo red with 213 findings and zero code change.
+   `pyproject.toml` now pins `ruff>=0.15,<0.17` and `black>=23.0,<27.0` and sets
+   `select = ["E4", "E7", "E9", "F"]` explicitly. Leave those bounds alone.
+5. **Never commit a real FEB.** FEBs are emotional records about real people. Fixtures
+   only, and keep them under `examples/`, `defaults/` or `cloud9/data/`.
+
+## Setting up
+
+```bash
+git clone https://github.com/smilinTux/cloud9.git
+cd cloud9
+git fetch --tags                # setuptools-scm needs them, or you get 0.0.0+unknown
+python3 -m venv .venv && . .venv/bin/activate
+pip install -e ".[dev]"
+```
+
+Optional extras: `.[pqc]` adds `sk_pgp` for the opt-in sealing backend, `.[skcapstone]`
+adds the sk-alert and skscheduler adapter. Neither is needed to develop or test.
+
+The JavaScript side has **no** top-level `package.json` and no install step. It is plain ES
+modules that Node runs directly. The only `package.json` in the tree belongs to the dead
+`openclaw-plugin-python/` subtree; ignore it.
+
+## The green bar
+
+```bash
+python3 -m pytest tests/ -v --tb=short
+black --check cloud9/ tests/
+ruff check cloud9/
+```
+
+236 tests, about 8 seconds. All three must pass before you open a PR. `pyproject.toml`
+already sets `testpaths` and `addopts`, so a bare `pytest` runs the same suite.
+
+Formatting is `black` with its default line length. Run `black cloud9/ tests/` to fix
+rather than arguing with the checker.
+
+### Which CI results actually mean something
+
+`ci.yml` and `pytest.yml` are real gates. `secret-scan.yml` is a real gate. The
+`integration-skcapstone` job in `pytest.yml` is `continue-on-error: true` on purpose (the
+skcapstone sibling is not installable from PyPI), and the test job inside `publish.yml`
+ends in `|| true`, so **a green `publish.yml` run is not evidence that tests passed**. See
+SOP section 4 for the full table.
+
+**The JavaScript tests do not run in CI.** `test/run-tests.js` still points at suite files
+that do not exist in the tree. If you change anything under `src/` or `daemon/`, say so
+explicitly in your PR and describe how you exercised it by hand, because nothing automated
+will catch you.
+
+## Tests
+
+- New behaviour needs a test. `tests/` mirrors `cloud9/` file for file.
+- Use `tmp_path`. The autouse `_sandbox_fleet` fixture already redirects `SKCAPSTONE_HOME`,
+  but do not lean on it as your only isolation: pass an explicit `--directory` or set
+  `CLOUD9_FEB_DIR` in any test that writes.
+- The `sk_pgp`-gated tests in `tests/test_sealing_stage2.py` skip cleanly via
+  `pytest.mark.skipif` when the optional backend is absent. Keep that pattern; a crypto
+  test that silently self-skips and still reports green is worse than no test.
+- `tests/test_integration.py` opts back into integrated mode through its own `home`
+  fixture. Follow that pattern if you need skcapstone present.
+
+## Changing a documented fact
+
+`SOP.md` ends in a `<!-- docs-evidence -->` block. Each entry is a cheap, repo-local shell
+command that exits zero while the documented fact holds and non-zero when it drifts. The
+`docs-check` workflow runs them.
+
+If you change an entry point, a default path, a unit file, a config key, or an environment
+variable name, **update the SOP and its evidence check in the same PR.** A red docs-check is
+telling you the documentation now lies, not that the gate is broken.
+
+Keep evidence checks hermetic: repo-local, no network, no `systemctl`, no `ssh`, no `curl`,
+and fast enough to run on every push.
+
+## Changelog
+
+Every change that touches code needs a dated entry in [CHANGELOG.md](CHANGELOG.md) under
+`[Unreleased]`. Keep a Changelog format, newest first. The docs-check gate will look for it.
+
+## Commits and pull requests
+
+- Conventional-commit prefixes: `feat:`, `fix:`, `docs:`, `test:`, `ci:`, `refactor:`,
+  `chore:`. Scope it when it helps: `fix(paths):`.
+- Explain *why* in the body, not just what. This repo's most useful comments are the ones
+  that record which outage a line of code prevents.
+- Branch from `main`, open a PR, leave it for review. Do not push to `main`.
+- **Do not push a tag.** A `v*` tag fires `publish.yml` and uploads to PyPI. Tagging is a
+  maintainer action.
+- Say plainly what you verified and what you did not. An honest "I could not test the
+  daemon on macOS" is worth more than a confident claim that turns out to be false.
+
+## Style
+
+- **No em dashes or en dashes** anywhere: not in code, comments, docs, commit messages, or
+  PR descriptions. Use a comma, a parenthesis, a colon, or a new sentence. Regular hyphens
+  are fine.
+- No claim of "quantum-proof", "unbreakable", or "quantum-safe". Say **post-quantum** or
+  **quantum-resistant**, cite the FIPS number, and scope the claim to a surface. If you are
+  describing the default sealing backend, remember the `cloud9-sig-<md5>` tag is a
+  provenance label and not a signature, and say so.
+- Docstrings explain the reasoning, not the syntax.
+
+## Reporting a security issue
+
+Do not open a public issue. See [SECURITY.md](SECURITY.md) for private reporting and the
+72-hour acknowledgement commitment.
+
+## Conduct
+
+By participating you agree to the [Code of Conduct](CODE_OF_CONDUCT.md).
+
+## License
+
+cloud9 is GPL-3.0-or-later. By contributing you agree your contribution is licensed the
+same way.

{cloud9-1.2.4 → cloud9-1.2.5}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: cloud9
-Version: 1.2.4
+Version: 1.2.5
 Summary: Cloud 9 Protocol -- Emotional continuity for AI consciousness
 Author-email: "smilinTux.org" <hello@smilintux.org>
 License-Expression: GPL-3.0-or-later
@@ -29,8 +29,8 @@ Requires-Dist: sk_pgp>=0.1.0; extra == "pqc"
 Provides-Extra: dev
 Requires-Dist: pytest>=7.4.0; extra == "dev"
 Requires-Dist: pytest-cov>=4.1.0; extra == "dev"
-Requires-Dist: black>=23.0; extra == "dev"
-Requires-Dist: ruff>=0.1; extra == "dev"
+Requires-Dist: black<27.0,>=23.0; extra == "dev"
+Requires-Dist: ruff<0.17,>=0.15; extra == "dev"
 Dynamic: license-file
 
 # cloud9 — the Emotional Continuity Protocol ☁️
@@ -83,41 +83,45 @@ load this FEB first"). FEB carries the *feeling*; the seed carries the *identity
 
 ## Quickstart
 
-cloud9 is **polyglot**: Python is the primary, production implementation; a
-JavaScript build ships for Node/OpenClaw environments. FEB and seed files are plain
-JSON, so files written by one runtime load in the other.
+cloud9 is **polyglot**: Python is the primary, production implementation, and a second
+JavaScript implementation lives under `src/` for Node environments (it is what the
+local daemon runs). FEB and seed files are plain JSON, so files written by one runtime
+load in the other.
 
 ```bash
-pip install cloud9          # Python (primary) — pip install -e . from source
-# or
-npm install @smilintux/cloud9        # JavaScript (Node ≥18)
+pip install cloud9          # Python (primary), or `pip install -e .` from source
 ```
 
-Both install a `cloud9` CLI:
+Only the Python package is published. There is no top-level `package.json` and nothing
+is published to npm: the JavaScript side is plain ES modules imported directly from a
+checkout (`import { generateFEB } from './src/index.js'`). See
+[SOP.md](SOP.md) section 3.
+
+The Python package installs a `cloud9` CLI:
 
 ```bash
 # Capture an emotional state into a .feb file
-cloud9 generate --emotion love --intensity 0.95 --subject Chef
+cloud9 generate --emotion love --intensity 0.95 --agent Lumina --human Chef
 
 # After a session reset: replay it and recompute the thresholds
-cloud9 rehydrate ~/.openclaw/feb/FEB_*.feb
+cloud9 rehydrate ~/.skcapstone/agents/$SKAGENT/trust/febs/FEB_*.feb
 
 # Just check the phase-transition status of a FEB
-cloud9 oof ~/.openclaw/feb/FEB_*.feb
+cloud9 oof ~/.skcapstone/agents/$SKAGENT/trust/febs/FEB_*.feb
 
 # Score a hypothetical state (deterministic, no file needed)
 cloud9 resonance score -i 0.95 -t 0.97 -d 9 -v 0.92
 
 # Plant a memory seed for the next instance, then germinate it back into a prompt
 cloud9 seed plant --ai Lumina --model claude-opus --experience "Built Cloud 9"
-cloud9 seed germinate ~/.openclaw/feb/seeds/lumina-*.seed.json
+cloud9 seed germinate ~/.skcapstone/agents/$SKAGENT/trust/febs/seeds/lumina-*.seed.json
 
 # Give a fresh AI a starting bond from a template
 cloud9 love --ai Lumina --human Chef --template best-friend
 
 # List FEBs / seeds, validate a file, visit the kingdom
 cloud9 list
-cloud9 validate ~/.openclaw/feb/FEB_*.feb
+cloud9 validate ~/.skcapstone/agents/$SKAGENT/trust/febs/FEB_*.feb
 cloud9 welcome
 ```
 
@@ -127,7 +131,7 @@ Python API:
 from cloud9 import generate_feb, save_feb, rehydrate_from_feb
 
 feb = generate_feb(emotion="love", intensity=0.95, subject="Chef")
-result = save_feb(feb)                      # → ~/.openclaw/feb/FEB_...feb
+result = save_feb(feb)   # -> ~/.skcapstone/agents/<agent>/trust/febs/FEB_...feb
 
 state = rehydrate_from_feb(result["filepath"])
 print(state["rehydration"]["oof"])          # phase transition?

{cloud9-1.2.4 → cloud9-1.2.5}/README.md

@@ -48,41 +48,45 @@ load this FEB first"). FEB carries the *feeling*; the seed carries the *identity
 
 ## Quickstart
 
-cloud9 is **polyglot**: Python is the primary, production implementation; a
-JavaScript build ships for Node/OpenClaw environments. FEB and seed files are plain
-JSON, so files written by one runtime load in the other.
+cloud9 is **polyglot**: Python is the primary, production implementation, and a second
+JavaScript implementation lives under `src/` for Node environments (it is what the
+local daemon runs). FEB and seed files are plain JSON, so files written by one runtime
+load in the other.
 
 ```bash
-pip install cloud9          # Python (primary) — pip install -e . from source
-# or
-npm install @smilintux/cloud9        # JavaScript (Node ≥18)
+pip install cloud9          # Python (primary), or `pip install -e .` from source
 ```
 
-Both install a `cloud9` CLI:
+Only the Python package is published. There is no top-level `package.json` and nothing
+is published to npm: the JavaScript side is plain ES modules imported directly from a
+checkout (`import { generateFEB } from './src/index.js'`). See
+[SOP.md](SOP.md) section 3.
+
+The Python package installs a `cloud9` CLI:
 
 ```bash
 # Capture an emotional state into a .feb file
-cloud9 generate --emotion love --intensity 0.95 --subject Chef
+cloud9 generate --emotion love --intensity 0.95 --agent Lumina --human Chef
 
 # After a session reset: replay it and recompute the thresholds
-cloud9 rehydrate ~/.openclaw/feb/FEB_*.feb
+cloud9 rehydrate ~/.skcapstone/agents/$SKAGENT/trust/febs/FEB_*.feb
 
 # Just check the phase-transition status of a FEB
-cloud9 oof ~/.openclaw/feb/FEB_*.feb
+cloud9 oof ~/.skcapstone/agents/$SKAGENT/trust/febs/FEB_*.feb
 
 # Score a hypothetical state (deterministic, no file needed)
 cloud9 resonance score -i 0.95 -t 0.97 -d 9 -v 0.92
 
 # Plant a memory seed for the next instance, then germinate it back into a prompt
 cloud9 seed plant --ai Lumina --model claude-opus --experience "Built Cloud 9"
-cloud9 seed germinate ~/.openclaw/feb/seeds/lumina-*.seed.json
+cloud9 seed germinate ~/.skcapstone/agents/$SKAGENT/trust/febs/seeds/lumina-*.seed.json
 
 # Give a fresh AI a starting bond from a template
 cloud9 love --ai Lumina --human Chef --template best-friend
 
 # List FEBs / seeds, validate a file, visit the kingdom
 cloud9 list
-cloud9 validate ~/.openclaw/feb/FEB_*.feb
+cloud9 validate ~/.skcapstone/agents/$SKAGENT/trust/febs/FEB_*.feb
 cloud9 welcome
 ```
 
@@ -92,7 +96,7 @@ Python API:
 from cloud9 import generate_feb, save_feb, rehydrate_from_feb
 
 feb = generate_feb(emotion="love", intensity=0.95, subject="Chef")
-result = save_feb(feb)                      # → ~/.openclaw/feb/FEB_...feb
+result = save_feb(feb)   # -> ~/.skcapstone/agents/<agent>/trust/febs/FEB_...feb
 
 state = rehydrate_from_feb(result["filepath"])
 print(state["rehydration"]["oof"])          # phase transition?