pyroboreplay 2.7.0__tar.gz → 2.10.1__tar.gz

pyroboreplay-2.10.1/.github/ISSUE_TEMPLATE/bug_report.yml

@@ -0,0 +1,52 @@
+name: Bug report
+description: Report a problem with PyRoboReplay
+labels: ["bug"]
+body:
+  - type: textarea
+    id: description
+    attributes:
+      label: What happened?
+      description: Clear description of the bug.
+    validations:
+      required: true
+
+  - type: textarea
+    id: repro
+    attributes:
+      label: Steps to reproduce
+      description: Minimal steps or code to reproduce the issue.
+      placeholder: |
+        1. Run `pyroboreplay analyze mission.bag --detect-gaps`
+        2. ...
+    validations:
+      required: true
+
+  - type: textarea
+    id: expected
+    attributes:
+      label: Expected vs actual behavior
+    validations:
+      required: true
+
+  - type: input
+    id: version
+    attributes:
+      label: PyRoboReplay version
+      description: Output of `pyroboreplay --version` or `pip show pyroboreplay`
+    validations:
+      required: true
+
+  - type: input
+    id: environment
+    attributes:
+      label: Environment
+      description: OS, Rust version (`rustc --version`), Python version (`python --version`)
+      placeholder: "e.g. macOS 15, rustc 1.97.1, Python 3.11"
+    validations:
+      required: true
+
+  - type: textarea
+    id: logs
+    attributes:
+      label: Relevant logs/output
+      render: shell

pyroboreplay-2.10.1/.github/ISSUE_TEMPLATE/feature_request.yml

@@ -0,0 +1,34 @@
+name: Feature request
+description: Suggest an idea for PyRoboReplay
+labels: ["enhancement"]
+body:
+  - type: textarea
+    id: problem
+    attributes:
+      label: What problem does this solve?
+      description: What are you trying to do that PyRoboReplay doesn't support today?
+    validations:
+      required: true
+
+  - type: textarea
+    id: solution
+    attributes:
+      label: Proposed solution
+      description: What would you like to see happen? A CLI flag, a Python API addition, etc.
+    validations:
+      required: false
+
+  - type: textarea
+    id: alternatives
+    attributes:
+      label: Alternatives considered
+    validations:
+      required: false
+
+  - type: checkboxes
+    id: checked-roadmap
+    attributes:
+      label: Checklist
+      options:
+        - label: I checked ROADMAP_HONEST.md and this isn't already listed as built-but-unexposed
+          required: false

pyroboreplay-2.10.1/.github/dependabot.yml

@@ -0,0 +1,19 @@
+version: 2
+updates:
+  - package-ecosystem: "cargo"
+    directory: "/"
+    schedule:
+      interval: "weekly"
+    open-pull-requests-limit: 10
+
+  - package-ecosystem: "pip"
+    directory: "/"
+    schedule:
+      interval: "weekly"
+    open-pull-requests-limit: 10
+
+  - package-ecosystem: "github-actions"
+    directory: "/"
+    schedule:
+      interval: "weekly"
+    open-pull-requests-limit: 10

pyroboreplay-2.10.1/.github/pull_request_template.md

@@ -0,0 +1,20 @@
+## Description
+Brief summary of changes and why.
+
+## Type of change
+- [ ] Bug fix
+- [ ] New feature
+- [ ] Breaking change
+- [ ] Documentation update
+
+## Testing
+- [ ] `cargo test --lib` passes
+- [ ] `cargo fmt --check` passes
+- [ ] New code has tests (unit tests co-located with `#[cfg(test)]`, or `tests/` for integration)
+- [ ] Ran the relevant example/CLI command manually, if applicable
+
+## Related issues
+Fixes #
+
+## Notes for reviewers
+Anything that needs special attention (perf implications, known limitations, follow-up work).

{pyroboreplay-2.7.0 → pyroboreplay-2.10.1}/.github/workflows/ci.yml

@@ -26,19 +26,19 @@ jobs:
           toolchain: ${{ matrix.rust }}
 
       - name: Cache cargo registry
-        uses: actions/cache@v3
+        uses: actions/cache@v4
         with:
           path: ~/.cargo/registry
           key: ${{ runner.os }}-cargo-registry-${{ hashFiles('**/Cargo.lock') }}
 
       - name: Cache cargo index
-        uses: actions/cache@v3
+        uses: actions/cache@v4
         with:
           path: ~/.cargo/git
           key: ${{ runner.os }}-cargo-git-${{ hashFiles('**/Cargo.lock') }}
 
       - name: Cache cargo build
-        uses: actions/cache@v3
+        uses: actions/cache@v4
         with:
           path: target
           key: ${{ runner.os }}-cargo-build-target-${{ hashFiles('**/Cargo.lock') }}
@@ -74,7 +74,7 @@ jobs:
       - uses: actions/checkout@v4
 
       - name: Set up Python
-        uses: actions/setup-python@v4
+        uses: actions/setup-python@v5
         with:
           python-version: ${{ matrix.python-version }}
 
@@ -88,7 +88,7 @@ jobs:
         run: maturin build --release
 
       - name: Upload wheels
-        uses: actions/upload-artifact@v3
+        uses: actions/upload-artifact@v4
         with:
           name: wheels-${{ matrix.os }}-py${{ matrix.python-version }}
           path: target/wheels/
@@ -102,7 +102,7 @@ jobs:
       - uses: actions/checkout@v4
 
       - name: Set up Python
-        uses: actions/setup-python@v4
+        uses: actions/setup-python@v5
         with:
           python-version: '3.11'
 

{pyroboreplay-2.7.0 → pyroboreplay-2.10.1}/.github/workflows/docs.yml

@@ -33,5 +33,5 @@ jobs:
 
       - name: Validate markdown
         run: |
-          pip install markdownlint-cli
-          markdownlint README.md CLAUDE.md || true
+          npm install -g markdownlint-cli
+          markdownlint README.md docs/CLAUDE.md || true

{pyroboreplay-2.7.0 → pyroboreplay-2.10.1}/.github/workflows/release.yml

@@ -8,25 +8,24 @@ on:
 env:
   CARGO_TERM_COLOR: always
 
+permissions:
+  contents: write
+
 jobs:
   create-release:
     name: Create GitHub Release
     runs-on: ubuntu-latest
-    outputs:
-      upload_url: ${{ steps.create_release.outputs.upload_url }}
     steps:
       - uses: actions/checkout@v4
 
       - name: Create Release
-        id: create_release
-        uses: actions/create-release@v1
-        env:
-          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+        uses: softprops/action-gh-release@v2
         with:
-          tag_name: ${{ github.ref }}
-          release_name: Release ${{ github.ref }}
+          name: Release ${{ github.ref_name }}
           draft: false
           prerelease: false
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
 
   build-and-publish:
     name: Build and Publish Wheel
@@ -40,7 +39,7 @@ jobs:
       - uses: actions/checkout@v4
 
       - name: Set up Python
-        uses: actions/setup-python@v4
+        uses: actions/setup-python@v5
         with:
           python-version: ${{ matrix.python-version }}
 
@@ -54,14 +53,11 @@ jobs:
         run: maturin build --release
 
       - name: Upload Release Asset
-        uses: actions/upload-release-asset@v1
+        uses: softprops/action-gh-release@v2
+        with:
+          files: target/wheels/pyroboreplay-*.whl
         env:
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-        with:
-          upload_url: ${{ needs.create-release.outputs.upload_url }}
-          asset_path: ./target/wheels/pyroboreplay-*.whl
-          asset_name: pyroboreplay-${{ github.ref }}-${{ matrix.os }}-py${{ matrix.python-version }}.whl
-          asset_content_type: application/zip
 
       - name: Install dependencies
         run: pip install twine

{pyroboreplay-2.7.0 → pyroboreplay-2.10.1}/.github/workflows/security.yml

@@ -23,7 +23,15 @@ jobs:
         run: cargo install cargo-audit
 
       - name: Run security audit
-        run: cargo audit
+        # RUSTSEC-2026-0258 (h2), -0104/-0098/-0099 (rustls-webpki) all come
+        # from the same source: aws-smithy-http-client's hyper-0.14 compat
+        # path still pins hyper-rustls 0.24 -> rustls 0.21 -> the old h2/
+        # webpki. aws-smithy-http-client 1.4.2 is the latest published
+        # release as of this writing and still carries this; no version
+        # bump on our end resolves it. Everything else cargo-audit flagged
+        # (paste/lru/chacha20) is a warning, not an error, and already
+        # doesn't fail this step.
+        run: cargo audit --ignore RUSTSEC-2026-0258 --ignore RUSTSEC-2026-0104 --ignore RUSTSEC-2026-0098 --ignore RUSTSEC-2026-0099
 
   dependencies:
     name: Check Outdated Dependencies
@@ -57,7 +65,7 @@ jobs:
         continue-on-error: true
 
       - name: Upload coverage to Codecov
-        uses: codecov/codecov-action@v3
+        uses: codecov/codecov-action@v4
         with:
           files: ./cobertura.xml
           fail_ci_if_error: false

{pyroboreplay-2.7.0 → pyroboreplay-2.10.1}/.gitignore

@@ -34,10 +34,14 @@ env/
 
 # Rust
 target/
-Cargo.lock
+# Cargo.lock is intentionally committed: this crate ships a real binary
+# (`pyroboreplay`, src/main.rs) in addition to the library, so the lockfile
+# is kept for reproducible builds (see ROADMAP_HONEST.md technical debt notes).
 
 # Temp files
 *.tmp
 *.log
 temp/
 tmp/
+
+graphify-out/

pyroboreplay-2.10.1/.graphifyignore

@@ -0,0 +1,31 @@
+# Graphify ignore file - https://docs.graphify.com/reference/configuration
+# Keep the scan (and therefore the agent's graph) focused on real source.
+.git/
+.github/
+graphify-out/
+
+# Build output / artifacts
+target/
+dist/
+build/
+*.egg-info/
+node_modules/
+.venv/
+venv/
+env/
+
+# Caches
+__pycache__/
+*.pyc
+.pytest_cache/
+.mypy_cache/
+.ruff_cache/
+.tox/
+.nox/
+.coverage
+htmlcov/
+
+# Vendored / generated
+*.min.js
+*.min.css
+*.lock

pyroboreplay-2.10.1/CHANGELOG.md

@@ -0,0 +1,150 @@
+# Changelog
+
+All notable changes to this project are documented here. Format follows
+[Keep a Changelog](https://keepachangelog.com/en/1.1.0/).
+
+This file was started 2026-09-20, during an OSS-hygiene pass. It is not
+backfilled with invented entries for prior releases — that history is real
+but wasn't written down in this format as it happened, and reconstructing it
+now from commit messages risks getting dates/scope wrong. For the actual
+history of prior versions (v0.1 through v2.10.0), see `git log` and
+`docs/archive/` (old release notes, phase-completion reports, etc.). Going
+forward, new changes should be added here under `[Unreleased]` and moved to a
+dated section when released.
+
+## [2.10.1] - 2026-10-12
+
+### Fixed
+- CI is green again: `cargo clippy --all-targets --all-features -- -D warnings`
+  and `cargo fmt --check` now pass. Cleared all 47 pre-existing lib warnings
+  and the denials in tests/examples — unused/dead fields now carry explicit
+  `#[allow(dead_code)]` (intentional storage for future use), logic lints were
+  genuinely fixed (collapsed redundant `if`/`else if` branches in
+  `core/evidence_discovery.rs` and `phase17/counterfactual.rs`, replaced
+  `sort_by` closures with `sort_by_key`, `vec![..]` instead of
+  init-then-push, `matches!`, `checked_div`, iterator loops,
+  `format!`-in-`format!`, `Default` impl for `CausalGraph`, `&mut [_]`
+  over `&mut Vec`), and meaningless always-true assertions (`assert!(true)`,
+  `len() >= 0`, `u8 >= 0`) in tests were removed.
+- `PYRAMID`/`PI`/`TAU` literals in tests/examples now use
+  `std::f32::consts::{PI,TAU}`.
+
+### Changed
+- Added an optional, isolated Graphify code knowledge-graph backend (`tools/graphify/`, `.graphifyignore`, optional workflow, README badge).
+
+## [Unreleased]
+
+### Fixed
+- **CRITICAL: the ROS2 adapter never read real message content, for any
+  sensor type** (found 2026-09-27, fixed 2026-09-29). Every parser in
+  `src/adapters/ros2.rs` (`parse_lidar_message`, `parse_camera_message`,
+  `parse_imu_message`, `parse_odometry_message`, `parse_pose_message`) took
+  an unused `_msg: &RosMessage` and returned a hardcoded constant event
+  regardless of the message's real CDR-encoded bytes. Added
+  `src/adapters/cdr.rs`, a real CDR (Common Data Representation) decoder —
+  the real OMG CDR encapsulation header, real little-endian primitive
+  decoding, and the real alignment rules the format requires — and rewired
+  all 5 parsers to decode the actual standard `sensor_msgs`/`nav_msgs`/
+  `geometry_msgs` binary layouts (`LaserScan`, `Image`, `Imu`, `Odometry`,
+  `PoseWithCovarianceStamped`). `parse_pose_message`'s `confidence` is now
+  derived from the message's real position-covariance trace instead of a
+  hardcoded `0.95`, so `detect_localization_loss`'s `confidence < 0.5` check
+  can actually fire on real data — verified against a real 901-message
+  benchmark bag with an injected covariance spike: 81/81 real
+  localization-loss frames now correctly detected (previously 0/81). Added
+  `tests/test_ros2_cdr_decoding.rs` (7 tests) against a real,
+  independently-generated fixture (`tests/fixtures/ros2_cdr_fixture.db3`,
+  built with the third-party `rosbags` Python library) as a permanent
+  regression test. Full detail in `ROADMAP_HONEST.md` and README's "vs
+  Rerun" section.
+- `src/lib.rs:504` — `Hypothesis`'s `#[pyclass]` relied on PyO3's deprecated
+  automatic `FromPyObject` derive for `Clone` types; migrated to the explicit
+  opt-in `#[pyclass(from_py_object)]` (current recommended pattern for pyo3
+  0.29, matching the pinned version in `Cargo.toml`). Preserves existing
+  behavior; verified the deprecation warning is gone from `cargo build --lib`
+  and `cargo clippy --all-targets --all-features`, and `cargo test --lib`
+  still passes (834/834).
+- 22 clippy `manual_clamp` findings across `src/analyzers/`, `src/cli/`,
+  `src/core/`, `src/intelligence/`, `src/phase19/`, and `src/streaming/`
+  (e.g. `src/analyzers/scoring.rs:91,108,125,144`,
+  `src/analyzers/adaptive_recalibration.rs:121,162,204,260,266`) — replaced
+  manual `.max(a).min(b)` / `.min(b).max(a)` chains with `.clamp(a, b)`, using
+  clippy's own machine-generated replacement suggestions.
+- 9 clippy `approx_constant` findings (imprecise `PI`/`TAU` float literals:
+  `3.14`, `-3.14`, `6.28`) in test fixtures across `src/core/event.rs:392-393`,
+  `src/core/timeline.rs:345-346,360-361,390-391`, `src/cli/causal_viz.rs:351`,
+  and `tests/test_python_api_integration.rs` — replaced with
+  `std::f32::consts::PI` / `std::f32::consts::TAU`.
+- 3 clippy findings for `drop()` called on a `&mut` reference (a no-op) in
+  `src/analyzers/robot_calibration.rs:339,358,375` — replaced with
+  `let _ = profile;` per clippy's suggested fix.
+- `.github/workflows/release.yml` used the archived/deprecated
+  `actions/create-release@v1` and `actions/upload-release-asset@v1`; replaced
+  both with `softprops/action-gh-release@v2` (used once to create the release,
+  once per build matrix leg to attach wheel assets) and added an explicit
+  `permissions: contents: write` block. Validated with `actionlint` (clean);
+  not exercised against a real tag push (no network/GitHub access in this
+  environment).
+- `pyproject.toml`'s `[tool.maturin.sdist]` `include` list referenced a
+  top-level `CLAUDE.md` that doesn't exist (the real file is at
+  `docs/CLAUDE.md`); corrected the path.
+- `.github/workflows/docs.yml`'s `readme` job ran `markdownlint README.md
+  CLAUDE.md` against a nonexistent path; corrected to `docs/CLAUDE.md`.
+- Outdated GitHub Actions versions flagged by `actionlint`: `actions/cache@v3`
+  to `@v4`, `actions/setup-python@v4` to `@v5`, `codecov/codecov-action@v3`
+  to `@v4`.
+- `Cargo.lock` was gitignored despite this crate shipping a real binary
+  (`pyroboreplay` CLI); now committed for reproducible builds.
+- Removed stale `git.example.com` placeholder URLs from `CONTRIBUTING.md`,
+  `docs/GITHUB_SETTINGS.md`, and `docs/QUICKSTART.md`, replaced with the real
+  GitHub repo URL.
+- `CONTRIBUTING.md` referenced a root-level `CLAUDE.md` and `CODE_OF_CONDUCT.md`
+  that lived at different paths (or, for the latter, under `docs/`); fixed
+  links and moved `docs/CODE_OF_CONDUCT.md` to the repository root (the
+  conventional location).
+- README version references (`2.9.2` in badges/text) were out of sync with
+  `Cargo.toml`/`pyproject.toml` (`2.10.0`); updated, and the pinned
+  `pip install pyroboreplay==2.9.2` install command was changed to an
+  unpinned `pip install pyroboreplay` since this pass could not verify which
+  version is actually live on PyPI (no network access in this environment).
+
+### Changed
+- `CONTRIBUTING.md`'s "Areas We're Looking For Help" and "Roadmap" sections
+  contained a stale, fabricated-sounding quarterly roadmap (Q4 2026 / 2027
+  dates) that pre-dated the actual v2.10.0 codebase and listed already-shipped
+  work (Postgres/S3/BigQuery backends) as still-needed. Replaced with a
+  pointer to `ROADMAP_HONEST.md`.
+- Renamed `ROADMAP.md` to `ROADMAP_HONEST.md` and added a "Technical debt"
+  section with concrete `file:line` findings (see that file).
+- Moved 19 stale phase/status/strategy/testing snapshot docs (from both the
+  repo root and `docs/`) into `docs/archive/` with an index explaining why
+  each was archived, rather than deleting them.
+- Consolidated three overlapping stats-dashboard docs into one canonical
+  `docs/STATS_DASHBOARD.md` (kept current; the flag it documents,
+  `--stats-dashboard`, is real and verified against `src/cli/args.rs`).
+
+### Removed
+- `pyroboreplay/scripts/__init__.py.bak` — an empty, tracked backup file with
+  no purpose.
+
+## Known issues as of this pass
+
+See `ROADMAP_HONEST.md` for the full, current list. Highlights:
+- The MCP tool integration (`pyroboreplay/_mcp_tools.py`, `_mcp_connector.py`)
+  is unshippable dead code — it lives outside the directory maturin actually
+  packages, so it's not importable from an installed wheel, despite
+  `pyroboreplay.toml` claiming all 13 MCP tools are enabled. Not addressed in
+  this pass (needs a real wire-up-or-delete decision).
+- `cargo clippy --all-targets --all-features -- -D warnings` now fails with 61
+  errors (down from 96 — the mechanical `manual_clamp`, `approx_constant`, and
+  no-op-`drop` categories were fixed in this pass). The remainder is 3
+  `>7-arg` function signatures and 15+ dead struct fields/methods that need a
+  real refactor-or-delete decision, plus a handful of smaller style lints, none
+  touched in this pass.
+- `459` `.unwrap()` calls in `src/` (~208 estimated outside test modules) —
+  not audited in this pass, too large a surface for a quick-fix pass.
+- `src/adapters/ros2.rs` — every `parse_*_message` helper (lidar, camera, IMU,
+  odometry, pose) ignores the actual message payload bytes (`msg.data`) and
+  returns hardcoded zero/empty values; real per-topic CDR deserialization is
+  unimplemented. Checked in this pass and confirmed to be real feature work,
+  not a quick fix — left untouched.

{pyroboreplay-2.7.0 → pyroboreplay-2.10.1}/CONTRIBUTING.md

@@ -6,7 +6,7 @@ Thanks for your interest in contributing! We welcome contributions of all kinds.
 
 ### Report Bugs 🐛
 
-Found a bug? [Open an issue](https://git.example.com/user/pyroboreplay/issues) with:
+Found a bug? [Open an issue](https://github.com/Mullassery/pyroboreplay/issues) with:
 - Clear title: "Bug: [component] description"
 - Steps to reproduce
 - Expected vs actual behavior
@@ -15,7 +15,7 @@ Found a bug? [Open an issue](https://git.example.com/user/pyroboreplay/issues) w
 
 ### Suggest Features 💡
 
-Have an idea? Start a [discussion](https://git.example.com/user/pyroboreplay/discussions) or [issue](https://git.example.com/user/pyroboreplay/issues) with:
+Have an idea? Start a [discussion](https://github.com/Mullassery/pyroboreplay/discussions) or [issue](https://github.com/Mullassery/pyroboreplay/issues) with:
 - Use case: why would this be useful?
 - Proposed solution (if you have one)
 - Alternative approaches you've considered
@@ -27,7 +27,7 @@ Have an idea? Start a [discussion](https://git.example.com/user/pyroboreplay/dis
 
 ```bash
 # Clone repo
-git clone https://git.example.com/user/pyroboreplay.git
+git clone https://github.com/Mullassery/pyroboreplay.git
 cd pyroboreplay
 
 # Install Rust (if needed)
@@ -166,23 +166,20 @@ None / Describe any perf implications
 
 ## Areas We're Looking For Help
 
-### High Priority
-- **Performance:** Optimize large mission analysis (1M+ events)
-- **Storage:** Add PostgreSQL, BigQuery adapters
-- **Streaming:** Real-time event ingestion from live robots
-- **Testing:** Integration tests for complex scenarios
-- **Documentation:** Tutorials, blog posts, video demos
+See [ROADMAP_HONEST.md](ROADMAP_HONEST.md) for the current, code-verified list of
+what's built, what's partial, and what's missing. As of this writing, the
+highest-leverage gap is CLI/Python exposure for Phases 12-20 (the analysis
+logic already exists in the Rust core with unit tests; it just isn't wired up
+to `src/cli/` or `src/pyroboreplay/__init__.py` yet). Note: Postgres, S3, and
+BigQuery storage backends already exist with dedicated integration test
+suites — that work is done, not needed.
 
-### Medium Priority
-- **CLI:** New commands (e.g., `export-video`, `batch-analyze`)
-- **Visualization:** Web dashboard for fleet monitoring
-- **Analysis:** Failure prediction ML models
-- **Compliance:** Additional regulatory standards (e.g., ISO 13849-1)
+### Good First Issues
 
 ### Good First Issues
-- Look for [good-first-issue](https://git.example.com/user/pyroboreplay/labels/good-first-issue) label
+- Look for [good-first-issue](https://github.com/Mullassery/pyroboreplay/labels/good-first-issue) label
 - Start with documentation or small bug fixes
-- Ask questions in [discussions](https://git.example.com/user/pyroboreplay/discussions) if stuck
+- Ask questions in [discussions](https://github.com/Mullassery/pyroboreplay/discussions) if stuck
 
 ---
 
@@ -215,12 +212,12 @@ rust-gdb --args target/debug/my_binary
 # Create feature branch
 git checkout -b feat/my-feature
 
-# Keep updated with main
+# Keep updated with master (the default branch)
 git fetch origin
-git rebase origin/main
+git rebase origin/master
 
 # Before pushing, squash if needed
-git rebase -i origin/main
+git rebase -i origin/master
 
 # Push and open PR
 git push origin feat/my-feature
@@ -233,31 +230,16 @@ Workflows run automatically on push/PR:
 - **security.yml**: Vulnerability scanning, coverage
 - **release.yml**: Auto-publish on version tags
 
-Check status in [Actions](https://git.example.com/user/pyroboreplay/actions).
+Check status in [Actions](https://github.com/Mullassery/pyroboreplay/actions).
 
 ---
 
 ## Architecture & Design
 
-- **[CLAUDE.md](CLAUDE.md)** — Product vision, principles, long-term roadmap
+- **[docs/CLAUDE.md](docs/CLAUDE.md)** — Product vision, principles
+- **[docs/ARCHITECTURE.md](docs/ARCHITECTURE.md)** — System architecture
 - **[.github/CI_SETUP.md](.github/CI_SETUP.md)** — CI/CD architecture
-- **[Roadmap](#-roadmap)** below
-
-### Roadmap
-
-**v0.9** (Q4 2026): AI-Driven Remediation
-- Automated fix suggestions
-- Reinforcement learning for strategy optimization
-
-**v1.0** (Q4 2026): Production Scale
-- Distributed analysis across multiple machines
-- Enterprise observability integrations
-- Advanced security audit trails
-
-**v1.1+** (2027): Autonomous Systems
-- Fleet coordination layer
-- Real-time mission optimization
-- Cross-mission knowledge graphs
+- **[ROADMAP_HONEST.md](ROADMAP_HONEST.md)** — What's actually built, partial, or missing (no fabricated timelines)
 
 ---
 
@@ -274,9 +256,9 @@ Check status in [Actions](https://git.example.com/user/pyroboreplay/actions).
 
 ## Getting Help
 
-- **Questions?** Ask in [GitHub Discussions](https://git.example.com/user/pyroboreplay/discussions)
+- **Questions?** Ask in [GitHub Discussions](https://github.com/Mullassery/pyroboreplay/discussions)
 - **Stuck?** Open an issue and label it `help-wanted`
-- **Chat?** Connect via GitHub issues/discussions (we respond within 24h)
+- **Chat?** Connect via GitHub issues/discussions. This is currently maintained by one person in their spare time — there is no guaranteed response time.
 
 ---