maxitor 3.11.0__tar.gz

maxitor-3.11.0/.gitignore

@@ -0,0 +1,104 @@
+# ============================================================================
+# Secrets
+# ============================================================================
+# Real values live on the machine that uses them. An `.env.example` shows the shape and stays tracked.
+.env
+.env.*
+!.env.example
+/certificates/
+
+# ============================================================================
+# Python
+# ============================================================================
+__pycache__/
+*.py[cod]
+*$py.class
+*.so
+.Python
+
+# ============================================================================
+# Virtual environments
+# ============================================================================
+.venv/
+venv/
+ENV/
+env/
+
+# ============================================================================
+# Distribution / packaging
+# ============================================================================
+build/
+dist/
+*.egg-info/
+*.egg
+.eggs/
+wheels/
+
+# ============================================================================
+# Testing
+# ============================================================================
+.pytest_cache/
+.coverage
+.coverage.*
+htmlcov/
+*.cover
+.hypothesis/
+.tox/
+.nox/
+
+# ============================================================================
+# Type checking
+# ============================================================================
+.mypy_cache/
+.dmypy.json
+dmypy.json
+.pyre/
+.pytype/
+
+# ============================================================================
+# Node (Maxitor web client — source lives in git; node_modules stays local only)
+# ============================================================================
+packages/maxitor/web/client/node_modules/
+packages/maxitor/web/client/.vite/
+# Built frontend — assembled by CI before packaging; never commit
+packages/maxitor/web/maxitor/web/static/
+
+# ============================================================================
+# IDE
+# ============================================================================
+.idea/
+.vscode/
+*.swp
+*.swo
+.DS_Store
+
+# ============================================================================
+# Logs and temporary files
+# ============================================================================
+*.log
+code_quality.log
+*.tmp
+*.temp
+ocel_log.json
+
+# ============================================================================
+# Project specific - ARCHIVE (ваши локальные снимки)
+# ============================================================================
+archive/
+*.ver
+code.txt
+project_structure.txt
+
+# ============================================================================
+# Локальные черновики (русские версии документации и примеров)
+# ============================================================================
+*_draft.md
+*_draft.py
+.ipynb_checkpoints/
+docs/ru/
+
+# ============================================================================
+# НЕ ИГНОРИРУЕМ - эти файлы должны быть в git!
+# ============================================================================
+!.python-version
+!uv.lock

maxitor-3.11.0/CHANGELOG.md

@@ -0,0 +1,170 @@
+# Changelog
+
+All notable changes to `maxitor` (until 2.3.0 published as `aoa-maxitor`) are documented in this file.
+
+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).
+
+## [Unreleased]
+
+### Added
+
+- **Maxitor explores events step by step.** The Events pages open on one layer — every domain, every event, or every action that emits, as a pill at the top chooses — and you follow the graph link by link through ports, each showing what it leads to and how many. A domain tells how many events its vocabulary holds (an empty vocabulary is still one), or how many it emits without one; its actions port shows all its actions, so you see what events do not cover yet. A path passes each kind once: the second layer leads on to the kind not yet on the path, and the third joins back to what is already on the screen, so from an event you reach the actions of a domain and see which of them emit it. Filters fit what is on the screen — domains, coverage, the standing of events, kinds of method, actions with or without events — and any of them can paint it. Rest on a line to read its method, on an event to read its fields, producers and domains. A comparison of two versions paints the changes and counts them on closed ports, so none hides behind one; the address keeps what you opened.
+- **Maxitor opens a graph's history** served by `repo-graph-port` and shows any version: a version button and a picker with a time axis — its handle dragged to a version in One as in Diff — of merged pull requests, direct pushes, open pull requests by review state and Live; version numbers from tags, release flags, a card per point with who made and merged it, its size and its graph change; the address bar carries the key, so copying it shares the view. `repo-graph-port` adds each version's contribution and graph change, pull requests read from merge commits, and the open pull requests.
+- **`repo-graph-port`**, a service that reads a graph's history from its repository: versions with their pull requests, tags and releases, and any version's graph; read keys for private repositories through a GitHub App, links for public ones, GitHub's webhooks, and without them a fetch on read once ten minutes have passed. `pip install "maxitor[repo-graph-port]"`, command `repo-graph-port`.
+
+### Changed — breaking
+
+- **The setup skill sets up versions and graphs**, either or both, and audits the project on every run; release tags are no longer required.
+- **The setup skill is `aoa-graph-builder-setup`** (was `graph-builder-setup`): after its survey it asks one question at a time, with options — where each graph goes, how CI checks every graph, which check run writes them — then shows one table of what is and what will change and goes on only with the user's consent; it proposes a workflow when the project has no CI, and pins a commit until a release exists.
+- **The web part is `front`**: extra `front` (was `viewer`), command `maxitor` (was `maxitor-api`), import `maxitor.front` (was `maxitor.viewer`).
+
+## [3.0.0] – 2026-10-29
+
+### Changed — breaking
+
+- **One package, `maxitor`, with parts chosen by extras.** `pip install maxitor` is the `graph-builder` command alone (no AOA, no server); `maxitor[viewer]` adds the app; `maxitor[all]` both. Until 2.3.0 the app was `aoa-maxitor`, and the command was `maxitor-gnomon` 0.1.0.
+- **Imports**: the app is `maxitor.viewer` (was `aoa.maxitor`), the command `maxitor.graph_builder` (was `maxitor_gnomon`).
+- **The command** is `graph-builder` (was `gnomon`), its config `graph-builder.toml` with `graph_builder = "1.0"` (was `gnomon.toml` with `gnomon = "1.0"`), its skill `graph-builder-setup` (was `gnomon-setup`). Graph files are unchanged.
+- **The CI step** is `uses: bystrovmaxim/aoa/packages/maxitor/tools/graph_builder@<ref>`; it no longer installs the project's environment — the steps before it do, in whatever language the project is.
+- **The protocol's schemas** live in `packages/open-gnomon-protocol`, a folder with no code; their `$id` is the raw address of each file.
+
+## [2.3.0] – 2026-10-27
+
+### Added
+
+- **Rooms: look at one service together.** **Open room** gives a link; whoever opens it gives a name and joins. Everyone sees the others' pointers on the same spot of the diagram at any zoom, filters and layout modes are shared per page, a click on someone's circle goes to them, and **Follow** keeps your screen where theirs is, at your own zoom and never in a circle. The link is the invitation and names are not verified; a room holds 20 people and ends two minutes after its last person leaves. Rooms run over the WebSocket route `/api/v1/rooms/{room_id}/live`; a proxy in front of Maxitor must pass WebSockets through and keep the page's `Host` (README, *Production*). ([#271](https://github.com/bystrovmaxim/aoa/issues/271))
+
+- **Held graphs stay current.** While someone looks at a graph, Maxitor asks its service whether it changed — every 30 seconds with `ETag` or `Last-Modified`, every 2 minutes by the body's SHA-256 — rebuilds a changed one in the background and swaps it in only after a successful build; a service that is down keeps the graph. Open pages redraw in place. `GET /api/v1/graph-fingerprint` and `GET /api/meta/app-info` are new. ([#271](https://github.com/bystrovmaxim/aoa/issues/271))
+
+- **The same layout everywhere**, proven in the check run across Chromium, Firefox and WebKit and two screen sizes; a remembered full-graph arrangement is laid out once more. ERD tables take the new style, and the left panel shows a project link and the running version. ([#271](https://github.com/bystrovmaxim/aoa/issues/271))
+
+### Changed
+
+- **A built graph stays until `MAXITOR_MAX_GRAPHS` is reached.** The idle removal and `MAXITOR_GRAPH_IDLE_SECONDS` are gone. `MAXITOR_ROOM_ORIGINS` lists extra browser origins allowed to join a room. Requires `aoa-fastapi-adapter` 1.3.0 or later. ([#271](https://github.com/bystrovmaxim/aoa/issues/271))
+
+## [2.2.0] – 2026-10-27
+
+### Added
+
+- **Entity kinds come from the graph, and the ERD filters by them.** A graph names the kinds it holds and the name of each, and Maxitor keeps no list of its own: it shows whatever the graph says, calls an unnamed kind by its word with a capital letter, and lists an entity with no kind as unknown, so older graphs still open. `GET /api/v1/list-entity-kinds` returns the kinds of the loaded source. The ERD's one filter panel folds Domains and Kinds, one section open at a time, and each row hides or shows its tables; each table's header carries its kind's icon. ([#239](https://github.com/bystrovmaxim/aoa/issues/239))
+
+- **Every line between two tables on screen is drawn, and every association is one line.** A line no longer goes missing when its two ends are neighbours or come from two domains shown together. A relation and its declared inverse are one line with `source_field` and `target_field`, drawn with a bar for one end, a crow's foot for many, and the field name at each side. `list-entities` also returns the request-wide relations list, and hovering a line marks the fields at both ends while clicking a table or field name copies it. ([#239](https://github.com/bystrovmaxim/aoa/issues/239))
+
+### Changed
+
+- **A relation field's type is the target table's name.** The `FK -> ` prefix is gone, and a dictionary field's type no longer repeats the dictionary's name after an arrow: the line says it. The eighth domain colour is orange instead of grey, which is left to entity kinds. ([#239](https://github.com/bystrovmaxim/aoa/issues/239))
+
+## [2.0.0] – 2026-10-26
+
+### Breaking changes
+
+- **Every graph read names its source.** `GET /api/v1/*` and `GET /api/sidebar` require `?source=<graph-json URL>`; a read without it answers `400` naming the missing parameter, and the sidebar no longer answers an empty payload when nothing is loaded. `POST /api/load` now rebuilds the source it names instead of loading one graph for the whole process, and `GET /api/health` also reports `graphs_held`, `builds_running` and `builds_queued`. ([#214](https://github.com/bystrovmaxim/aoa/issues/214))
+
+### Added
+
+- **One graph per source.** The process keeps one built graph per AOA service: a cold read builds it once, repeat reads cost nothing, an unread graph is removed after an hour, at most 50 are held and at most 4 builds run at once. Deep links still open the graph they name in one step, a new "Reload from service" button rebuilds only the open source, and a busy server is retried by the page instead of being reported as a broken service. ([#214](https://github.com/bystrovmaxim/aoa/issues/214))
+
+### Changed
+
+- **Dictionary cards show their fields, not their values.** An entity diagram no longer draws a row for every value a dictionary declares: the card is the dictionary's name and its own fields, with the arrows that reach it and nothing in place of the values. A region catalogue of ninety-three entries stops deciding how tall a domain's drawing is. The graph export and the entity endpoint keep every value with its code, label and descriptive properties, and a saved graph renders without a rebuild. ([#265](https://github.com/bystrovmaxim/aoa/issues/265))
+
+- **Dictionary references connect entity cards.** Graph imports carry catalogue values and field hints beside the relation to a dictionary card. Newly rebuilt complete selections use ordinary association edges; earlier exports may contain special reference edges. The current query duplicates the retained dictionary field row and synthesized FK row for the ordinary-association form; row merging has not been delivered. See the [reproduction](../../docs/reports/complete-relationship-verification.md#dictionary-fields-in-maxitor) before relying on one row per field. ([#256](https://github.com/bystrovmaxim/aoa/issues/256))
+
+- **Dictionary cards emphasize human labels** — Value rows print labels and descriptive properties, while codes remain in tooltips. The inherited code and display-name fields are omitted from ordinary dictionary field rows; other entity fields are preserved. Existing reference payloads retain their codes. See the [diagram guide](../../docs/tutorials/step-29-maxitor.md). *The value row described here was removed by the entry above; the field-row rule stands.*
+
+### Changed
+
+- **Dictionary descriptions reach the diagram consistently.** Dictionary cards preserve exported properties, including formatted dates and collection values, as readable text. Specialization groups display one complete label supplied by the server, so the dictionary name no longer appears twice. Existing graph files that already contain these properties need no rebuild. ([#244](https://github.com/bystrovmaxim/aoa/issues/244))
+- **Dictionaries are visible in the model.** Entity diagrams show a dictionary’s values, names and descriptive properties inside its card, and identify fields that refer to it. Specialization groups name their dictionary and keep its declared order, without a duplicated selector column on the head. ([#241](https://github.com/bystrovmaxim/aoa/issues/241))
+- **The graph carries the meaning of each entity.** Maxitor now preserves the entity kind declared by the model, so graph consumers can distinguish business objects, technical connections, owned parts, specializations and reference values. Regenerate older graph exports before loading them. Automatic hiding of technical connections is not included in this change. ([#210](https://github.com/bystrovmaxim/aoa/issues/210))
+- **Lifecycle diagrams use state descriptions.** States now receive human names, an optional display order and optional outline and fill colours from the model. Initial states stay first; without presentation settings, the existing ordering and palette remain. Other domain fields stay available in the full graph rather than being copied into the diagram response. ([#209](https://github.com/bystrovmaxim/aoa/issues/209))
+
+- **A table on the entity diagram is one shape.** The band above a table's fields and the tinted rows that mark its primary and foreign keys used to keep their square corners, so every card wore small tabs where the colour ran past its rounded outline. The colour now follows the outline: the band's upper corners sit on the arcs and a tinted last row follows the lower ones, while the small gap the drawing always left between a fill and the border stays exactly as it was. Everything else about the card is what it was — the outline, the colours, the text, the arrows and the canvas — and the lifecycle and use-case diagrams are untouched. ([#226](https://github.com/bystrovmaxim/aoa/issues/226))
+
+## [1.3.0] – 2026-10-17
+
+### Added
+
+- **Entity specialization in diagrams.** The entity diagram now shows which kinds of details an entity can have: for example, move details or assignment details for an event. Alternatives appear together in a frame, while the field lists their codes and the field that distinguishes them. The frame groups alternatives visually; it does not represent another entity. ([#199](https://github.com/bystrovmaxim/aoa/issues/199))
+
+### Changed
+
+- **The six diagram endpoints declare the one graph they share.** Maxitor keeps one coordinator graph per process — the one `POST /api/load` builds from a service URL — and every diagram endpoint reads it: the domain list, the entity list, the node types, the full graph, the lifecycle automaton and the use-case diagram. That graph is now handed to them as a single shared resource, declared once, instead of as a resource recreated for every request. The declaration and the behaviour finally agree, and a second load still replaces the graph for everyone at once. Once a graph is loaded the endpoints answer exactly what they answered before. Before one is loaded the answers are also unchanged, with a single exception worth knowing: an endpoint that never reads the graph no longer fails merely because nothing is loaded — the entity list asked without a domain filter answers an empty result rather than an error. ([#213](https://github.com/bystrovmaxim/aoa/issues/213))
+
+## [1.1.6] – 2026-07-11
+
+### Added
+
+- **URL deep-linking for the Maxitor SPA.** `?source=<service-url>&view=<full-graph|domain-erd|use-case|lifecycle-fsm>[&domain=|&node=&host=]` loads the given service and lands directly on the given view — `use-case`/`lifecycle-fsm` opened without their qualifier fall back to the first matching sidebar row once it loads. Every subsequent navigation (sidebar click, loading/switching service) pushes a browser history entry and updates the URL, so Back/Forward step through visited diagrams one at a time (reloading the graph server-side if needed) and the current URL is always copy-paste shareable. ([#126](https://github.com/bystrovmaxim/aoa/issues/126))
+- **Mobile-responsive layout for the Maxitor SPA.** Below the `sm` breakpoint the sidebar becomes an off-canvas overlay drawer (was a permanent panel eating 48-255px of a narrow viewport) with a menu button to open it and auto-close on diagram selection. ERD/use-case/lifecycle views (Graphviz SVG) gained touch pan and two-finger pinch-zoom — previously mouse-only despite `touchAction: "none"` silently blocking native touch with nothing replacing it; the Full Graph view (G6 canvas) already had native touch support via G6 v5 and needed no change. Zoom toolbar buttons grow from 30px to 44px on mobile to meet minimum touch-target guidance. The "Node types" / "Domains" legend panels, previously pinned open and covering most of a narrow canvas, now start collapsed to a small pill on mobile and expand on tap. ([#125](https://github.com/bystrovmaxim/aoa/issues/125))
+- **Copy button on recent service URLs.** Hovering a row in the "AOA Service URL" panel's recent-history list reveals a copy-to-clipboard button (also reachable via keyboard focus), independent of the row's own click-to-load action.
+
+## [1.1.4] – 2026-07-10
+
+### Fixed
+
+- **`GetLifecycleFiniteAutomatonAction` reads FSM from DuckDB instead of local class import.** Previously the action called `importlib.import_module` on the entity class qualname, which fails in standalone deployments (`pip install aoa-maxitor`) where the target service's Python packages are not installed. Rewritten as a five-aspect pipeline — parse interchange id → validate Lifecycle vertex → load states → load transitions → assemble FSM payload — querying the already-loaded DuckDB graph (`lifecycle`, `state`, `lifecycle_contains_state_edges`, `lifecycle_transition_edges` tables); no local entity classes required. Aspect-level unit tests added. ([#101](https://github.com/bystrovmaxim/aoa/issues/101))
+
+## [1.1.3] – 2026-07-09
+
+### Fixed
+
+- **Frontend built with relative API paths.** Removed hardcoded `VITE_MAXITOR_API_BASE_URL=https://aoa.run/maxitor` and `--base=/maxitor/` from CI build; frontend now uses `--base=/` and relative `/api/` paths, making the package deployable at any domain or IP without rebuilding.
+- **`LoadAOAServiceAction` accepts arbitrary endpoint URLs.** Previously the URL normalization always appended `/examples/model/graph-json`, making it impossible to load from services with a different path (e.g. `/api/model/graph`). Now any URL with an explicit path is used as-is; the default AOA path is appended only when a bare host URL is supplied.
+
+## [1.1.2] – 2026-07-09
+
+### Changed
+
+- **Dependencies updated to current PyPI releases.** `aoa-action-machine>=1.0.1a0` (was `>=1.0.0a4`), `duckdb>=1.5,<2` (was `>=1.1,<2`), `httpx>=0.28,<1.0` (was `>=0.27,<1.0`).
+
+## [1.1.1] – 2026-07-08
+
+### Fixed
+
+- **Dependency `aoa-action-machine` pinned to non-existent stable version.** Changed `==1.0.0` → `>=1.0.0a4` so the package installs correctly from PyPI where only alpha releases are available. Similarly tightened `aoa-fastapi-adapter>=1.0.0a0` → `>=1.0.0`.
+
+## [1.1.0] – 2026-07-08
+
+### Added
+
+- **Bundled React SPA.** The compiled Vite frontend (`src/aoa/maxitor/static/`) is now included in the wheel via hatchling `artifacts`. `pip install aoa-maxitor` delivers both the API backend and the complete web UI — no Node.js required on the server.
+- **`StaticFiles` mount.** `create_app()` now mounts the bundled SPA at `/` (after all API routes) using FastAPI `StaticFiles(html=True)`, enabling SPA client-side routing fallback. The mount is skipped gracefully if the static directory is absent (dev environment without a built frontend).
+- **`uvicorn>=0.30` added to runtime dependencies.** Previously an implicit transitive dependency; now declared explicitly so `pip install aoa-maxitor` pulls a working ASGI server.
+
+### Deployment note
+
+The frontend is built with `--base=/maxitor/` and `VITE_MAXITOR_API_BASE_URL=https://aoa.run/maxitor`. Nginx should proxy `location /maxitor/ { proxy_pass http://127.0.0.1:8101/; }` — the prefix is stripped before reaching uvicorn.
+
+## [1.0.1] – 2026-06-27
+
+### Changed
+
+- **Test suite relocated into the package (`packages/aoa-maxitor/tests/`).** Maxitor unit tests moved out of the shared root `tests/maxitor/` into the package's own `tests/` directory, so the package is self-contained: test dependencies are declared in its `[dependency-groups]` dev group and pytest is configured via its own `[tool.pytest.ini_options]` (`testpaths`, `asyncio_mode`, `pythonpath`). The skipped integration test `test_load_aoa_service_action_integration.py` lives in the package alongside the maxitor unit tests (skipped by default — it requires a running `aoa-examples` service). ([#82](https://github.com/bystrovmaxim/aoa/issues/82))
+
+## [1.0.0] – 2026-06-24
+
+### Added
+
+- **`LoadAOAServiceAction` — five-aspect DuckDB loader for the AOA coordinator graph.** Accepts a bare base URL or full endpoint URL; empty/whitespace input rejected by Pydantic. Aspects in order: validate URL format → normalize to canonical `coordinator-json` endpoint → validate HTTP reachability → parse coordinator JSON structure → build `DuckDBGraphResource`. 24 unit tests cover all aspects and Pydantic validation; integration test included but skipped by default (`@pytest.mark.skip`). ([#78](https://github.com/bystrovmaxim/aoa/issues/78))
+- **`POST /api/load` — on-demand graph loading endpoint.** Accepts `{"service_url": "..."}`, runs `LoadAOAServiceAction` + `GetLeftMenuSidebarDataAction`, and stores results in `app.state`. The server no longer auto-loads a graph on startup; the graph is loaded only when the user provides a URL. `GET /api/sidebar` returns an empty payload when no graph is loaded. ([#78](https://github.com/bystrovmaxim/aoa/issues/78))
+- **Left sidebar: URL input with recent history.** When no graph is loaded, the sidebar shows an `AOA Service URL` text field with an inline load button. The last 10 successfully used URLs are persisted in `localStorage` and shown below the input as a quick-select list. ([#78](https://github.com/bystrovmaxim/aoa/issues/78))
+- **Left sidebar: switch-service button.** When a graph is loaded, a thin-stroke swap-arrows icon button appears in the sidebar header next to the collapse toggle. Clicking it clears the loaded graph from local state and returns to the URL input screen. ([#78](https://github.com/bystrovmaxim/aoa/issues/78))
+
+### Changed
+
+- **`GetLeftMenuSidebarDataAction` rewritten as a four-aspect DuckDB pipeline; `networkx` dependency removed.** The action no longer depends on `networkx`. Four `@regular_aspect` methods build sidebar `NodeEntity` lists in stages — level-1 root bucket nodes → level-2 fixed diagram rows → level-2 interchange nodes from DuckDB → level-3 per-domain ERD and per-entity class/lifecycle rows — with a `@summary_aspect` assembling the final `Result`. String helpers `_diagram_view_label` and `_lifecycle_state_machine_row_title` are `@staticmethod` methods on the class; aspect-level unit tests added. Deleted files: `api/session.py`, `node_build.py`, `interchange_demo_coordinator.py`, `model/diagrams/actions/load_graph_action.py`. ([#78](https://github.com/bystrovmaxim/aoa/issues/78))
+
+## maxitor-gnomon
+
+`maxitor-gnomon` joined `maxitor` in 3.0.0 as its `gnomon` part. Its one release, kept here as it was written:
+
+### [0.1.0] – 2026-10-28
+
+#### Added
+
+- **The Open Gnomon Protocol, versions 1.0 and 1.1** — a shared language for describing a project's model as a graph, one JSON Schema per version in `protocol/`; a published version never changes. ([#301](https://github.com/bystrovmaxim/aoa/issues/301))
+- **`gnomon write` and `gnomon check`** — each service's model kept in one `graph.json`, rebuilt from the code and checked in CI; a stale file fails with its differences, matched by `id`. **`gnomon validate`** tells a graph from anything else; **`gnomon skill`** prints the setup skill. ([#301](https://github.com/bystrovmaxim/aoa/issues/301))
+- **`gnomon.toml`**, the repository's list of graphs, with refusals that name the graph and the field. ([#301](https://github.com/bystrovmaxim/aoa/issues/301))
+- **The `gnomon-setup` skill** — connects a project to the protocol: surveys every service, proves its export (adding an exporter where needed), asks, then writes the config, the graphs and the CI check; never commits. ([#301](https://github.com/bystrovmaxim/aoa/issues/301))

maxitor-3.11.0/LICENSE

@@ -0,0 +1,192 @@
+                                 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.
+
+   Copyright 2026 Maxim Bystrov
+
+   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.

maxitor-3.11.0/NOTICE

@@ -0,0 +1,14 @@
+AOA — Action-Oriented Architecture
+Copyright 2026 Maxim Bystrov
+
+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.