echolot 0.1.0__tar.gz

echolot-0.1.0/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

echolot-0.1.0/PKG-INFO

@@ -0,0 +1,183 @@
+Metadata-Version: 2.4
+Name: echolot
+Version: 0.1.0
+Summary: A deterministic layer between Perfetto traces and AI agents
+Author-email: Andrey Grishanov <grishanov.dev@gmail.com>
+License-Expression: Apache-2.0
+Project-URL: Homepage, https://github.com/grishan0v/echolot
+Project-URL: Documentation, https://github.com/grishan0v/echolot/tree/main/docs
+Project-URL: Repository, https://github.com/grishan0v/echolot
+Project-URL: Issues, https://github.com/grishan0v/echolot/issues
+Keywords: perfetto,android,performance,tracing,profiling,ai-agents,claude-code
+Classifier: Development Status :: 3 - Alpha
+Classifier: Environment :: Console
+Classifier: Intended Audience :: Developers
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Programming Language :: Python :: 3.14
+Classifier: Topic :: Software Development :: Debuggers
+Classifier: Topic :: System :: Monitoring
+Requires-Python: >=3.10
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: perfetto==0.57.2
+Requires-Dist: PyYAML>=6.0
+Dynamic: license-file
+
+
+<img width="2560" height="904" alt="echolot-hero" src="https://github.com/user-attachments/assets/c5640665-d1ae-41ac-8da9-669434ce51ac" />
+
+## Install
+
+```bash
+pipx install echolot
+```
+
+## First time
+
+```bash
+cd ~/my-app
+//open your agent
+/echolot init
+```
+
+That installs the `.claude/` layer — the skill, the `perf-hunter` agent, the
+commands — checks that this machine computes correctly, and ends with the next
+step. Then open Claude Code in the project and type `/echolot`. That is the
+one door: it asks the tool where the project stands and takes the next step
+itself — the first time, that is building `echolot.yml` from the repository
+and a probe trace (four questions to you along the way); every time after,
+finding the cause of the regression you describe.
+
+```
+/echolot                              # reads the state, does what is next
+/echolot why is cold start slow       # hunt, with that as the question
+/echolot init · setup · hunt · reflect · doctor   # that thing, explicitly
+```
+
+## Coming back
+
+```bash
+echolot
+```
+
+Where things stand — layer, config, traces, last report, last `doctor` — and
+one line saying what to do next; usually `/echolot`. After updating the
+package, run `echolot init` again: it brings the layer up to date and leaves
+the files you edited alone.
+
+Without an agent, or in CI:
+
+```bash
+echolot collect -c echolot.yml -n 5                              # 5 repeats of the scenario
+echolot analyze .echolot/traces/*.perfetto-trace -c echolot.yml  # the report
+echolot doctor -q                                                # exit 0/1: does this environment compute correctly?
+```
+
+The output is `.echolot/out/report.md` for humans and `report.json` for the
+agent. `doctor` builds a synthetic trace with problems planted in advance and
+checks the answers against them — no device, about a second — good both as a
+CI gate and as the agent's first move.
+
+## What it looks for
+
+| detector | what it catches |
+|---|---|
+| `main_thread_block` | where the main thread spent its time (by self time) |
+| `gc_pressure` | frequent or expensive GC, and waits on allocation |
+| `monitor_contention` | monitor contention, with the owner's tid as evidence |
+| `binder_txn` | long synchronous IPC, and death by a thousand cuts |
+| `runnable_starvation` | thread ready but preempted on CPU |
+| `uninstrumented_cpu` | **threads burning CPU with no instrumentation** |
+
+The last one is the only detector that finds a problem inside uninstrumented
+code. It does not guess; it presents a fact: "thread
+`DefaultDispatcher-worker-2` was Running for 340 ms, zero slices". That is
+where to add `trace{}` and re-record.
+
+Each detector is one self-contained `.sql` file with its metadata in the
+header. Drop a file into `echolot/sql/detectors/` and it is picked up — there
+is no registration in code.
+
+## The commands
+
+Two are yours to remember — `init` and `echolot` with nothing after it. The
+rest split by who calls them.
+
+**You**
+
+```
+echolot     where this project stands, and the next step
+init        install or update the .claude/ layer; checks the environment
+analyze     run the detectors, build a Marker Report — CI, or traces by hand
+collect     capture N traces of one scenario: launch | command | gradle
+doctor      environment + self-check on a synthetic trace + is the layer current; exit 0/1, -q for three lines
+```
+
+**The agent**, behind `/echolot` — you do not call
+these:
+
+```
+probe       processes, threads by CPU, scenario anchor candidates
+names       slice name inventory and detector mask coverage
+domains     slice-to-code map and instrumentation coverage
+mark        the first temporary markers for a project with none — from the manifest and the SDK, not from names; --apply / --remove
+calibrate   thresholds derived from known-healthy runs
+explain     list the detectors and their parameters
+```
+
+**Improving the tool**
+
+```
+reflect     the same kind of report over an agent session — how the tool was used, where it got in the way
+```
+
+## Where things live
+
+```
+android-project/
+├── echolot.yml       ← the project half, committed
+├── local.yml         ← device serials, binary path; in .gitignore
+└── .echolot/         ← traces, reports, the run log, reflect reports; in .gitignore
+```
+
+Read it like `gradle.properties` and `local.properties`: one tool per machine,
+the binding to a project inside that project's repository.
+
+## Documentation
+
+| document | about |
+|---|---|
+| [docs/collecting.md](https://github.com/grishan0v/echolot/blob/main/docs/collecting.md) | `collect`, the three modes, merging repeats |
+| [docs/analysing.md](https://github.com/grishan0v/echolot/blob/main/docs/analysing.md) | `probe`, `names`, `domains` — from a trace to a place in the code |
+| [docs/mark.md](https://github.com/grishan0v/echolot/blob/main/docs/mark.md) | `mark` — the first markers for a project with no instrumentation, from the platform's vocabulary |
+| [docs/detectors.md](https://github.com/grishan0v/echolot/blob/main/docs/detectors.md) | writing your own, the context views, self time versus total |
+| [docs/calibrate.md](https://github.com/grishan0v/echolot/blob/main/docs/calibrate.md) | thresholds from healthy runs, why rank beats percentile |
+| [docs/determinism.md](https://github.com/grishan0v/echolot/blob/main/docs/determinism.md) | the pinned trace_processor, `doctor`, the self-check |
+| [docs/agent-layer.md](https://github.com/grishan0v/echolot/blob/main/docs/agent-layer.md) | the `.claude/` layer and why the loop lives in a subagent |
+| [docs/reflect.md](https://github.com/grishan0v/echolot/blob/main/docs/reflect.md) | `reflect` — the report over the agent's session, for improving the tool |
+
+The agent-facing reference material ships inside the package, under
+`echolot/claude/skills/echolot/references/` — the report schema, the config
+schema, how ART names things, and how to capture a trace by hand.
+
+## Status
+
+v0. Everything planned for it is in place except CI mode.
+
+The detectors were validated on a synthetic trace (46 checks in `doctor`) and
+on live traces from Android 14 (emulator) and Android 13 (Galaxy A51). The
+naming masks for GC, locks and binder were narrowed against those real traces,
+and every narrowing is pinned by a check.
+
+**Not done: CI mode.** `scenario.budget_ms` is declared in the config but not
+read by the code. What is needed is `analyze` with an exit code — either
+against the budget or on "any detector fired", which after `calibrate` amounts
+to a comparison against the baseline.
+
+A failed detector never fails the run — the error goes to stderr and into
+`report.json`.

echolot-0.1.0/README.md

@@ -0,0 +1,153 @@
+
+<img width="2560" height="904" alt="echolot-hero" src="https://github.com/user-attachments/assets/c5640665-d1ae-41ac-8da9-669434ce51ac" />
+
+## Install
+
+```bash
+pipx install echolot
+```
+
+## First time
+
+```bash
+cd ~/my-app
+//open your agent
+/echolot init
+```
+
+That installs the `.claude/` layer — the skill, the `perf-hunter` agent, the
+commands — checks that this machine computes correctly, and ends with the next
+step. Then open Claude Code in the project and type `/echolot`. That is the
+one door: it asks the tool where the project stands and takes the next step
+itself — the first time, that is building `echolot.yml` from the repository
+and a probe trace (four questions to you along the way); every time after,
+finding the cause of the regression you describe.
+
+```
+/echolot                              # reads the state, does what is next
+/echolot why is cold start slow       # hunt, with that as the question
+/echolot init · setup · hunt · reflect · doctor   # that thing, explicitly
+```
+
+## Coming back
+
+```bash
+echolot
+```
+
+Where things stand — layer, config, traces, last report, last `doctor` — and
+one line saying what to do next; usually `/echolot`. After updating the
+package, run `echolot init` again: it brings the layer up to date and leaves
+the files you edited alone.
+
+Without an agent, or in CI:
+
+```bash
+echolot collect -c echolot.yml -n 5                              # 5 repeats of the scenario
+echolot analyze .echolot/traces/*.perfetto-trace -c echolot.yml  # the report
+echolot doctor -q                                                # exit 0/1: does this environment compute correctly?
+```
+
+The output is `.echolot/out/report.md` for humans and `report.json` for the
+agent. `doctor` builds a synthetic trace with problems planted in advance and
+checks the answers against them — no device, about a second — good both as a
+CI gate and as the agent's first move.
+
+## What it looks for
+
+| detector | what it catches |
+|---|---|
+| `main_thread_block` | where the main thread spent its time (by self time) |
+| `gc_pressure` | frequent or expensive GC, and waits on allocation |
+| `monitor_contention` | monitor contention, with the owner's tid as evidence |
+| `binder_txn` | long synchronous IPC, and death by a thousand cuts |
+| `runnable_starvation` | thread ready but preempted on CPU |
+| `uninstrumented_cpu` | **threads burning CPU with no instrumentation** |
+
+The last one is the only detector that finds a problem inside uninstrumented
+code. It does not guess; it presents a fact: "thread
+`DefaultDispatcher-worker-2` was Running for 340 ms, zero slices". That is
+where to add `trace{}` and re-record.
+
+Each detector is one self-contained `.sql` file with its metadata in the
+header. Drop a file into `echolot/sql/detectors/` and it is picked up — there
+is no registration in code.
+
+## The commands
+
+Two are yours to remember — `init` and `echolot` with nothing after it. The
+rest split by who calls them.
+
+**You**
+
+```
+echolot     where this project stands, and the next step
+init        install or update the .claude/ layer; checks the environment
+analyze     run the detectors, build a Marker Report — CI, or traces by hand
+collect     capture N traces of one scenario: launch | command | gradle
+doctor      environment + self-check on a synthetic trace + is the layer current; exit 0/1, -q for three lines
+```
+
+**The agent**, behind `/echolot` — you do not call
+these:
+
+```
+probe       processes, threads by CPU, scenario anchor candidates
+names       slice name inventory and detector mask coverage
+domains     slice-to-code map and instrumentation coverage
+mark        the first temporary markers for a project with none — from the manifest and the SDK, not from names; --apply / --remove
+calibrate   thresholds derived from known-healthy runs
+explain     list the detectors and their parameters
+```
+
+**Improving the tool**
+
+```
+reflect     the same kind of report over an agent session — how the tool was used, where it got in the way
+```
+
+## Where things live
+
+```
+android-project/
+├── echolot.yml       ← the project half, committed
+├── local.yml         ← device serials, binary path; in .gitignore
+└── .echolot/         ← traces, reports, the run log, reflect reports; in .gitignore
+```
+
+Read it like `gradle.properties` and `local.properties`: one tool per machine,
+the binding to a project inside that project's repository.
+
+## Documentation
+
+| document | about |
+|---|---|
+| [docs/collecting.md](https://github.com/grishan0v/echolot/blob/main/docs/collecting.md) | `collect`, the three modes, merging repeats |
+| [docs/analysing.md](https://github.com/grishan0v/echolot/blob/main/docs/analysing.md) | `probe`, `names`, `domains` — from a trace to a place in the code |
+| [docs/mark.md](https://github.com/grishan0v/echolot/blob/main/docs/mark.md) | `mark` — the first markers for a project with no instrumentation, from the platform's vocabulary |
+| [docs/detectors.md](https://github.com/grishan0v/echolot/blob/main/docs/detectors.md) | writing your own, the context views, self time versus total |
+| [docs/calibrate.md](https://github.com/grishan0v/echolot/blob/main/docs/calibrate.md) | thresholds from healthy runs, why rank beats percentile |
+| [docs/determinism.md](https://github.com/grishan0v/echolot/blob/main/docs/determinism.md) | the pinned trace_processor, `doctor`, the self-check |
+| [docs/agent-layer.md](https://github.com/grishan0v/echolot/blob/main/docs/agent-layer.md) | the `.claude/` layer and why the loop lives in a subagent |
+| [docs/reflect.md](https://github.com/grishan0v/echolot/blob/main/docs/reflect.md) | `reflect` — the report over the agent's session, for improving the tool |
+
+The agent-facing reference material ships inside the package, under
+`echolot/claude/skills/echolot/references/` — the report schema, the config
+schema, how ART names things, and how to capture a trace by hand.
+
+## Status
+
+v0. Everything planned for it is in place except CI mode.
+
+The detectors were validated on a synthetic trace (46 checks in `doctor`) and
+on live traces from Android 14 (emulator) and Android 13 (Galaxy A51). The
+naming masks for GC, locks and binder were narrowed against those real traces,
+and every narrowing is pinned by a check.
+
+**Not done: CI mode.** `scenario.budget_ms` is declared in the config but not
+read by the code. What is needed is `analyze` with an exit code — either
+against the budget or on "any detector fired", which after `calibrate` amounts
+to a comparison against the baseline.
+
+A failed detector never fails the run — the error goes to stderr and into
+`report.json`.