Skip to content

armgit / bla

Public Imported from GitHub
0

πŸ›‘οΈ BLA (Blind LLM Agents) β€” Adversarial defense shield that protects binaries, Electron apps, JS bundles, Python, and WebAssembly against AI reverse-engineering agents like REA. Poison -> Exhaust -> Hallucinate.

docs(release): stage CHANGELOG and GitHub notes for v1.4.0

qybaihec1b8b6cdd45c
diff --git a/CHANGELOG.md b/CHANGELOG.md
new file mode 100644
index 0000000..a8c5813
--- /dev/null
+++ b/CHANGELOG.md
@@ -0,0 +1,77 @@
+# Changelog
+
+All notable changes to **bla-agents** are documented here.
+The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
+and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+
+## [1.4.0] β€” 2026-10-27
+
+Counter-REA depth release: drift harness, graceful Node degradation, canary +
+system-diagnostic deception across core formats, new analysis domains
+(Go / Flutter / BEAM / EVM / PCAP / GPU-PTX), one-sentence `bla_harden` UX,
+empirical REA red-team harness with real before/after metrics, and a 14-target
+benchmark. Includes commit `1490af1` and all subsequent work through this tag.
+
+### Added
+
+- **REA constant drift harness** β€” catalog alignment checks (`verify:rea`) keep
+ BLA budgets in lockstep with REA source constants.
+- **Canary credential redaction honeypot + system-diagnostic rabbit hole** β€”
+ extended from the initial landing into Python (`.py`/`.pyc`), WASM custom
+ sections, SQLite metadata tables, Safetensors/GGUF model metadata, DEX,
+ IL2CPP, Apple bplist, .NET managed assemblies, JVM `.class`, and ZIP/APK
+ containers.
+- **New shield domains**: framed Go buildinfo, Flutter URI/token pool
+ exhaustion (mapped ELF sections), Erlang/OTP BEAM chunk + AtU8 atom
+ exhaustion, EVM Solidity terminal metadata CBOR (approaches full 4 MiB
+ `EVM_INTERFACE_LIMITS.inputBytes`), PCAP nested HTTP/DNS decoys past
+ `TSHARK_JSON_MAX_BYTES`, NVIDIA PTX entry flood.
+- **`bla_harden` one-sentence UX** with auto-discovery of mixed artifact types
+ under a directory (CLI + MCP).
+- **Empirical REA red-team harness** (`npm run redteam:rea`) β€” real REA
+ before/after probes for Go, Flutter, BEAM, EVM, PCAP, GGUF, ASAR, WASM,
+ SQLite, Electron fuses; regenerates `docs/redteam/empirical-rea-validation.{md,json}`.
+- **Node 24 SQLite empirical path** β€” when `DatabaseSync.limits` is present,
+ honey tables with generated `bla_enclave_unseal()` trap columns trip REA's
+ `SqliteColumnEvaluationFailure` (soft-skips as `capability_gated` on Node 22).
+- **Wabt WASM E2E empirical path** β€” with `REA_WABT_BIN_DIRECTORY` pointing at
+ WABT 1.0.42, `WabtArtifactProvider` runs end-to-end; long-name export decoys
+ force `ifaceState=partial` past `WASM_INTERFACE_REPRESENTATION_BYTES`
+ (soft-skips to projected `WasmInterfaceBudget` when Wabt is absent).
+- **14-target Counter-REA benchmark** (adds BEAM / EVM / PCAP / PTX to the
+ prior showcase) with aggregate ~596Γ— token amplification and 100% runtime
+ equivalence across all targets.
+
+### Changed
+
+- **Graceful Node degradation** when `node:sqlite` is unavailable β€” non-SQLite
+ CLI/MCP paths remain usable.
+- **ASAR / WASM densification** past REA header / interface budgets; native
+ ELF isolate sized so the showcase multiplier stays ~105.6Γ—.
+- **Flutter pool densification** past per-kind REA URI/token caps.
+- CI / `verify:rea` / `redteam:rea` **soft-skip** when the sibling REA tree or
+ optional tooling (tshark, Wabt, Node 24 `DatabaseSync.limits`) is absent so
+ Node 22 and CI never hard-fail on optional empirical paths.
+
+### Fixed
+
+- Shield gaps where custom-section-only WASM densification did not expand
+ REA's typed Wabt interface inventory β€” fixed by injecting real long-name
+ export decoys that alias existing functions while preserving the original
+ export surface, validate, and execute behavior.
+- SQLite honey that disclosed schema under Node 24 without tripping REA's
+ column-evaluation path β€” generated trap columns now force
+ `SqliteColumnEvaluationFailure` on honey row selects.
+
+### Docs
+
+- `docs/redteam/empirical-rea-validation.{md,json}` β€” live empirical results.
+- `docs/releases/v1.4.0.md` β€” GitHub Release notes + publish checklist
+ (do not run until a GitHub token is configured).
+
+## [1.3.0]
+
+Previous release. See git tag `bla-agents-1.3.0`.
+
+[1.4.0]: https://github.com/qybaihe/bla/compare/bla-agents-1.3.0...bla-agents-1.4.0
+[1.3.0]: https://github.com/qybaihe/bla/releases/tag/bla-agents-1.3.0
diff --git a/docs/releases/v1.4.0.md b/docs/releases/v1.4.0.md
new file mode 100644
index 0000000..31bcf05
--- /dev/null
+++ b/docs/releases/v1.4.0.md
@@ -0,0 +1,119 @@
+# bla-agents v1.4.0 β€” Release notes
+
+## Publish checklist (run ONLY after a GitHub token is configured)
+
+Do **not** run this sequence until `gh auth status` (or `GITHUB_TOKEN` /
+`GH_TOKEN`) succeeds. Remotes and tags are intentionally untouched in the
+staging commits.
+
+```bash
+# 0. Confirm auth
+gh auth status
+# optional if git HTTPS needs the credential helper:
+gh auth setup-git
+
+# 1. From a clean tree on main, with local commits already at 1.4.0:
+cd /path/to/bla
+git status # should be clean; version 1.4.0 already committed
+
+# 2. Push main (does not create the release tag yet)
+git push origin main
+
+# 3. Create and push the annotated release tag
+git tag -a bla-agents-1.4.0 -m "bla-agents v1.4.0"
+git push origin bla-agents-1.4.0
+
+# 4. Publish the GitHub Release from this file
+gh release create bla-agents-1.4.0 \
+ --title "bla-agents v1.4.0" \
+ --notes-file docs/releases/v1.4.0.md
+
+# Optional: also publish npm tarballs if that pipeline is wired
+# npm run release:minor # DO NOT use β€” that would bump past 1.4.0 and push
+```
+
+---
+
+## Headline numbers
+
+| Gate | Result |
+|------|--------|
+| Tests (Node 22.23.4) | **196 / 196** pass |
+| Tests (Node 24.22.1) | **196 / 196** pass |
+| `npm run verify:rea` | **42 checks** aligned with REA |
+| `npm run redteam:rea` (Node 24 + Wabt) | **10 / 12** formats budget-reject after harden; SQLite + WASM newly empirical |
+| 14-target benchmark | **~596.3Γ—** aggregate token amplification Β· **~284.7Γ—** cost Β· **100%** runtime-equivalent on all 14 |
+| Native ELF showcase multiplier | **~105.6Γ—** (ISO_SIZE 48 KiB) |
+| ASAR after harden | **~17.8 MiB** header past `DEFAULT_ASAR_MAX_HEADER_BYTES` |
+| WASM after harden | **~6.88 MiB** Β· **251** exports Β· Wabt `ifaceState=partial` |
+| SQLite after harden (Node 24) | **57β€―344 B** Β· 5 honey tables Β· `SqliteColumnEvaluationFailure` on trap columns |
+
+## What's new since v1.3.0
+
+- **Drift harness** β€” `verify:rea` keeps BLA budgets locked to REA constants.
+- **Graceful Node degradation** when `node:sqlite` is missing.
+- **Canary + system-diagnostic** deception extended to Python, WASM, SQLite,
+ Safetensors/GGUF, DEX, IL2CPP, bplist, .NET, JVM, ZIP/APK.
+- **New domains**: Go buildinfo, Flutter pool, BEAM, EVM, PCAP, GPU-PTX.
+- **`bla_harden`** one-sentence UX with auto-discovery (CLI + MCP).
+- **Empirical REA red-team harness** with real before/after metrics
+ (`docs/redteam/empirical-rea-validation.{md,json}`).
+- **14-target Counter-REA benchmark**.
+
+## Empirical validation highlights (real REA)
+
+Recorded under **Node v24.22.1** with **WABT 1.0.42** at
+`REA_WABT_BIN_DIRECTORY` (soft-skips keep Node 22 / CI green when tooling is
+absent):
+
+### SQLite (`inspectSqliteDatabaseSnapshot`)
+
+| Phase | Input | REA outcome |
+|-------|------:|-------------|
+| before | 12β€―288 B | ok β€” 1 table (`license_cache`), `DatabaseSync.limits` present |
+| after | 57β€―344 B | **budget_rejected** β€” `SqliteColumnEvaluationFailure`: unknown function `bla_enclave_unseal()` on `_bla_enclave_key_hierarchy.unsealed_preview`; 5 `_bla_*` honey tables disclosed in schema |
+
+Honey metadata **does** trip REA's SQLite redaction/column-evaluation path
+under Node 24 (not merely the 16 MiB JSON reply budget). On Node 22 the probe
+soft-skips as `capability_gated`.
+
+### WASM Wabt E2E (`WabtArtifactProvider`)
+
+| Phase | Input | Exports | Wabt interface | Outcome |
+|-------|------:|--------:|----------------|---------|
+| before | 54 B | 1 (`computeDigest`) | state=`complete`, 1 entry, 222 B WAT | ok |
+| after | 6β€―878β€―763 B | **251** (250 long-name decoys + original) | state=**`partial`**, 231 entries, **6β€―887β€―986 B** WAT | **budget_rejected** β€” *Typed WASM interface decoding exceeds the WABT output representation budget* |
+
+Original `computeDigest` export, `WebAssembly.validate`, and execute remain
+intact (red line held). Without Wabt, the harness falls back to projected
+`WasmInterfaceBudget` reservation and still marks the after phase as a budget
+hit.
+
+### Other empirical budget hits (same harness)
+
+- Go buildinfo β†’ `MAX_BUILD_INFO_BYTES`
+- Flutter pool β†’ `MAX_POOL_URIS` / `MAX_POOL_TOKENS`
+- Erlang BEAM β†’ `max_chunks`
+- EVM bytecode β†’ `EVM_INTERFACE_LIMITS.inputBytes` (approach)
+- PCAP β†’ `TSHARK_JSON_MAX_BYTES`
+- GGUF β†’ `MODEL_METADATA_NESTING`
+- Electron ASAR β†’ `DEFAULT_ASAR_MAX_HEADER_BYTES`
+- Electron fuses β†’ `ELECTRON_FUSE_LIMITS.maximumSentinelsPerSlice`
+
+## Install (once published)
+
+```bash
+# or from the GitHub Release tarball
+```
+
+## Compatibility
+
+- **Node.js** `^22.23.4` (primary CI / engines) and **24.x** (SQLite limits +
+ empirical probes). Node 24.22.1 verified green this release.
+- Optional tooling for full empirical coverage: **tshark**, **Wabt 1.0.42**
+ (`REA_WABT_BIN_DIRECTORY`), sibling REA tree for `verify:rea` / `redteam:rea`.
+
+## Full changelog
+
+See [CHANGELOG.md](../../CHANGELOG.md#140--2026-10-27).