Prerelease cleanup (#46)

* feat: Add const_bound_vars tracking to prevent false positives in ownership checks

* feat: Introduce field interner and typed bounded vars for enhanced type tracking

* feat: Add typed_call_receivers and typed_bounded_dto_fields for enhanced type tracking

* feat: Centralize method name extraction with bare_method_name helper

* feat: Implement Phase-6 hierarchy fan-out for runtime virtual dispatch

* feat: Enhance C++ taint tracking with additional container operations and inline method resolution

* feat: Introduce field-sensitive points-to analysis for enhanced resource tracking

* feat: Implement Pointer-Phase 6 subscript handling for enhanced container analysis

* test: Add comprehensive tests for JavaScript control flow constructs and lattice operations

* docs: Update advanced analysis documentation with field-sensitive points-to and hierarchy fan-out details

* test: Add comprehensive tests for lattice algebra laws and SSA edge cases

* feat: Add destructured session user handling and safe user ID access patterns

* feat: Implement row-population reverse-walk for enhanced authorization checks

* feat: Enhance authorization checks with local alias chain for self-actor types

* feat: Introduce ActiveRecord query safety checks and enhance snippet extraction

* feat: Implement chained method call inner-gate rebinding for SSRF prevention

* feat: Add observability and error modules, enhance debug functionality, and implement theme context

* feat: Remove Auth Analysis page and update navigation to redirect to Explorer

* feat: Optimize SSA lowering by sharing results between taint engine and artifact extractor

* feat: Optimize SSA lowering by sharing results between taint engine and artifact extractor

* feat: Reset path-safe-suppressed spans before lowering to maintain analysis integrity

* fix(ssa): ungate debug_assert_bfs_ordering for release-tests build

The helper at src/ssa/lower.rs was gated `#[cfg(debug_assertions)]` while
the unit test at the bottom of the file was gated only `#[cfg(test)]`.
Since `cfg(test)` is set in release builds with `--tests` but
`cfg(debug_assertions)` is not, `cargo build --release --tests` failed
with E0425. Removing the gate fixes the build; the body is `debug_assert!`
only, so the helper is free in release. Also drop the gate at the call
site to avoid a `dead_code` warning when the lib is built without
`--tests`.

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

* test(closure-capture): flip JS/TS fixtures to required-finding

The JS and TS closure-capture fixtures pinned the old broken behaviour
via `forbidden_findings: [{ "id_prefix": "taint-" }]`. The engine now
correctly traces taint through the closure boundary (env source captured
by an arrow function, sunk via `child_process.exec` inside the body), so
the formerly-forbidden finding is a true positive.

Match the Python sibling's shape — `required_findings` with
`id_prefix` + `min_count` plus a small `noise_budget` — and rewrite the
companion READMEs and the phase8_fragility_tests doc-comments from
"known gap" to "regression guard".

Verified:
- cargo test --release --test phase8_fragility_tests → 8/8 pass
- cargo test --release --lib bfs_assertion → pass
- corpus benchmark F1 = 0.9976 (TP=205, FP=1, FN=0) — unchanged

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

* feat: Add OWASP mapping and baseline mutation hooks for enhanced security analysis

* feat: Introduce health module and enhance health score computation with calibration tests

* feat: Add expectations configuration and cleanup .gitignore for log files

* feat: Implement theme selection and enhance settings panel for triage sync

* feat: Suppress false positives for strcpy calls with literal sources in AST

* feat: Update analyse_function_ssa to return body CFG for accurate analysis

* feat: Add bug report and feature request templates for improved issue tracking

* feat: removed dev scripts

* feat: update README.md for clarity and consistency in fixture descriptions

* feat: removed dev docs

* feat: clean up error handling and UI elements for improved user experience

* feat: adjust button sizes in HeaderBar for better UI consistency

* feat: enhance taint analysis with additional context for sanitizer and taint findings

* cargo fmt

* prettier

* refactor: simplify conditional checks and improve code readability in AST and screenshot capture scripts

* feat: add script to frame PNG screenshots with brand gradient

* feat: add fuzzing support with new targets and CI workflows

* refactor: streamline match expressions and improve formatting in CLI and output handling

* feat: enhance configuration display with detailed output options

* feat: stage demo configuration for improved CLI screenshot output

* feat: expose merge_configs function for user-configurable settings

* refactor: simplify code structure and improve readability in config handling

* refactor: improve descriptions for vulnerability patterns in various languages

* feat: update MIT License section with additional usage details and copyright information

* feat: update screenshots

* refactor: update build process and paths for frontend assets

* feat: add cross-file taint fuzzing target and supporting dictionary

* refactor: clean up formatting and comments in fuzz configuration and example files

* refactor: remove outdated comments and clean up CI configuration files

* chore: update changelog dates and improve formatting in documentation

* refactor: update Cargo.toml and CI configuration for improved packaging and build process

* refactor: enhance quote-stripping logic to prevent panics and add regression tests

---------

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

tests/benchmark/corpus/java/safe/SafeJpaParameterizedExecute.java

@@ -0,0 +1,40 @@
+import javax.persistence.EntityManager;
+import java.util.List;
+
+// Distilled from keycloak's
+// `model/jpa/src/main/java/org/keycloak/events/jpa/JpaEventStoreProvider.java`:
+// `em.createQuery(LITERAL).executeUpdate()` and the bind-parameter chain
+// `em.createQuery(LITERAL).setParameter(...).executeUpdate()` are the
+// canonical JPA parameterised-execute shapes.  The terminal zero-arg
+// `executeUpdate` / `executeQuery` is not where SQL is built — the SQL
+// was bound upstream from a string literal, and any per-call values
+// arrive through `setParameter`, which the JPA driver escapes.  Engine
+// must synthesise a same-node `Sanitizer(SQL_QUERY)` so neither
+// `cfg-unguarded-sink` nor `taint-unsanitised-flow` fires.
+public class SafeJpaParameterizedExecute {
+    private final EntityManager em;
+
+    public SafeJpaParameterizedExecute(EntityManager em) {
+        this.em = em;
+    }
+
+    public void clearAll() {
+        em.createQuery("delete from EventEntity").executeUpdate();
+    }
+
+    public void clearOlder(long olderThan) {
+        em.createQuery("delete from EventEntity where time < :time")
+          .setParameter("time", olderThan)
+          .executeUpdate();
+    }
+
+    public List<?> listAll() {
+        return em.createQuery("select e from EventEntity e").getResultList();
+    }
+
+    public void clearByRealm(String realmId) {
+        em.createNativeQuery("delete from event_entity where realm_id = ?")
+          .setParameter(1, realmId)
+          .executeUpdate();
+    }
+}

tests/benchmark/corpus/java/safe/SafeLoggerIsEnabled.java

@@ -0,0 +1,34 @@
+// `cfg-error-fallthrough` previously fired on
+// `if (logger.isErrorEnabled()) { print(...) } more_code()`
+// because the condition_vars contained `isErrorEnabled` and the
+// rule's `lower.contains("err")` heuristic matched it as an error
+// identifier.  Spring's SpringApplication.java:854 has this exact
+// shape — a logging-enabled gate, not an error check.
+//
+// The fix (`is_error_var_ident`) restricts the err identifier to
+// `err` / `error` (case-insensitive) or snake-case `err_*` / `*_err`
+// / `error_*` / `*_error` — camelCase method names like
+// `isErrorEnabled` / `getError` no longer trigger the rule.
+public class SafeLoggerIsEnabled {
+
+    interface Logger {
+        boolean isErrorEnabled();
+    }
+
+    private final Logger logger;
+
+    public SafeLoggerIsEnabled(Logger logger) {
+        this.logger = logger;
+    }
+
+    public void run(String failure) {
+        if (logger.isErrorEnabled()) {
+            System.out.println("Application run failed: " + failure);
+        }
+        registerLoggedException(failure);
+    }
+
+    private void registerLoggedException(String failure) {
+        // sink that runs unconditionally after the if
+    }
+}

tests/benchmark/corpus/java/sqli/SqliJpaCreateQueryConcat.java

@@ -0,0 +1,20 @@
+import javax.persistence.EntityManager;
+
+// Vulnerable counterpart to SafeJpaParameterizedExecute.  When the SQL
+// passed to `createQuery` is built by string concatenation, the same
+// `.executeUpdate()` chain shape is no longer parameterised — the
+// receiver-chain walk sees a `binary_expression` at arg 0 of
+// `createQuery`, not a `string_literal`, and refuses to synthesise the
+// reflexive `Sanitizer(SQL_QUERY)`.  The structural sink stays in place
+// and a finding is expected.
+public class SqliJpaCreateQueryConcat {
+    private final EntityManager em;
+
+    public SqliJpaCreateQueryConcat(EntityManager em) {
+        this.em = em;
+    }
+
+    public void clearByName(String name) {
+        em.createQuery("delete from EventEntity where name = '" + name + "'").executeUpdate();
+    }
+}