logseq-matryca-parser 1.2.0__tar.gz → 1.2.1__tar.gz

{logseq_matryca_parser-1.2.0 → logseq_matryca_parser-1.2.1}/.cursorignore

@@ -68,3 +68,6 @@ tests/fixtures/*.md
 .vscode/
 .idea/
 .clinerules
+
+# Esclude lo storico delle metriche per preservare il contesto LLM
+metrics/history.json

logseq_matryca_parser-1.2.1/.github/CODEOWNERS

@@ -0,0 +1,4 @@
+# Default owners for all files in this repository.
+# See: https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners
+
+* @MarcoPorcellato

logseq_matryca_parser-1.2.1/.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,11 @@
+blank_issues_enabled: false
+contact_links:
+  - name: Security vulnerability
+    url: https://github.com/MarcoPorcellato/logseq-matryca-parser/security/policy
+    about: Report a security issue privately — do not open a public issue
+  - name: Contributing guidelines
+    url: https://github.com/MarcoPorcellato/logseq-matryca-parser/blob/main/CONTRIBUTING.md
+    about: Read how to set up your environment, run tests, and open a pull request
+  - name: Code of Conduct
+    url: https://github.com/MarcoPorcellato/logseq-matryca-parser/blob/main/CODE_OF_CONDUCT.md
+    about: Community standards and how to report unacceptable behavior

logseq_matryca_parser-1.2.1/.github/workflows/ci.yml

@@ -0,0 +1,49 @@
+name: Logos Protocol CI
+
+on:
+  push:
+    branches: [ "main" ]
+  pull_request:
+    branches: [ "main" ]
+
+concurrency:
+  group: ${{ github.workflow }}-${{ github.ref }}
+  cancel-in-progress: true
+
+permissions:
+  contents: read
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    strategy:
+      fail-fast: false
+      matrix:
+        python-version: [ "3.12", "3.13" ]
+
+    steps:
+    - name: Checkout Code
+      uses: actions/checkout@v6
+
+    - name: Install uv
+      uses: astral-sh/setup-uv@v6
+      with:
+        python-version: ${{ matrix.python-version }}
+        enable-cache: true
+
+    - name: Sync dependencies
+      run: uv sync --all-extras
+
+    - name: Audit dependencies
+      run: |
+        uv export --no-dev --no-emit-workspace --no-hashes -o "${{ runner.temp }}/requirements-audit.txt"
+        uv run pip-audit -r "${{ runner.temp }}/requirements-audit.txt"
+
+    - name: Lint
+      run: make lint
+
+    - name: Type check
+      run: make check
+
+    - name: Test
+      run: make test

logseq_matryca_parser-1.2.1/.github/workflows/codeql.yml

@@ -0,0 +1,37 @@
+name: CodeQL
+
+on:
+  push:
+    branches: [ "main" ]
+  pull_request:
+    branches: [ "main" ]
+
+jobs:
+  analyze:
+    name: Analyze
+    runs-on: ubuntu-latest
+    permissions:
+      security-events: write
+      packages: read
+      actions: read
+      contents: read
+
+    strategy:
+      fail-fast: false
+      matrix:
+        language: [ "python" ]
+
+    steps:
+    - name: Checkout repository
+      uses: actions/checkout@v6
+
+    - name: Initialize CodeQL
+      uses: github/codeql-action/init@v3
+      with:
+        languages: ${{ matrix.language }}
+
+    - name: Autobuild
+      uses: github/codeql-action/autobuild@v3
+
+    - name: Perform CodeQL Analysis
+      uses: github/codeql-action/analyze@v3

logseq_matryca_parser-1.2.1/.github/workflows/daily-metrics.yml

@@ -0,0 +1,145 @@
+name: Daily Metrics Saver
+
+on:
+  schedule:
+    - cron: '0 3 * * *' # Gira ogni giorno alle 03:00 UTC
+  workflow_dispatch: # Permette l'avvio manuale con un click
+
+permissions:
+  contents: write
+
+env:
+  # Forza l'ambiente di esecuzione su Node.js 24 per prevenire i warning di deprecazione di giugno 2026
+  FORCE_JAVASCRIPT_ACTIONS_TO_NODE24: true
+
+jobs:
+  save-metrics:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout Repository
+        uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+
+      - name: Set up Python
+        uses: actions/setup-python@v5
+        with:
+          python-version: '3.11'
+
+      - name: Fetch and Merge Metrics
+        env:
+          GITHUB_TOKEN: ${{ secrets.METRICS_TOKEN }}
+          REPO_SLUG: ${{ github.repository }}
+        run: |
+          python -c "
+          import os, json, sys, datetime
+          from urllib.request import Request, urlopen
+          from urllib.error import HTTPError
+          token = os.environ.get('GITHUB_TOKEN')
+          repo = os.environ.get('REPO_SLUG')
+          if not token:
+              print('Errore critico: METRICS_TOKEN non trovato nei Secrets!')
+              sys.exit(1)
+
+          headers = {
+              'Authorization': f'Bearer {token}',
+              'Accept': 'application/vnd.github.v3+json'
+          }
+
+          def fetch_api(url):
+              try:
+                  req = Request(url, headers=headers)
+                  with urlopen(req) as response:
+                      return json.loads(response.read().decode())
+              except HTTPError as e:
+                  print(f'Errore API HTTP {e.code} per {url}: {e.reason}')
+                  return None
+              except Exception as e:
+                  print(f'Errore generico nel fetching di {url}: {e}')
+                  return None
+
+          # 1. Recupera tutti i dati di traffico (inclusi i nuovi endpoint)
+          views_data = fetch_api(f'https://api.github.com/repos/{repo}/traffic/views')
+          clones_data = fetch_api(f'https://api.github.com/repos/{repo}/traffic/clones')
+          referrers_data = fetch_api(f'https://api.github.com/repos/{repo}/traffic/popular/referrers')
+          paths_data = fetch_api(f'https://api.github.com/repos/{repo}/traffic/popular/paths')
+          releases_data = fetch_api(f'https://api.github.com/repos/{repo}/releases')
+
+          # 2. Prepara la cartella e la struttura dello storico
+          os.makedirs('metrics', exist_ok=True)
+          history_file = 'metrics/history.json'
+
+          if os.path.exists(history_file):
+              with open(history_file, 'r') as f:
+                  try:
+                      history = json.load(f)
+                  except:
+                      history = {}
+          else:
+              history = {}
+
+          # Inizializza i nodi se mancanti
+          for key in ['views', 'clones', 'releases', 'referrers', 'popular_content']:
+              if key not in history:
+                  history[key] = {}
+
+          today = datetime.datetime.utcnow().strftime('%Y-%m-%d')
+
+          # 3. Storicizza le Views (Ultimi 14 giorni)
+          v_days_added = []
+          if views_data and 'views' in views_data:
+              for v in views_data['views']:
+                  day = v['timestamp'][:10]
+                  history['views'][day] = {'count': v['count'], 'uniques': v['uniques']}
+                  v_days_added.append(day)
+          print(f'-> [INFO] Rilevate {len(v_days_added)} giornate di traffico (Views).')
+
+          # 4. Storicizza i Clones (Ultimi 14 giorni)
+          c_days_added = []
+          if clones_data and 'clones' in clones_data:
+              for c in clones_data['clones']:
+                  day = c['timestamp'][:10]
+                  history['clones'][day] = {'count': c['count'], 'uniques': c['uniques']}
+                  c_days_added.append(day)
+          print(f'-> [INFO] Rilevate {len(c_days_added)} giornate di clonazione (Clones).')
+
+          # 5. Nuovo: Snapshot quotidiano dei Referring Sites (Siti di provenienza)
+          if referrers_data:
+              history['referrers'][today] = [
+                  {'referrer': r['referrer'], 'count': r['count'], 'uniques': r['uniques']}
+                  for r in referrers_data
+              ]
+              print(f'-> [INFO] Snapshot dei Referring Sites archiviato per la data: {today}')
+
+          # 6. Nuovo: Snapshot quotidiano dei Popular Paths (Contenuto popolare)
+          if paths_data:
+              history['popular_content'][today] = [
+                  {'path': p['path'], 'title': p['title'], 'count': p['count'], 'uniques': p['uniques']}
+                  for p in paths_data
+              ]
+              print(f'-> [INFO] Snapshot del Popular Content archiviato per la data: {today}')
+
+          # 7. Snapshot cumulativo dei download delle release
+          if releases_data:
+              history['releases'][today] = [
+                  {
+                      'tag': r['tag_name'],
+                      'assets': [{a['name']: a['download_count']} for a in r.get('assets', [])]
+                  }
+                  for r in releases_data
+              ]
+              print(f'-> [INFO] Snapshot dei download release registrato.')
+
+          # 8. Scrivi lo storico aggiornato su disco
+          with open(history_file, 'w') as f:
+              json.dump(history, f, indent=2)
+          
+          print('✓ Database JSON delle metriche aggiornato con successo con i nuovi tracciamenti!')
+          "
+
+      - name: Commit & Push Changes
+        run: |
+          git config --local user.email "action@github.com"
+          git config --local user.name "GitHub Action Bot"
+          git add metrics/history.json
+          git diff --quiet && git diff --staged --quiet || (git commit -m "chore(analytics): archive comprehensive repository metrics [skip ci]" && git push)

{logseq_matryca_parser-1.2.0 → logseq_matryca_parser-1.2.1}/.github/workflows/pypi_publish.yml

@@ -10,7 +10,32 @@ permissions:
   id-token: write
 
 jobs:
+  pre-flight:
+    name: Pre-flight checks (Python ${{ matrix.python-version }})
+    runs-on: ubuntu-latest
+    strategy:
+      fail-fast: false
+      matrix:
+        python-version: [ "3.12", "3.13" ]
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v6
+
+      - name: Install uv
+        uses: astral-sh/setup-uv@v6
+        with:
+          python-version: ${{ matrix.python-version }}
+          enable-cache: true
+
+      - name: Sync dependencies
+        run: uv sync --all-extras
+
+      - name: Run quality gate
+        run: make all
+
   publish:
+    name: Publish
+    needs: pre-flight
     runs-on: ubuntu-latest
     environment:
       name: pypi

logseq_matryca_parser-1.2.1/.pre-commit-config.yaml

@@ -0,0 +1,19 @@
+repos:
+-   repo: https://github.com/astral-sh/ruff-pre-commit
+    rev: v0.15.12
+    hooks:
+    -   id: ruff
+        args: [--fix]
+-   repo: https://github.com/pre-commit/mirrors-mypy
+    rev: v1.20.2
+    hooks:
+    -   id: mypy
+        pass_filenames: false
+        args: [src/, tests/, examples/]
+        additional_dependencies:
+        - pydantic>=2.7.0
+        - typer>=0.12.0
+        - rich>=13.7.1
+        - pytest>=9.0.3
+        - networkx>=3.0.0
+        - pyvis>=0.3.2

{logseq_matryca_parser-1.2.0 → logseq_matryca_parser-1.2.1}/CHANGELOG.md

@@ -7,6 +7,29 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [1.2.1] - 2026-06-18
+
+### Added
+
+- **Community health files** — `CODE_OF_CONDUCT.md` (Contributor Covenant 2.1), `.github/CODEOWNERS`, and `.github/ISSUE_TEMPLATE/config.yml` for GitHub Community Standards compliance.
+- **PyPI project URLs** — `Repository`, `Source`, `Documentation`, and `Changelog` links in `pyproject.toml`.
+- **Coverage gate** — `pytest-cov` in the dev group; `make test` enforces `--cov-fail-under=80` with `[tool.coverage.*]` in `pyproject.toml`.
+- **CodeQL workflow** — `.github/workflows/codeql.yml` for Python SAST on push/PR to `main`.
+- **PyPI pre-flight** — `pypi_publish.yml` runs `make all` via `uv` before building and publishing a tag.
+- **CI Python matrix** — GitHub Actions tests Python **3.12** and **3.13** in `ci.yml` and PyPI pre-flight.
+
+### Changed
+
+- **CI toolchain** — `.github/workflows/ci.yml` uses `astral-sh/setup-uv` and runs `uv sync --all-extras` followed by `make lint`, `make check`, and `make test` (parity with local `make all`).
+- **CONTRIBUTING.md** — development setup documents `uv sync --all-extras` instead of `pip install -e .`.
+- **Pre-commit** — Ruff and Mypy hook versions aligned with the `dev` dependency group in `pyproject.toml`.
+- **Mypy scope** — unified to `src/`, `tests/`, and `examples/` in the Makefile, CI, CONTRIBUTING, and pre-commit.
+- **CI security** — `pip-audit` on exported production requirements and `concurrency` cancel-in-progress on the same ref.
+- **Version sync test** — `tests/test_package_version.py` asserts `__version__` matches `importlib.metadata.version(...)`.
+- **Documentation layout** — root `ROADMAP_*.md` files consolidated under `docs/roadmaps/`.
+- **README badges** — Python support badge updated to **3.12 | 3.13**; CI badge links directly to the workflow.
+- **PyPI classifiers** — `Programming Language :: Python :: 3.13` added in `pyproject.toml`.
+
 ## [1.2.0] - 2026-05-29
 
 ### Added

logseq_matryca_parser-1.2.1/CODE_OF_CONDUCT.md

@@ -0,0 +1,132 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, caste, color, religion, or sexual
+identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the overall
+  community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or advances of
+  any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email address,
+  without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, and will communicate reasons for moderation
+decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official email address,
+posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement at
+**marco@marcoporcellato.it**.
+
+All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining
+the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series of acts.
+
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction with
+those enforcing the Code of Conduct, for a specified period of time. This
+includes avoiding interactions in community spaces as well as external channels
+like social media. Violating these terms may lead to a temporary or permanent
+ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including
+sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No public or
+private interaction with the people involved, including unsolicited interaction
+with those enforcing the Code of Conduct, is allowed during this period.
+Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior, harassment of an
+individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within the
+community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.1, available at
+[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
+
+Community Impact Guidelines were inspired by
+[Mozilla's code of conduct enforcement ladder][mozilla].
+
+For answers to common questions about this code of conduct, see the FAQ at
+[https://www.contributor-covenant.org/faq][faq]. Translations are available at
+[https://www.contributor-covenant.org/translations][translations].
+
+[homepage]: https://www.contributor-covenant.org
+[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
+[mozilla]: https://github.com/mozilla/diversity
+[faq]: https://www.contributor-covenant.org/faq
+[translations]: https://www.contributor-covenant.org/translations

{logseq_matryca_parser-1.2.0 → logseq_matryca_parser-1.2.1}/CONTRIBUTING.md

@@ -15,7 +15,7 @@ User-facing behavior is documented in:
 - [`README.md`](README.md) — overview, quickstart, and feature matrix
 - [`docs/ARCHITECTURE.md`](docs/ARCHITECTURE.md) — LOGOS, SYNAPSE, `LogseqGraph`, agents, and data flow
 - [`docs/logseq_ast_primer.md`](docs/logseq_ast_primer.md) — Logseq Spatial Markdown domain rules
-- [`CHANGELOG.md`](CHANGELOG.md) — shipped releases (current: **1.2.0**) and **Unreleased** changes (Keep a Changelog)
+- [`CHANGELOG.md`](CHANGELOG.md) — shipped releases (current: **1.2.1**) and **Unreleased** changes (Keep a Changelog)
 - [`docs/RELEASE_PROCESS.md`](docs/RELEASE_PROCESS.md) — version bump, tag, and PyPI publish checklist
 
 When you add or change observable parser or graph behavior, update the relevant doc sections and add a bullet under **`## [Unreleased]`** in `CHANGELOG.md` (see [`.cursor/rules/05-auto-changelog.mdc`](.cursor/rules/05-auto-changelog.mdc)).
@@ -36,7 +36,7 @@ Before writing any code, please understand our core principles:
 
 ## 🛠️ Development Setup
 
-To set up your local environment:
+This project uses [uv](https://docs.astral.sh/uv/) for dependency management and a virtual environment in `.venv/`. Do not use `pip install -e .` — CI and local workflows both go through `uv`.
 
 1. **Fork and Clone:**
    ```bash
@@ -44,19 +44,22 @@ To set up your local environment:
    cd logseq-matryca-parser
    ```
 
-2. **Create an Isolated Environment:**
+2. **Install uv** (if not already installed):
    ```bash
-   python3 -m venv .venv
-   source .venv/bin/activate  # On Windows: .venv\Scripts\activate
+   curl -LsSf https://astral.sh/uv/install.sh | sh
    ```
 
-3. **Install the Project in Editable Mode:**
-   *(Includes development dependencies)*
+3. **Sync the environment** (project + optional extras + dev tools from `pyproject.toml`):
    ```bash
-   pip install -e .
-   pip install pytest mypy ruff
+   uv sync --all-extras
    ```
 
+4. **Optional — install pre-commit hooks** (Ruff + Mypy, aligned with CI):
+   ```bash
+   uv run pre-commit install
+   ```
+   If `pre-commit` is not yet available, add it once with `uv tool install pre-commit` or `uv add --dev pre-commit`.
+
 ---
 
 ## 🚦 The Contribution Workflow
@@ -85,31 +88,26 @@ git checkout -b feat/add-html-exporter
 
 ### 4. Code Quality & Linting (Mandatory)
 
-We run a strict CI pipeline. Before committing, you must ensure your code passes static analysis and tests.
-
-We provide a `Makefile` to simplify running these commands. You can execute them individually or all at once:
+CI runs the same commands as your local environment: `uv sync --all-extras`, then `make lint`, `make check`, and `make test`. Before committing, run the full gate:
 
 ```bash
-# Run all checks (linting, static typing, and tests)
 make all
-
-# Or run them individually:
-make lint   # Check formatting and linting with Ruff
-make check  # Check static typing with Mypy
-make test   # Run unit tests with Pytest
 ```
 
-Alternatively, you can run the commands directly:
+Or run each step individually:
 
 ```bash
-# Check formatting and linting
-ruff check .
+make lint   # Ruff (with auto-fix)
+make check  # Mypy on src/, tests/, examples/
+make test   # Pytest on tests/
+```
 
-# Check static typing
-mypy src/ tests/ examples/
+Equivalent `uv run` invocations:
 
-# Run tests
-pytest
+```bash
+uv run ruff check . --fix
+uv run mypy src/ tests/ examples/
+uv run pytest -v tests/
 ```
 
 ### 5. Commit Standards
@@ -131,6 +129,8 @@ We follow [Conventional Commits](https://www.conventionalcommits.org/). Your com
 
 ## 🤝 Code of Conduct
 
-We expect all contributors to maintain a professional, respectful, and constructive tone. We are building the future of sovereign knowledge management together.
+This project follows the [Contributor Covenant](CODE_OF_CONDUCT.md). By participating, you agree to uphold a professional, respectful, and constructive community.
+
+Report unacceptable behavior to [marco@marcoporcellato.it](mailto:marco@marcoporcellato.it).
 
 > *By contributing to this project, you agree that your contributions will be licensed under its Apache 2.0 License.*

{logseq_matryca_parser-1.2.0 → logseq_matryca_parser-1.2.1}/Makefile

@@ -6,10 +6,10 @@ lint:
 	uv run ruff check . --fix
 
 check:
-	uv run mypy src/ tests/
+	uv run mypy src/ tests/ examples/
 
 test:
-	uv run pytest -v tests/
+	uv run pytest --cov=src/logseq_matryca_parser --cov-report=term-missing --cov-fail-under=80 -v tests/
 
 build:
 	uv run python -m nuitka --standalone --onefile src/logseq_matryca_parser/kinetic.py