aa-fitting-mastery 0.1.0__tar.gz

aa_fitting_mastery-0.1.0/.coveragerc

@@ -0,0 +1,18 @@
+[run]
+branch = True
+source = mastery
+
+[report]
+exclude_lines =
+    if self.debug:
+    pragma: no cover
+    raise NotImplementedError
+    if __name__ == .__main__.:
+ignore_errors = True
+omit =
+    setup.py
+    tests.py
+    */test_*.py
+    */tests/*
+    */migrations/*
+    doc/*

aa_fitting_mastery-0.1.0/.gitattributes

@@ -0,0 +1,2 @@
+# Auto detect text files and perform LF normalization
+* text=auto

aa_fitting_mastery-0.1.0/.github/workflows/main.yml

@@ -0,0 +1,55 @@
+# This is a basic workflow to help you get started with Actions
+name: CI
+
+# Controls when the workflow will run
+on:
+  push:
+    branches:
+      - "**"
+    tags-ignore:
+      - "**"
+  pull_request:
+    branches:
+      - "**"
+    tags-ignore:
+      - "**"
+  # Allows you to run this workflow manually from the Actions tab
+  workflow_dispatch:
+
+# A workflow run is made up of one or more jobs that can run sequentially or in parallel
+jobs:
+  test:
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        python-version: ["3.10", "3.11", "3.12"]
+    steps:
+      - uses: actions/checkout@v4
+
+      - uses: shogo82148/actions-setup-redis@v1
+        with:
+          redis-version: "latest"
+
+      - run: redis-cli ping
+
+      - uses: actions/setup-python@v5
+        with:
+          python-version: ${{ matrix.python-version }}
+
+      - name: install dependencies
+        run: make dev
+
+      - name: Run Tests
+        run: make test
+
+      - name: Upload test coverage
+        if: ${{ !env.ACT }}
+        uses: actions/upload-artifact@v4
+        with:
+          # Artifact name
+          name: Python${{ matrix.python-version }} Test Coverage
+          # A file, directory or wildcard pattern that describes what to upload
+          path: htmlcov/
+
+      - name: Build Projects
+        run: make package

aa_fitting_mastery-0.1.0/.github/workflows/publish.yml

@@ -0,0 +1,33 @@
+name: Deploy to PyPi
+
+on:
+  release:
+    types: [released, prereleased]
+  # Allows you to run this workflow manually from the Actions tab
+  workflow_dispatch:
+
+jobs:
+  release:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+
+      - uses: actions/setup-python@v4
+        with:
+          python-version: "3.11"
+
+      - name: install dependencies
+        run: make dev
+
+      - name: clean up
+        run: make clean
+
+      - name: Build Python
+        run: make package
+
+      - name: Upload Package
+        if: ${{ !env.ACT }} # Don't run in a local test environment
+        env:
+          TWINE_USERNAME: __token__
+          TWINE_PASSWORD: ${{ secrets.PYPI_TOKEN }}
+        run: make deploy

aa_fitting_mastery-0.1.0/.gitignore

@@ -0,0 +1,181 @@
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[cod]
+*$py.class
+
+# C extensions
+*.so
+
+# Distribution / packaging
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+share/python-wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+MANIFEST
+
+# PyInstaller
+#  Usually these files are written by a python script from a template
+#  before PyInstaller builds the exe, so as to inject date/other infos into it.
+*.manifest
+*.spec
+
+# Installer logs
+pip-log.txt
+pip-delete-this-directory.txt
+
+# Unit test / coverage reports
+htmlcov/
+.tox/
+.nox/
+.coverage
+.coverage.*
+.cache
+nosetests.xml
+coverage.xml
+*.cover
+*.py,cover
+.hypothesis/
+.pytest_cache/
+cover/
+
+# Translations
+*.mo
+*.pot
+
+# Django stuff:
+*.log
+local_settings.py
+db.sqlite3
+db.sqlite3-journal
+
+# Flask stuff:
+instance/
+.webassets-cache
+
+# Scrapy stuff:
+.scrapy
+
+# Sphinx documentation
+docs/_build/
+
+# PyBuilder
+.pybuilder/
+target/
+
+# Jupyter Notebook
+.ipynb_checkpoints
+
+# IPython
+profile_default/
+ipython_config.py
+
+# pyenv
+#   For a library or package, you might want to ignore these files since the code is
+#   intended to run in multiple environments; otherwise, check them in:
+# .python-version
+
+# pipenv
+#   According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
+#   However, in case of collaboration, if having platform-specific dependencies or dependencies
+#   having no cross-platform support, pipenv may install dependencies that don't work, or not
+#   install all needed dependencies.
+#Pipfile.lock
+
+# UV
+#   Similar to Pipfile.lock, it is generally recommended to include uv.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+#uv.lock
+
+# poetry
+#   Similar to Pipfile.lock, it is generally recommended to include poetry.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+#   https://python-poetry.org/docs/basic-usage/#commit-your-poetrylock-file-to-version-control
+#poetry.lock
+
+# pdm
+#   Similar to Pipfile.lock, it is generally recommended to include pdm.lock in version control.
+#pdm.lock
+#   pdm stores project-wide configurations in .pdm.toml, but it is recommended to not include it
+#   in version control.
+#   https://pdm.fming.dev/latest/usage/project/#working-with-version-control
+.pdm.toml
+.pdm-python
+.pdm-build/
+
+# PEP 582; used by e.g. github.com/David-OConnor/pyflow and github.com/pdm-project/pdm
+__pypackages__/
+
+# Celery stuff
+celerybeat-schedule
+celerybeat.pid
+
+# SageMath parsed files
+*.sage.py
+
+# Environments
+.env
+.venv
+env/
+venv/
+ENV/
+env.bak/
+venv.bak/
+
+# Spyder project settings
+.spyderproject
+.spyproject
+
+# Rope project settings
+.ropeproject
+
+# mkdocs documentation
+/site
+
+# mypy
+.mypy_cache/
+.dmypy.json
+dmypy.json
+
+# Pyre type checker
+.pyre/
+
+# pytype static type analyzer
+.pytype/
+
+# Cython debug symbols
+cython_debug/
+
+# PyCharm
+#  JetBrains specific template is maintained in a separate JetBrains.gitignore that can
+#  be found at https://github.com/github/gitignore/blob/main/Global/JetBrains.gitignore
+#  and can be added to the global gitignore or merged into this file.  For a more nuclear
+#  option (not recommended) you can uncomment the following to ignore the entire idea folder.
+#.idea/
+
+# Ruff stuff:
+.ruff_cache/
+
+# PyPI configuration file
+.pypirc
+
+# Cursor  
+#  Cursor is an AI-powered code editor.`.cursorignore` specifies files/directories to 
+#  exclude from AI features like autocomplete and code analysis. Recommended for sensitive data
+#  refer to https://docs.cursor.com/context/ignore-files
+.cursorignore
+.cursorindexingignore

aa_fitting_mastery-0.1.0/.readthedocs.yml

@@ -0,0 +1,19 @@
+version: 2
+
+build:
+  os: "ubuntu-22.04"
+  apt_packages:
+    - redis
+  tools:
+    python: "3.11"
+
+# Build from the docs/ directory with Sphinx
+sphinx:
+  configuration: docs/conf.py
+
+# Explicitly set the version of Python and its requirements
+python:
+  install:
+    - method: pip
+      path: .
+    - requirements: docs/requirements.txt

aa_fitting_mastery-0.1.0/AGENTS.md

@@ -0,0 +1,41 @@
+# AGENTS.md
+
+## Scope and mental model
+- This file is for work in `working/aa-fitting-mastery/` only. Treat other plugins as external dependencies unless a task explicitly crosses repo boundaries.
+- `aa-fitting-mastery` is a Django app for Alliance Auth that bridges `fittings` and `memberaudit`: it turns doctrines/fittings into `SkillSetGroup` + `SkillSet` data, then augments them with EVE SDE masteries/certificates.
+- The core flow is: doctrine -> doctrine map -> fitting map -> extracted required skills -> recommended mastery skills -> optional blacklist/suggestions.
+
+## Read these files first
+- Start with `README.md`, `pyproject.toml`, and `mastery/apps.py` for package identity and hard dependencies.
+- Read `mastery/urls.py`, `mastery/views.py`, and `mastery/api.py` to see the actual UI/API surface.
+- For the main business logic, read `mastery/services/doctrine/doctrine_map_service.py` and `mastery/services/doctrine/doctrine_skill_service.py`.
+- Then read `mastery/services/fittings/skill_extractor.py`, `mastery/services/sde/mastery_service.py`, and `mastery/services/skills/{skill_control_service.py,suggestion_service.py}`.
+- Use `mastery/models/` and `mastery/migrations/` as the source of truth for persistence shape.
+
+## Architecture and data flow you should preserve
+- `DoctrineMapService.create_doctrine_map()` creates one `memberaudit.SkillSetGroup` per `fittings.Doctrine`, stores it in `DoctrineSkillSetGroupMap`, then immediately calls `sync()`.
+- `FittingMapService.create_fitting_map()` creates one `memberaudit.SkillSet` per `fittings.Fitting`, attaches it to the doctrine’s skillset group, and stores the mapping in `FittingSkillsetMap`.
+- `DoctrineSkillService.generate_for_doctrine()` is the core orchestrator: it reads doctrine fittings, extracts hard requirements from `eve_sde.TypeDogma`, merges them with mastery recommendations from imported SDE data, wipes existing `skillset.skills`, bulk-creates new `SkillSetSkill` rows, then records suggestions in `FittingSkillControl`.
+- Blacklist state is stored in `FittingSkillControl.is_blacklisted`; suggestion metadata also lives in `FittingSkillControl`, not in transient view state.
+- `DoctrineSkillSnapshot` exists as persisted snapshot data for doctrine/fitting/skill combinations; inspect current usage before changing or deleting it.
+
+## Project-specific conventions
+- Views in `mastery/views.py` are thin and instantiate service objects at module scope. Preserve that pattern unless you have a strong reason to change initialization behavior.
+- This plugin uses service classes, not fat models, for most business logic. New behavior usually belongs under `mastery/services/`, not directly in views/API handlers.
+- Data creation is intentionally idempotent-ish: `filter().first()`, `create()`, and `update_or_create()` are used heavily to avoid duplicate maps/control rows.
+- `mastery/api.py` is minimal right now: `toggle_blacklist` is the real mutating endpoint; `update_skill_level` currently parses JSON and returns `{"status": "ok"}` without persistence.
+- `auth_hooks.py` is the navigation/URL integration point: menu entry uses `mastery.basic_access`, while management screens require `mastery.manage_fittings`.
+- `character_portrait_url` does not reliably support arbitrary sizes (e.g. 24). Use supported portrait sizes in templates (this plugin standardises on `32`).
+
+## External dependencies and integration points
+- Hard package dependencies are declared in `pyproject.toml`: `allianceauth`, `aa-memberaudit`, `fittings`, `allianceauth-app-utils`, `django-esi`, and `django-eveonline-sde`.
+- `skill_extractor.py` depends on `eve_sde` dogma attributes for skill requirements; changes there can alter every generated skillset.
+- SDE mastery recommendations are imported from CCP static data by `mastery/services/sde/importer.py` and exposed through `MasteryService.get_ship_skills()`.
+- If a task touches installation/runtime integration, check `working/myauth/myauth/settings/local.py`: this workspace already enables `'mastery'` and schedules `mastery.tasks.import_sde_masteries` under `CELERYBEAT_SCHEDULE['update_sde_masteries']`.
+
+## Testing and developer workflow
+- `Makefile` assumes an active virtualenv; `make dev` installs editable mode and `make test` runs `tox`.
+- `tox.ini` expects `testauth.settings_aa4.local` and `runtests.py`; keep those files in sync when changing test setup.
+- For real validation, prefer focused checks in the integrated AA instance or targeted Django shell/management-command smoke tests over guessing from `tox.ini`.
+- If you change SDE import logic, validate both the management command `python manage.py import_sde_masteries --dry-run` and the Celery task path in `mastery/tasks.py`.
+

aa_fitting_mastery-0.1.0/CHANGELOG.md

@@ -0,0 +1,25 @@
+# Change Log
+
+All notable changes to this project will be documented in this file.
+
+The format is based on [Keep a Changelog](http://keepachangelog.com/)
+and this project adheres to [Semantic Versioning](http://semver.org/).
+
+## [Unreleased] - yyyy-mm-dd
+
+### Added
+
+- Nothing yet.
+
+## [0.1.0] - 2026-04-15
+
+### Added
+
+- Initial public release of the Fitting Mastery plugin for Alliance Auth.
+- Doctrine skill plan generation based on `fittings` doctrines and fittings.
+- Mastery recommendation merge using imported EVE SDE certificates/masteries.
+- Pilot-facing readiness views and skill plan export helpers.
+- Summary/audience views to review readiness across selected member scopes.
+- Skill control tooling: blacklist, manual skill overrides, and recommendation overrides.
+- SDE import tooling with management command (`import_sde_masteries`) and Celery update task (`update_sde_masteries`).
+

aa_fitting_mastery-0.1.0/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Jay's
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

aa_fitting_mastery-0.1.0/Makefile

@@ -0,0 +1,30 @@
+.PHONY: help clean dev package test deploy
+
+help:
+	@echo "This project assumes that an active Python virtualenv is present."
+	@echo "The following make targets are available:"
+	@echo "  dev        install all deps for dev environment"
+	@echo "  clean      remove all old packages"
+	@echo "  test       run tests"
+	@echo "  package    build the python package"
+	@echo "  deploy     Configure the PyPi config file in CI"
+
+clean:
+	rm -rf dist/*
+
+dev:
+	pip install --upgrade pip
+	pip install wheel -U
+	pip install tox -U
+	pip install -e .
+
+test:
+	tox
+
+deploy:
+	pip install twine
+	twine upload dist/*
+
+package:
+	pip install flit
+	flit build