…117)

## Why

PR #105 added the android/** carve-out via **two** mechanisms:

- (a) Prune `android/` from a local `find` step in
`.github/workflows/language-policy.yml`
- (b) Add `.hypatia-baseline.json` with `file_pattern: "android/**"`

The estate-wide reusable at
`hyperpolymath/standards/.github/workflows/governance-reusable.yml`
(called from this repo's `governance.yml`) **already** reads
`.hypatia-baseline.json` and exempts matched paths in its own
`language-policy` job (see `governance-reusable.yml:91-285`).

**(b) alone is sufficient.** (a) is a duplicate that uses the brittle
`find` mechanism the reusable explicitly warns against — `git ls-files`
respects `.gitignore` correctly.

## What this PR does

Removes the local `Check for Java/Kotlin files` step. The neurophone
`.hypatia-baseline.json` carve-out continues to handle the android/**
exemption via the estate-wide reusable.

## Net behaviour change

**Zero.** The local check duplicated the estate check. Both gate on
Java/Kotlin files; both exempt android/** via different mechanisms.
Removing the local check means there's one mechanism instead of two, and
the remaining mechanism is the auditable baseline file.

## Properties preserved

- Kotlin (`.kt`, `.kts`) is still fully banned — by the estate-wide
reusable's `enforce "Java/Kotlin files"` block.
- Non-Android Java (e.g. a stray `Foo.java` at repo root) is still
blocked — same path.
- The `android/**` carve-out is still respected via
`.hypatia-baseline.json`.

## Stale-entry cleanup at end of migration

When the Gossamer migration completes and `android/` is removed, the
baseline entry will become stale. The reusable's `Detect stale baseline
entries` job (`governance-reusable.yml:127+`) will warn. The entry can
be removed in the same PR that deletes `android/` (i.e. sub-PR #9 of the
migration sequence in RFC PR #97).

## Supersedes

- `hyperpolymath/standards#341` (closed) — estate-wide grep change was
redundant given the baseline mechanism already exists.
- `#107` (closed) — same intent as this PR but
pre-#105; rebase would have been a different change.

## Test plan

- [x] Workflow YAML is well-formed (visually verified).
- [ ] CI passes — local language-policy.yml runs without the Java/Kotlin
step; estate-wide reusable runs and exempts android/** via baseline.
- [ ] Negative test: a hypothetical `Foo.java` at repo root would still
trigger the estate-wide `Language / package anti-pattern policy` job
(verified by inspection of `governance-reusable.yml:345` + `enforce()`
at line 310 + `is_exempt()` at line 292).

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

…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>