feat: initial implementation of Picklock

.flake8

@@ -0,0 +1,12 @@
+[flake8]
+
+max-line-length = 130
+# E203: whitespace before ':' (black-compatible — black puts spaces around the
+#       colon in slices like data[i : i + n], which conflicts with PEP 8).
+# E701: multiple statements on one line (colon) — used pervasively as a style choice.
+# W503: line break before binary operator (black-compatible).
+ignore = E203, E701, W503
+
+per-file-ignores =
+    # __init__.py files are allowed to have unused imports and lines-too-long.
+    */__init__.py:F401, E501

.github/FUNDING.yml

@@ -0,0 +1,3 @@
+# These are supported funding model platforms
+
+github: JeanExtreme002

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,45 @@
+---
+name: Bug report
+about: Create a report to help us improve
+title: ''
+labels: ''
+assignees: ''
+
+---
+
+**Describe the bug**
+A clear and concise description of what the bug is.
+
+**To Reproduce**
+The exact commands you ran, and what happened:
+
+```console
+$ picklock
+picklock> ps:open 91434
+Attached to process.exe (PID 91434, 64-bit). (0.00 sec)
+picklock> ...
+```
+
+**Expected behavior**
+A clear and concise description of what you expected to happen instead.
+
+**Versions**
+Paste the output of `picklock --version` — it covers Picklock, PyMemoryEditor,
+Python and the platform:
+
+```
+       Picklock: 0.1.0
+PyMemoryEditor: 2.2.0
+        Python: 3.12.0
+      Platform: Linux 6.8.0 (x86_64)
+```
+
+**Environment**
+- Were you running elevated (`sudo` / Administrator)? [yes / no]
+- Terminal (e.g. Windows Terminal, iTerm2, GNOME Terminal, plain SSH):
+- On Linux, the value of `/proc/sys/kernel/yama/ptrace_scope`:
+- Target process (e.g. a game, browser, another script), if that matters:
+
+**Additional context**
+Add any other context about the problem here. If the target was a process you
+cannot share, a minimal script that reproduces the same behaviour helps a lot.

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,35 @@
+---
+name: Feature request
+about: Suggest an idea for this project
+title: ''
+labels: ''
+assignees: ''
+
+---
+
+**Is your feature request related to a problem? Please describe.**
+- A clear and concise description of what the problem is. Ex. I always have to
+  type [...] to do [...]
+- A clear and concise description of what you want to happen.
+- Any alternative commands or workflows you have considered.
+
+**Is not your feature request related to a problem? Please describe**
+A clear and concise description of how your feature can positively impact the
+project.
+
+**What would it look like?**
+If it is a new command or a new flag, sketch the session:
+
+```console
+picklock> mycommand 0x1000 --flag
+```
+
+**Is this Picklock or PyMemoryEditor?**
+Picklock is a client — it parses commands and formats results, while
+[PyMemoryEditor](https://github.com/JeanExtreme002/PyMemoryEditor) performs
+every read, write and scan. If the feature needs a memory capability that does
+not exist yet, it may belong upstream. Say which you think it is; being wrong
+is fine, the issue will be routed.
+
+**Additional context**
+Add any other context or screenshots about the feature request here.

.github/ISSUE_TEMPLATE/questioning.md

@@ -0,0 +1,34 @@
+---
+name: Questioning
+about: Ask a question about the project
+title: ''
+labels: question
+assignees: ''
+
+---
+
+**Did you check the built-in help? If so, please describe**
+Picklock documents itself: `help` lists every command, `help <command>` explains
+one in full, and `help types`, `help address` and `help scanning` cover what
+several commands share. If one of those was confusing, say which and how — that
+is a documentation bug worth fixing.
+
+**Describe your question**
+A clear and concise description of what you are trying to do.
+
+**What did you try?**
+The commands you ran and the output you got:
+
+```console
+picklock> ...
+```
+
+**Versions**
+Paste the output of `picklock --version`, if applicable.
+
+**Environment**
+- Were you running elevated (`sudo` / Administrator)? [yes / no]
+- On Linux, the value of `/proc/sys/kernel/yama/ptrace_scope`:
+
+**Additional context**
+Add any other context about your question here.

.github/dependabot.yml

@@ -0,0 +1,21 @@
+# https://docs.github.com/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file
+#
+# `open-pull-requests-limit: 0` disables routine version-update PRs (no weekly
+# bump churn). Dependabot security advisories still surface via the Security
+# tab and security-update PRs are unaffected by this limit, so a vulnerability
+# in PyMemoryEditor or an action remains visible.
+
+version: 2
+
+updates:
+  - package-ecosystem: "pip"
+    directory: "/"
+    schedule:
+      interval: "weekly"
+    open-pull-requests-limit: 0
+
+  - package-ecosystem: "github-actions"
+    directory: "/"
+    schedule:
+      interval: "weekly"
+    open-pull-requests-limit: 0

.github/labeler.yml

@@ -0,0 +1,48 @@
+# Path-based labels applied to PRs by .github/workflows/labeler.yml.
+# Uses actions/labeler@v5 match rules.
+
+# The command layer — where a new command or a change to an existing one lands.
+commands:
+  - changed-files:
+      - any-glob-to-any-file:
+          - "picklock/commands/**"
+
+# The shell itself: line parsing, dispatch, readline, the CLI front end.
+shell:
+  - changed-files:
+      - any-glob-to-any-file:
+          - "picklock/shell.py"
+          - "picklock/cli.py"
+
+# Everything that decides how a result looks on screen.
+output:
+  - changed-files:
+      - any-glob-to-any-file:
+          - "picklock/output.py"
+          - "picklock/valuetypes.py"
+
+# Any change inside the package.
+core:
+  - changed-files:
+      - any-glob-to-any-file:
+          - "picklock/**"
+
+tests:
+  - changed-files:
+      - any-glob-to-any-file:
+          - "tests/**"
+
+docs:
+  - changed-files:
+      - any-glob-to-any-file:
+          - "README.md"
+          - "CONTRIBUTING.md"
+          - "SECURITY.md"
+          - "CODE_OF_CONDUCT.md"
+
+ci:
+  - changed-files:
+      - any-glob-to-any-file:
+          - ".github/**"
+          - "Makefile"
+          - "codecov.yml"

.github/pull_request_template.md

@@ -0,0 +1,27 @@
+**Why is this PR necessary, what does it do?**
+
+<!-- 
+IMPORTANT! Explain the **motivation** for making this change: what existing
+problem the pull request solves or what new features it implements.
+-->
+
+**Checklist (complete all items)**:
+
+- [ ] Added tests as necessary.
+- [ ] There is no breaking change for existing features.
+
+**References:**
+
+<!-- (Nice to have) 
+Link tasks, issues, PRs that are related to this pull request, etc. 
+-->
+
+No references to be shared. 
+
+**Notes:**
+
+<!-- (Optional) 
+Explain some changes that can be useful when reviewing this pull request. 
+-->
+
+No notes to be shared. 

.github/workflows/delete-pr-branch.yml

@@ -0,0 +1,41 @@
+name: Delete PR branch
+
+on:
+  pull_request:
+    types: [closed]
+
+permissions:
+  contents: write
+
+jobs:
+  delete:
+    name: Delete head branch after PR close
+    if: github.event.pull_request.head.repo.full_name == github.repository
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/github-script@v7
+        with:
+          script: |
+            const pr = context.payload.pull_request;
+            const ref = pr.head.ref;
+
+            const protectedBranches = new Set(["main", "gh-pages"]);
+            if (protectedBranches.has(ref)) {
+              core.info(`Refusing to delete protected branch: ${ref}`);
+              return;
+            }
+
+            try {
+              await github.rest.git.deleteRef({
+                owner: context.repo.owner,
+                repo: context.repo.repo,
+                ref: `heads/${ref}`,
+              });
+              core.info(`Deleted branch: ${ref}`);
+            } catch (err) {
+              if (err.status === 422 || err.status === 404) {
+                core.info(`Branch already gone: ${ref}`);
+                return;
+              }
+              throw err;
+            }

.github/workflows/labeler.yml

@@ -0,0 +1,27 @@
+name: Labeler
+
+on:
+  pull_request_target:
+    types:
+      - opened
+      - synchronize
+      - reopened
+
+concurrency:
+  group: ${{ github.workflow }}-${{ github.event.number || github.ref }}
+  cancel-in-progress: true
+
+permissions:
+  contents: read
+  pull-requests: write
+
+jobs:
+  label:
+    name: Label PR by changed files
+    runs-on: ubuntu-latest
+    steps:
+      - name: Apply labels
+        uses: actions/labeler@v5
+        with:
+          configuration-path: .github/labeler.yml
+          sync-labels: true

.github/workflows/lint-pr-title.yml

@@ -0,0 +1,46 @@
+name: Lint PR title
+
+on:
+  pull_request_target:
+    types:
+      - opened
+      - edited
+      - synchronize
+      - reopened
+
+concurrency:
+  group: ${{ github.workflow }}-${{ github.event.number || github.ref }}
+  cancel-in-progress: true
+
+permissions:
+  pull-requests: read
+
+jobs:
+  lint:
+    name: Conventional commit title
+    runs-on: ubuntu-latest
+    steps:
+      - name: Lint PR title
+        uses: amannn/action-semantic-pull-request@v5
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+        with:
+          # Conventional commit types accepted in titles. Mirrors the set the
+          # PR labeler recognizes in .github/workflows/labeler.yml.
+          types: |
+            feat
+            fix
+            perf
+            refactor
+            revert
+            docs
+            ci
+            build
+            chore
+            test
+            style
+          # Subject must start lowercase and not end with a period.
+          subjectPattern: ^(?![A-Z])(?!.*\.$).+$
+          subjectPatternError: |
+            The subject "{subject}" found in "{title}" must start with a
+            lowercase letter and must not end with a period.

.github/workflows/publish.yml

@@ -0,0 +1,28 @@
+name: Publish to PyPI
+
+on:
+  release:
+    types: [published]
+
+jobs:
+  publish:
+    runs-on: ubuntu-latest
+    environment: pypi
+    permissions:
+      id-token: write  # Required for trusted publishing (OIDC)
+    steps:
+    - uses: actions/checkout@v4
+
+    - name: Set up Python
+      uses: actions/setup-python@v5
+      with:
+        python-version: '3.12'
+
+    - name: Install build tools
+      run: python -m pip install --upgrade pip build
+
+    - name: Build package
+      run: python -m build
+
+    - name: Publish to PyPI
+      uses: pypa/gh-action-pypi-publish@release/v1