dsl41 0.1.0__tar.gz

dsl41-0.1.0/.github/workflows/release.yml

@@ -0,0 +1,40 @@
+# Publish to PyPI via trusted publishing (OIDC, no stored tokens) on version
+# tags. One-time setup on pypi.org: Account -> Publishing -> add pending
+# publisher (project dsl41, owner mrbald, repo dsl41, workflow release.yml,
+# environment pypi). Release: git tag vX.Y.Z && git push origin vX.Y.Z.
+
+name: release
+
+on:
+  push:
+    tags: ["v*"]
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: astral-sh/setup-uv@v6
+      - run: uv sync --extra dev
+      - run: uv run pytest -q
+      - run: uv build
+      - run: uvx twine check --strict dist/*
+      - uses: actions/upload-artifact@v4
+        with:
+          name: dist
+          path: dist/
+
+  publish:
+    needs: build
+    runs-on: ubuntu-latest
+    environment:
+      name: pypi
+      url: https://pypi.org/p/dsl41
+    permissions:
+      id-token: write
+    steps:
+      - uses: actions/download-artifact@v4
+        with:
+          name: dist
+          path: dist
+      - uses: pypa/gh-action-pypi-publish@release/v1

dsl41-0.1.0/.gitignore

@@ -0,0 +1,9 @@
+__pycache__/
+*.pyc
+.pytest_cache/
+.ruff_cache/
+.mypy_cache/
+dist/
+*.egg-info/
+.idea/
+.hypothesis/

dsl41-0.1.0/CLAUDE.md

@@ -0,0 +1,86 @@
+# CLAUDE.md — working agreement for dsl41
+
+You are implementing a migration compiler designed in a prior session. The design
+is finished and normative; it lives in `docs/`. Do not re-derive it — read it.
+
+## Read first, in this order
+1. `docs/ir-design.md` — the central spec (pipeline, AST/IR-F/IR-G models, oracle,
+   equivalence tiers, linter rules L001–L015). Model sketches there are the API.
+2. `docs/jil-statement-syntax.md` — statement scanner spec + fidelity tests F1–F4.
+3. `docs/autosys-semantics.md` — SEM entries; every one implies a trace test (§8).
+4. `docs/stonebranch-semantics.md` — UCS entries + M01–M36 mapping table; the UC
+   backend refuses R-rows and reports A-row assumptions (Part II requirements 1–3).
+5. `docs/decision-log.md` — do not relitigate DL entries; append new ones.
+
+## Non-negotiable disciplines
+- **No silent loss.** AST→IR-F lowering errors on unknown non-allow-listed
+  attributes (DL-07). UC compile refuses R-classified edges and emits migration-
+  report items instead. Every A-classified edge records its assumption.
+- **Fidelity is tested, not asserted.** `render(parse(x)) == x` on the whole corpus
+  before anything else is built. Canonical mode is a fixpoint (F2).
+- **IR-G is derived, never authoritative.** Pure function of IR-F; regenerate, do
+  not edit or persist as truth.
+- **Pure compiler.** No runtime dependency in any emitted artifact.
+- **Corpus hygiene.** `tests/corpus/` is synthetic/doc-derived ONLY. Never accept
+  production JIL from any employer estate into the repo, tests, or docs (LICENSING.md).
+- **Open questions stay open.** Q1–Q7 (autosys dossier §9), U1–U8 (stonebranch
+  Part III) are unresolved. Those with an implemented default (Q1–Q4, Q7, U1–U5,
+  U8) are marked in code with `# PENDING: Qn/Un`; the rest have no code switch —
+  Q5/Q6 live in the autosys dossier only (Q6-adjacent aside in oracle.py), U6/U7
+  in backend_uc's `_U_QUESTIONS` report table. Do not guess-resolve any of them;
+  implement the documented default and keep the switch (see condition.lark Q1 banner).
+
+## Implementation order (DL-03) — one phase per PR-sized unit
+All ten phases are built and tested (README's implementation memo has the source
+map); this list stays as the normative order and scope of each unit.
+1. `ast_jil`: scanner per spec + preserve/canonical renderers + F1–F4 tests.
+   Definition of done: all corpus files round-trip byte-identical; fuzz test green.
+2. `conditions`: lark loader (both start rules, `CONDITION_PRECEDENCE` setting),
+   Tree→Cond transformer, lookback token validation (L015 shapes), span retention.
+3. `ir`: Pydantic models exactly as ir-design §3–4 + lowering + model validators
+   (XOR rules SEM-31, lookback-on-global ban SEM-04).
+4. `lint`: Violation model (stable codes, `exit_code(strict)`) + L001–L005, L015
+   first (pure IR-F rules); graph rules follow phase 5.
+5. `derive`: passes 1–7 from ir-design §5, including mutex/OR/same-cycle detectors.
+6. `viz`: Markdown report of per-component Mermaid charts from IR-G (boxes →
+   subgraph, predicate-labeled edges, collapse threshold; visual grammar,
+   component split, and appendices per DL-35).
+7. `oracle`: event loop + status store + box fold; port dossier §8 trace tests.
+8. `equiv`: canonical form, tier a (structural), tier b (truth table w/ atom
+   ceiling), tier c (oracle traces, hypothesis event scripts).
+9. `backend_uc`: BLOCKED on U3 (pull `/resources/openapi.json` from the live
+   controller, freeze `docs/uc-edge-schema.md`, generate client). Until then only
+   the migration-report emitter and edge-classification plumbing.
+10. DSL (`decompiler` + surface): LAST, extracted from patterns the corpus shows
+    (DL-03). Do not design combinators speculatively.
+
+## Testing conventions
+- pytest + hypothesis; trace tests named `test_semXX_*` / pairs `test_pMxx_*`.
+- Every linter rule ships with a corpus fixture that triggers it and one that
+  doesn't.
+- The Q1 sentinel test (`test_precedence_modes_differ_where_expected`) must keep
+  passing until Q1 resolves; then replace it with the pinning trace test and
+  delete the losing grammar rule.
+
+## Style
+- Python ≥3.12, Pydantic V2, typer CLI, ruff line length 100, mypy clean.
+- snake_case throughout; small pure functions for analysis passes; no clever
+  metaprogramming in the IR.
+
+## When live-instance access is available (ask the user, don't assume)
+- Resolve Q1 (precedence), Q2 (lookback-0 anchor), Q3 (time+condition composition)
+  with tiny throwaway jobs; record answers as SEM amendments + trace tests.
+- Pull OpenAPI (U3), pin UC version, freeze edge schema.
+- `autorep -q` samples may be INSPECTED by the user to inform synthetic fixture
+  shapes but never committed (corpus hygiene).
+
+<!-- hats:core -->
+## Engineering core (hats)
+
+This project uses the shared **hats engineering core**. Before substantive
+work, read and follow `~/.hats/docs/USING.md`; it loads the hard rules
+(`GUARDRAILS.md`), the engineering priors (`PRIORS.md`), and the validated
+thinking tools. Re-read each session: the core is the source of truth and
+its updates propagate here automatically. If `~/.hats` does not resolve,
+the core is not linked on this machine (see the hats repo's README).
+<!-- /hats:core -->

dsl41-0.1.0/COMMERCIAL.md

@@ -0,0 +1,14 @@
+# Commercial licensing
+
+dsl41 is dual-licensed. The public repository is offered under the GNU Affero
+General Public License v3.0 only ([LICENSE](LICENSE)). If the AGPL's terms do
+not fit your use — for example embedding dsl41 in a proprietary product, or
+running a modified version as a network service without offering source — a
+separate commercial license is available from the copyright holders.
+
+Contact: mail@bobah.net
+
+> This document is an availability notice, not a license grant or a contract.
+> Commercial terms are agreed per customer in a signed agreement drafted with
+> counsel. Until such an agreement is executed, your use of dsl41 is governed
+> solely by the AGPL-3.0-only terms in [LICENSE](LICENSE).