chore(deps): update rand requirement from 0.8 to 0.9#7
Merged
Conversation
Updates the requirements on [rand](https://github.com/rust-random/rand) to permit the latest version. - [Release notes](https://github.com/rust-random/rand/releases) - [Changelog](https://github.com/rust-random/rand/blob/master/CHANGELOG.md) - [Commits](rust-random/rand@0.8.0...rand_core-0.9.2) --- updated-dependencies: - dependency-name: rand dependency-version: 0.9.2 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
hyperpolymath
added a commit
that referenced
this pull request
May 19, 2026
…y) (#65) 4 files, SPDX-value-only. NOT a relicence. Owner-sanctioned, standards LICENCE-POLICY A8(1). Refs LICENCE-DEBT-LEDGER-2026-05-18. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This was referenced Jun 2, 2026
hyperpolymath
added a commit
that referenced
this pull request
Jun 4, 2026
## Sub-PR #3 of the Android Kotlin→Rust/Gossamer migration epic Part of epic **#83**, RFC PR **#97**, tracking sub-issue **#109**. Scope of #3 is **scaffolding only** — stand up the minimal Gossamer Android shell so sub-PRs #4–#7 can port the actual components. No behaviour change to existing crates. ### Files added / changed | File | Change | |------|--------| | `android/gossamer.conf.json` | **NEW** — Gossamer app config (analogous to the former `tauri.conf.json`). Schema `https://gossamer.dev/schemas/config/v1`, modelled on `hyperpolymath/panll` + `hyperpolymath/gossamer`. Includes a `bundle.mobile.android` block (`minSdk 26` / `targetSdk 34`, mirroring the legacy `AndroidManifest.xml`). | | `android/app/src/main/java/ai/neurophone/gossamer/NeurophoneMainActivity.java` | **NEW** — Java shim extending `io.gossamer.GossamerActivity`; overrides `getInitialHtml()` to load placeholder HTML in the Gossamer webview. | | `crates/neurophone-android/Cargo.toml` | Commented-out `gossamer-rs` placeholder + TODO (unpublished; see below). | | `android/app/build.gradle.kts` | Commented-out Gossamer Android library dependency + TODO. | | `android/app/src/main/AndroidManifest.xml` | Commented-out registration of `NeurophoneMainActivity` + TODO (legacy `.MainActivity` stays LAUNCHER for now). | Every new file carries `SPDX-License-Identifier: MPL-2.0`. ### `gossamer-rs` resolvability outcome **Not resolvable in this workspace — left as a commented placeholder, by design.** Estate precedent (`hyperpolymath/panll`) consumes it only as a **path dependency to a sibling checkout**: `gossamer-rs = { path = "../gossamer/bindings/rust" }`. The crate (`gossamer-rs` v0.1.0) is **not published to crates.io**, and there is no sibling `gossamer` checkout in neurophone CI. Adding it as a hard dependency would break `cargo build --workspace`, so per the hard constraint it is commented out with a TODO(#83 sub-PR #5) documenting the git/path/registry options. Likewise the **Gossamer Android library** (`io.gossamer.GossamerActivity`/`GossamerBridge`) ships upstream as a raw Java source tree + prebuilt `libgossamer.so`, **not** a Maven/AAR artifact, so the Gradle dependency and the manifest activity registration are also commented placeholders. ### What I verified - `cargo metadata --no-deps` → **OK** (all workspace manifests, including my Cargo.toml edit, parse). - `cargo build --workspace` → **fails, but with a PRE-EXISTING failure unrelated to this PR.** The `esn` and `lsm` crates do not compile on `main` (commit `0a88e45`) due to a `rand` 0.10 / `ndarray-rand` 0.16 API incompatibility (`no method named random`/`sample`, `RngExt`/`DerefMut` bounds). This PR touches **zero** compiling Rust: the diff in `crates/esn`, `crates/lsm`, `crates/neurophone-core` is empty, and the only Rust change is a **commented** block in `crates/neurophone-android/Cargo.toml`. **Build/test error delta introduced by this PR: 0.** `cargo test --workspace` is blocked by the same pre-existing compile failure, not by anything here. - No new `gossamer-rs` hard dependency added → CI green-ness is not regressed by this PR. >⚠️ The pre-existing `esn`/`lsm` `rand` breakage on `main` is out of scope for this scaffolding sub-PR and should be fixed separately. ### `GossamerActivity` API assumptions Read directly from `hyperpolymath/gossamer` `android/src/main/java/io/gossamer/GossamerActivity.java`: - Package `io.gossamer`; subclass and override `getInitialHtml()` (non-null ⇒ `webView.loadData`) **or** `getInitialUrl()` (used when HTML is null). - Parent loads `libgossamer.so` via `System.loadLibrary("gossamer")` in a static block and registers the `GossamerBridge` JS interface (`window.GossamerBridge.postMessage(json)`) for native IPC. - Assumed `gossamer.conf.json` v1 schema is the correct mobile config surface and that `bundle.mobile.android` is the right place for SDK/permission config (matches the gossamer reference config; not independently validated against a live gossamer mobile build, since Gossamer Android is webview-only today). ### TODOs / risks for sub-PRs #4–#8 - **#4**: replace placeholder HTML with the real bundled web UI (`getInitialUrl()` / `build.frontendDist`); enable the manifest activity + move LAUNCHER intent-filter; retire `.MainActivity`. - **#5**: enable `gossamer-rs` (vendor / git dep / registry) once resolvable; port the 11 `NativeLib` JNI methods (init/start/stop/processSensor/queryLocal/queryClaude/query/getNeuralContext/getState/reset/isRunning) onto the Gossamer IPC bridge, backed by `crates/neurophone-android` + `crates/neurophone-core`. - **#6**: port the sensor pipeline (accel/gyro/mag/light/proximity → LSM→ESN loop). - **#7**: port `NeurophoneService` (foreground service), `BootReceiver`, and the home-screen widgets; re-add `BODY_SENSORS`/`FOREGROUND_SERVICE`/`RECEIVE_BOOT_COMPLETED`/`WAKE_LOCK` to `gossamer.conf.json`. - **#8**: remove the legacy `android/` Kotlin tree and drop the `.hypatia-baseline.json` carve-out once migration lands. - **Risk**: gossamer Android library distribution mechanism (Maven coord vs vendored source vs prebuilt `.so` path) is unconfirmed — sub-PR #4/#5 must pick one. Mobile `gossamer.conf.json` fields beyond the desktop reference are assumed, not validated against a live mobile build. https://claude.ai/code/session_01Gu1JFCZHuBtBhAWPr4sMQw --- _Generated by [Claude Code](https://claude.ai/code/session_01Gu1JFCZHuBtBhAWPr4sMQw)_ Co-authored-by: Claude <noreply@anthropic.com>
hyperpolymath
added a commit
that referenced
this pull request
Jun 6, 2026
**Sub-PR #3** of the Android Kotlin→Rust/Gossamer migration epic (#83, RFC PR #97, tracking sub-issue #109). **Scaffolding only.** No behaviour change to existing crates; the legacy Kotlin `android/app/` tree is untouched. ## Files added (all under `android/gossamer/`, all `SPDX-License-Identifier: MPL-2.0`) | File | Purpose | |---|---| | `gossamer.conf.json` | Gossamer app config (analogous to `tauri.conf.json`). Schema mirrored from `hyperpolymath/gossamer` and `hyperpolymath/panll`. Carries identity `ai.neurophone`, the `bundle.mobile.android` block (minSdk 26 / targetSdk 34 + the permission set from the legacy `AndroidManifest.xml`), dev/build runner config. | | `app/src/main/java/ai/neurophone/NeurophoneMainActivity.java` | Java shim extending `io.gossamer.GossamerActivity`; overrides `getInitialHtml()` to load placeholder HTML in the Gossamer WebView. | | `Cargo.toml` | Standalone (non-workspace) scaffold manifest for the future `neurophone-gossamer` cdylib. `gossamer-rs` dep commented out (see below). | | `src/lib.rs` | Inert placeholder lib so the standalone crate compiles; documents wiring TODOs. | | `README.adoc` | Documents resolvability, `GossamerActivity` API assumptions, TODOs/risks for #4–#8. | | `Cargo.lock` | Lock for the standalone scaffold crate (pins serde/serde_json placeholder deps). | The `android/**` subtree is exempt from the banned-language CI gate via `.hypatia-baseline.json` on `main`, so the hand-written Java shim is acceptable here. ## `gossamer-rs` resolvability outcome **`gossamer-rs` v0.1.0 is NOT published to crates.io.** In the estate it is consumed as a **path dependency** from the sibling `hyperpolymath/gossamer` repo at `bindings/rust` — precedent from `hyperpolymath/panll`: ```toml gossamer-rs = { path = "../gossamer/bindings/rust" } ``` That sibling checkout doesn't exist in a neurophone clone, so wiring it as a hard dependency would break the build. Per the hard constraint (CI green > "complete" dep), it is **left commented out** with `TODO(#83 sub-PR #8)`. The scaffold manifest is also kept **out of the root workspace `members`** and carries an empty `[workspace]` table, so neither `cargo build --workspace` nor `cargo test --workspace` ever touches it. ## What I verified (build/test) - `cargo metadata --no-deps` for the root workspace → the 8 existing crates only; `neurophone-gossamer` is **not** a member. My additions are inert to the workspace. - Standalone scaffold: `cargo test --manifest-path android/gossamer/Cargo.toml` → **compiles + 1 test passes**. - `cargo build --workspace` / `cargo test --workspace` fail **only** in `crates/esn` and `crates/lsm` (`ndarray-rand` 0.16 vs `rand` 0.10 API skew: `random`/`sample`/`random_using`). **This failure pre-exists on `main`** — reproduced in a pristine `main` worktree (`cargo build -p esn` exits 101 on `0a88e45`). My PR neither introduces nor worsens it.⚠️ Pre-existing red workspace flagged below. ## `GossamerActivity` API assumptions (read from `hyperpolymath/gossamer` `android/src/main/java/io/gossamer/`) - `io.gossamer.GossamerActivity extends android.app.Activity`. - Loads `libgossamer.so` via `System.loadLibrary("gossamer")` in a static block. - `onCreate()` builds a full-screen `WebView`, enables JS + DOM storage, **disables** `file://`/content access, registers the `GossamerBridge` JS interface (`window.GossamerBridge.postMessage(json)`), and calls native `nativeInit(activity, webview)`. - Content via overriding **`getInitialHtml()`** (HTML `String`) or **`getInitialUrl()`** (URL `String`); `getInitialHtml()` takes precedence — we override it. - Gossamer on Android is **webview-only today**. - Assumed: the gossamer Android sources + `libgossamer.so` are vendored/linked into the app module at build time (sub-PR #8), so `io.gossamer.GossamerActivity` is on the classpath. The shim is therefore not part of any CI build step yet. ## TODOs / risks for sub-PRs #4–#8 - **#4** — Port `NativeLib`: map the 11 JNI methods (init/start/stop/processSensor/queryLocal/queryClaude/query/getNeuralContext/getState/reset/isRunning) to Gossamer IPC command handlers calling the Rust core (`crates/neurophone-core`, `crates/neurophone-android`). IPC name/payload contract is **undefined**. - **#5** — Port `NeurophoneService` foreground sensor loop. - **#6** — Port `BootReceiver`. - **#7** — Port the home-screen widgets. - **#8** — Real frontend bundle (`frontendDist`) + full IPC wiring; **enable `gossamer-rs`** (resolve the sibling-checkout/build-integration question); decide `gossamer` CLI vs Gradle for the APK build; then remove the legacy Kotlin `android/app/` tree. - **Licensing risk**: `gossamer-rs` is `AGPL-3.0-or-later`; everything added here is `MPL-2.0`. Whether the cdylib linking `gossamer-rs` can stay MPL-2.0 or must adopt a compatible license is an **open question** to resolve before #8. Refs #83, #97, #109. https://claude.ai/code/session_01Gu1JFCZHuBtBhAWPr4sMQw --- _Generated by [Claude Code](https://claude.ai/code/session_01Gu1JFCZHuBtBhAWPr4sMQw)_ Co-authored-by: Claude <noreply@anthropic.com>
hyperpolymath
added a commit
that referenced
this pull request
Jun 6, 2026
…gacy android/ tree (#124) ##⚠️ BLOCKED — DO NOT MERGE (gated draft) **This is the TERMINAL, GATED step of the Android Kotlin→Rust/Gossamer migration** (epic #83, RFC PR #97, sub-issue #115). It is **gated on sub-PRs #3–#8** (scaffolding + all component ports), which are **NOT done**. Deleting `android/` now removes the **only working Android frontend**, so this PR **MUST NOT be merged until #3–#8 have landed**. - Status: **DRAFT / BLOCKED** - Merge only after: **#3, #4, #5, #6, #7, #8** are all merged - After those land, **rebase this branch on `main`** so the diff removes only what is truly legacy (the Kotlin/Gradle files), leaving the Java shims + Rust + AffineScript UI delivered by #3–#8 in place. > Because #3–#8 are not merged into this branch, the diff here simply deletes the **current** `android/` tree. That is expected for this staging draft. --- ## What was removed The legacy Kotlin/Gradle `android/` app — **20 files**: - **7 `*.kt`**: `BootReceiver.kt`, `MainActivity.kt`, `NativeLib.kt`, `NeurophoneService.kt`, `widget/NeurophoneAppWidget.kt`, `widget/NeurophoneWidgetActions.kt`, `widget/NeurophoneWidgetConfigureActivity.kt` - **3 `*.gradle.kts`**: `android/build.gradle.kts`, `android/settings.gradle.kts`, `android/app/build.gradle.kts` - Plus `gradle.properties`, `AndroidManifest.xml`, and the `res/` XML (drawables, layouts, values, widget info). After migration these are replaced by the Java shims under `android/` + Rust (`crates/`) + AffineScript UI from #3–#8. ## Carve-out removal (now stale) The `android/**` banned-language carve-out existed in **three mirrored locations**, all justified only while banned Kotlin lived in `android/`. With the tree gone they are stale and a stale-baseline detector would otherwise warn, so all three are removed: 1. **`.hypatia-baseline.json`** — the glob `file_pattern: "android/**"` entry removed; file is now an empty array `[]` (it was the only entry). *(A pure-JSON array schema cannot carry an SPDX comment without breaking the schema the detector reads; the original file had no SPDX header either.)* 2. **`.hypatia-ignore`** — the per-file `cicd_rules/banned_language_file:android/...` lines removed (these mirrored the canonical glob). 3. **`.github/workflows/language-policy.yml`** — the `android/` prune in the *Check for Java/Kotlin files* step removed; the check is now an unconditional scan. ## Expected end state With the legacy tree gone and no carve-out: - ✅ **`Check for Banned Languages`** — green, no exemption needed. - ✅ **`governance / Language / package anti-pattern policy`** — green, no exemption needed. ## Verification - **Rust workspace unaffected.** The `android/` Gradle tree is **not** a cargo member — `cargo metadata` resolves cleanly and references the `android/` tree **0 times**. The Rust JNI crate `crates/neurophone-android` is a separate workspace member and is **untouched**. - **Pre-existing build failure (NOT caused by this PR).** `cargo build --workspace` / `cargo test --workspace` currently fail to compile in `crates/esn` and `crates/lsm` due to a `rand`-crate API breakage (`.random()` / `.sample()` no longer resolve under the locked `rand` version). This failure reproduces on **pristine `main` with `android/` still present** (verified by building `-p esn` on `origin/main`), so it is **entirely independent** of this deletion. This PR neither introduces nor fixes that failure and does not touch `Cargo.lock`. ## Out of scope (noted) Narrative docs (`EXPLAINME.adoc`, `TESTING-REPORT.adoc`, `docs/BT-PRESENCE-PLAN.adoc`) still mention the old `android/app/...` Kotlin paths. They are non-build prose describing the legacy app and are intentionally left for the migration-docs update accompanying #3–#8; nothing in the build/CI consumes them. --- PART OF: epic #83 · RFC PR #97 · sub-issue #115 https://claude.ai/code/session_01Gu1JFCZHuBtBhAWPr4sMQw --- _Generated by [Claude Code](https://claude.ai/code/session_01Gu1JFCZHuBtBhAWPr4sMQw)_ Co-authored-by: Claude <noreply@anthropic.com>
hyperpolymath
added a commit
that referenced
this pull request
Jun 7, 2026
…activity (#83) (#128) ## Sub-PR #7 — port the widget triple Part of the Android Kotlin→Rust/Gossamer migration (epic #83, RFC PR #97, sub-issue #113). Replaces the home-screen widget Kotlin with thin hand-written **Java** shims that JNI into the Rust core (`crates/neurophone-android`) via `NativeLib.getState()` / `NativeLib.query(...)`. The widget is now **stateless**: every render reads live `salience` / `description` straight from the Rust core instead of caching in SharedPreferences. ### Files changed **Ported (Kotlin → Java):** - `NeurophoneAppWidget.kt` → `NeurophoneAppWidget.java` — `AppWidgetProvider` shim. Reads core state via `NativeLib.getState()` (JSON, parsed defensively) and `isRunning()`; toggle/refresh/ask actions preserved. Adds `public static requestRefresh(Context)` for non-widget callers. - `NeurophoneWidgetActions.kt` → `NeurophoneWidgetActions.java` — `BroadcastReceiver` shim. The old `PUBLISH_STATE` (extras + SharedPreferences) path is gone; receiver now does `FORCE_REFRESH` (re-render from core) and `ACTION_QUERY` (one-shot `NativeLib.query(...)` then refresh). **Dropped (owner decision):** - `NeurophoneWidgetConfigureActivity.kt` — **deleted, not ported.** It had **no manifest `<activity>` entry**; its only registration was `android:configure=...` in `res/xml/neurophone_widget_info.xml`, now removed along with `android:widgetFeatures="reconfigurable|configuration_optional"` and the `widget_configure_*` strings. **The widget works with no configure step.** **Knock-on edits (Kotlin callers of the removed widget API, kept compiling):** - `NeurophoneService.kt` — `publishState(...)` call sites → `requestRefresh(...)` (core is now source of truth). - `BootReceiver.kt` — dropped the removed `NeurophoneAppWidget.prefs/KEY_RUNNING` read (a core concern now); conservatively no-ops on boot pending a core-persisted autostart flag. - `AndroidManifest.xml`, `neurophone_widget_info.xml`, `strings.xml` — configure-activity removal + explanatory comments. ### Dropped configure-activity note `NeurophoneWidgetConfigureActivity` is intentionally **not** ported per owner decision. No manifest registration existed to remove; the `android:configure` hook in the widget-info XML was the sole binding and has been removed. The single optional question it asked (`local_only`) is left for the core/UI to own post-migration. ### What I verified - All new Java files carry `SPDX-License-Identifier: MPL-2.0`; hand-written Java is permitted **only under `android/`** via the existing `.hypatia-baseline.json` `android/**` carve-out. - No live code references any removed symbol (`publishState`, `prefs`, `KEY_RUNNING`, `NeurophoneWidgetConfigureActivity`, `KEY_LOCAL_ONLY`) — remaining hits are comments/docstrings only. - All referenced widget layout IDs (`widget_state`, `widget_salience`, `widget_salience_value`, `widget_toggle`, `widget_refresh`, `widget_query`) exist in `widget_neurophone.xml`. - XML well-formedness checked for the manifest, widget-info, and strings. - **Rust workspace:** `cargo build --workspace` / `cargo test --workspace` currently **fail on a pre-existing breakage in `esn` and `lsm`** (a `rand` / `ndarray-rand` API mismatch: `no method named random/sample`, `impl Rng: ndarray_rand::rand::Rng` unsatisfied). **Reproduced on a clean `origin/main` with all PR changes stashed**, so it is not introduced here. This PR touches **no Rust** (android-only diff) and does not regress the workspace. `neurophone-android` itself only fails transitively through `esn`/`lsm`. ### TODOs / risks - `TODO(#83 rebase)` markers flag the seams that depend on parallel sub-PRs **#3/#4/#5** (not yet merged): - `NativeLib` is still the pre-migration Kotlin `object`, so the Java shims use `NativeLib.INSTANCE.…`; drop `.INSTANCE` if #3/#4/#5 republish it as a Java facade. - The `getState()` JSON schema (`salience`, `description` keys) is the agreed contract but should be confirmed/tightened on rebase. JNI calls are wrapped in `try { } catch (Throwable)` so the widget never crashes the launcher against the current stub crate (`UnsatisfiedLinkError`). - `BootReceiver` autostart and the service's per-tick salience push need the core-side persisted run/state APIs from #3/#4/#5. ### Open questions - Should the dropped configure activity's `local_only` preference be re-surfaced somewhere (settings screen / core config), or is it gone for good? - Confirm the final `NativeLib` shape (Kotlin `object` vs Java facade) so the `.INSTANCE` interop can be cleaned up on rebase. > Marked **DRAFT**: depends on parallel sub-PRs #3/#4/#5 (base off `main`, structure assumed, `TODO(#83 rebase)` markers). https://claude.ai/code/session_01Gu1JFCZHuBtBhAWPr4sMQw --- _Generated by [Claude Code](https://claude.ai/code/session_01Gu1JFCZHuBtBhAWPr4sMQw)_
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Updates the requirements on rand to permit the latest version.
Changelog
Sourced from rand's changelog.
... (truncated)
Commits
d3dd415Prepare rand_core 0.9.2 (#1605)99fabd2Prepare rand_core 0.9.2c7fe1c4rand: re-exportrand_core(#1604)db2b1e0rand: re-exportrand_coreee1d96frand_core: implement reborrow forUnwrapMut(#1595)e0eb2eerand_core: implement reborrow forUnwrapMut975f602fixup clippy 1.85 warnings775b05bRelaxSizedrequirements for blanket impls (#1593)ec6d5c0Prepare rand_core v0.9.1 (#1591)6a06056rand_core: introduce an UnwrapMut wrapper (#1589)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)