bravos 0.1.0__py3-none-any.whl

bravos/__init__.py

@@ -0,0 +1,22 @@
+# @comment -- "bravos: deterministic orchestrator that drives guardlink (annotate/SARIF) and
+#   cert-x-gen (cxg pentest) in a closed loop until the threat model converges. The package core
+#   is a state machine; AI coding-agent CLIs are invoked only at explicit judgment points."
+"""bravos — continuous SAST and whitebox pentest orchestrator."""
+
+__version__ = "0.1.0"
+
+# @comment -- "THE ONE SENTENCE, SO THERE IS ONLY EVER ONE TO CHANGE. The banner tagline, the
+#   `--help` description and the bare-`bravos` landing all render from here rather than each
+#   carrying its own copy, which is how they drifted apart in the first place — the landing and
+#   the tagline had already diverged in capitalisation, and one of the copies was the PyPI
+#   summary. The wording is the owner's, verbatim but for two mechanical fixes: SAST is an
+#   initialism, and his `Continuous sast, and whitebox pentest orchestrator` read as a list
+#   whose first item had no head noun.
+#   The docs landing page at docs.bugb.com/bravos/ deliberately keeps a longer benefit
+#   sentence instead. A summary and a banner are scanned for keywords, a landing page is read;
+#   the two are not required to agree and should not be reconciled.
+#   The only copies that cannot import this are `pyproject.toml` — the PyPI summary, read by
+#   the build backend before Python runs — and the test that pins the wording."
+DESCRIPTION = "Continuous SAST and whitebox pentest orchestrator"
+
+SCHEMA_VERSION = 1

bravos/__main__.py

@@ -0,0 +1,36 @@
+# @comment -- "Console-script entrypoint; delegates immediately so the CLI stays importable and
+#   testable without a subprocess."
+"""``python -m bravos`` / ``bravos`` entrypoint."""
+
+from __future__ import annotations
+
+import sys
+
+from .cli import main
+
+
+# @comment -- "KEPT, NOT SHIPPED, and the distinction is the whole entry. This was the `bugb`
+#   console script, and its reason was that `pip install -U` REPLACES a distribution, so an upgrade
+#   would take `bugb` off PATH and stop every script, Makefile and CI step a team already wrote.
+#   That reason was checked against reality before the first publish and did not survive it: nothing
+#   has ever been published, so no machine holds a `bugb` that came from installing this
+#   distribution, and the shim protected nobody. What it did do was put a second, unexplained
+#   command on a brand-new user's PATH — and a command a customer is told to type is
+#   customer-facing, which per the 2026-09-08 decision means it is Bravos.
+#   The function stays because deleting it is not free and keeping it is: re-exposing the name is
+#   one line in pyproject.toml if real users ever turn out to need it, and until then this is the
+#   shape that line would restore. Nothing calls it today.
+#   The notice goes to stderr, as every compatibility notice here does — a `--format json` run still
+#   has to emit a document a pipeline can parse."
+def main_legacy() -> int:
+    """The retired ``bugb`` entry point: says the name moved, then runs ``bravos``.
+
+    Not declared in ``[project.scripts]``; kept so restoring the name is one line.
+    """
+    print("note: `bugb` is now `bravos`. This command still works and runs the same engine; "
+          "switch to `bravos` when convenient.", file=sys.stderr)
+    return main()
+
+
+if __name__ == "__main__":  # pragma: no cover
+    sys.exit(main())

bravos/adapters/__init__.py

@@ -0,0 +1,4 @@
+# @comment -- "Adapters wrap exactly one external surface each and take a ProcRunner by
+#   injection, so the fast test suite can assert the precise argv bravos builds without any real
+#   binary on PATH."
+"""Adapters over external tools."""