refactor: init

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -1,48 +0,0 @@
-name: Bug report
-description: Report a file that fails to unpack, unpacks incorrectly, or crashes senbei
-title: "[Bug]: "
-labels: [bug]
-body:
-  - type: markdown
-    attributes:
-      value: |
-        Thanks for the report. Attaching the protected input file helps us
-        better diagnose the issue. Please only attach files you are
-        authorized to share.
-  - type: textarea
-    id: symptom
-    attributes:
-      label: What happened?
-      description: The command you ran and the output/error you got. Use -v/--verbose and paste the stage log if unpacking failed midway.
-      placeholder: "senbei app.exe -> error: ..."
-    validations:
-      required: true
-  - type: textarea
-    id: expected
-    attributes:
-      label: What did you expect?
-      placeholder: "A runnable unpacked image at unpack\\app.unpack.exe"
-    validations:
-      required: true
-  - type: input
-    id: version
-    attributes:
-      label: Senbei version
-      description: Output of `senbei -V`
-    validations:
-      required: true
-  - type: textarea
-    id: fileinfo
-    attributes:
-      label: About the input file
-      description: |
-        Without attaching it: is it an EXE or DLL? 32-bit or 64-bit? Managed
-        (.NET) or native? Roughly how large? Does it have a `._` companion
-        file next to it?
-  - type: checkboxes
-    id: legal
-    attributes:
-      label: Confirmation
-      options:
-        - label: I am authorized to analyze and share the attached file(s), and I understand attachments are removed after investigation.
-          required: true

.github/ISSUE_TEMPLATE/config.yml

@@ -1 +0,0 @@
-blank_issues_enabled: false

.github/ISSUE_TEMPLATE/feature_request.yml

@@ -1,25 +0,0 @@
-name: Feature request
-description: Suggest an improvement or support for a new layout
-title: "[Feature]: "
-labels: [enhancement]
-body:
-  - type: markdown
-    attributes:
-      value: |
-        For a new Crackproof layout, attaching a sample protected file helps
-        us better understand the request. Please only attach files you are
-        authorized to share.
-  - type: textarea
-    id: idea
-    attributes:
-      label: What would you like?
-      description: The problem it solves for you, and any layout details you can share.
-    validations:
-      required: true
-  - type: checkboxes
-    id: legal
-    attributes:
-      label: Confirmation
-      options:
-        - label: This request is for lawful research/interoperability use, and I am authorized to share any file I attach.
-          required: true

.github/workflows/ci.yml

@@ -1,99 +0,0 @@
-name: CI
-
-on:
-  push:
-    branches: [main]
-  pull_request:
-
-env:
-  CARGO_TERM_COLOR: always
-
-jobs:
-  fmt:
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@v4
-      - run: cargo fmt --all -- --check
-
-  clippy:
-    runs-on: windows-latest
-    steps:
-      - uses: actions/checkout@v4
-      - run: cargo clippy --all-targets -- -D warnings
-
-  test:
-    # The test suite exercises Windows path semantics, so it runs on Windows.
-    # The golden corpus (samples/) is user-managed and absent on CI; the
-    # samples test is a no-op pass there by design.
-    runs-on: windows-latest
-    steps:
-      - uses: actions/checkout@v4
-      - run: cargo test --release
-
-  check-portable:
-    # Build-only portability gate: non-Windows host and the wasm target the
-    # web build uses. Clippy runs here too, not just on Windows: the platform
-    # `cfg` branches (the POSIX `localtime_r` path, the non-Windows stubs) are
-    # invisible to the Windows clippy job, so without this they are never
-    # linted at all.
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@v4
-      - run: cargo clippy --all-targets -- -D warnings
-      - run: cargo check --target wasm32-unknown-unknown
-
-  cli:
-    strategy:
-      matrix:
-        include:
-          - os: windows-latest
-            target: x86_64-pc-windows-msvc
-            bin: senbei.exe
-          - os: ubuntu-latest
-            target: x86_64-unknown-linux-gnu
-            bin: senbei
-    runs-on: ${{ matrix.os }}
-    steps:
-      - uses: actions/checkout@v4
-      - run: cargo build --release --locked
-      - name: Package senbei-<version>-<target>
-        shell: bash
-        run: |
-          set -euo pipefail
-          version=$(grep -m1 '^version' Cargo.toml | cut -d'"' -f2)
-          name="senbei-$version-${{ matrix.target }}"
-          mkdir -p "stage/$name"
-          cp "target/release/${{ matrix.bin }}" "stage/$name/"
-          cp LICENSE "stage/$name/"
-          awk '/^## Legal notice and intended use/{f=1} f && /^## / && !/Legal notice/{exit} f' \
-            README.md > "stage/$name/LEGAL-NOTICE.md"
-          echo "package=$name" >> "$GITHUB_ENV"
-      # upload-artifact always wraps the upload in its own zip, so the staged
-      # directory is uploaded loose — pre-compressing here would nest archives.
-      # The download is already <package>.zip with the folder inside.
-      - uses: actions/upload-artifact@v4
-        with:
-          name: ${{ env.package }}
-          path: stage/
-          retention-days: 14
-
-  web:
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@v4
-      - run: cargo install wasm-pack --locked
-      # `-- --locked` forwards to cargo: web/Cargo.lock is committed on
-      # purpose, so the wasm build must be pinned by it rather than silently
-      # re-resolving (which is how it drifted out of sync with the manifest).
-      - run: wasm-pack build --target web --release -- --locked
-        working-directory: web
-      - uses: actions/upload-artifact@v4
-        with:
-          name: senbei-web
-          path: |
-            web/index.html
-            web/app.js
-            web/worker.js
-            web/style.css
-            web/pkg/
-          retention-days: 14

.github/workflows/release.yml

@@ -1,79 +0,0 @@
-name: Release
-
-# Publishing a GitHub release:
-#  - cli-assets builds the Windows and Linux CLI binaries and attaches
-#    senbei-<version>-<target>.zip (binary + LICENSE + the legal
-#    notice extracted from README.md) to the release.
-#  - deploy-web rebuilds the browser app and pushes it to Cloudflare Pages
-#    (https://senbei.pages.dev). Requires two repository secrets:
-#    CLOUDFLARE_API_TOKEN (Pages:Edit) and CLOUDFLARE_ACCOUNT_ID. The Pages
-#    project is `senbei`; direct-upload projects default to `main` as the
-#    production branch, which `--branch=main` targets.
-
-on:
-  release:
-    types: [published]
-
-permissions:
-  contents: read
-
-jobs:
-  cli-assets:
-    permissions:
-      contents: write # attach assets to the release
-    strategy:
-      matrix:
-        include:
-          - os: windows-latest
-            target: x86_64-pc-windows-msvc
-            bin: senbei.exe
-          - os: ubuntu-latest
-            target: x86_64-unknown-linux-gnu
-            bin: senbei
-    runs-on: ${{ matrix.os }}
-    steps:
-      - uses: actions/checkout@v4
-      - run: cargo build --release --locked
-      - name: Package senbei-<version>-<target>
-        shell: bash
-        run: |
-          set -euo pipefail
-          version=$(grep -m1 '^version' Cargo.toml | cut -d'"' -f2)
-          name="senbei-$version-${{ matrix.target }}"
-          mkdir -p "stage/$name"
-          cp "target/release/${{ matrix.bin }}" "stage/$name/"
-          cp LICENSE "stage/$name/"
-          awk '/^## Legal notice and intended use/{f=1} f && /^## / && !/Legal notice/{exit} f' \
-            README.md > "stage/$name/LEGAL-NOTICE.md"
-          # Release assets are served as-is (unlike CI artifacts, which the
-          # upload action always re-zips), so the archive is created here.
-          # Zip on every OS, matching the CI artifacts; 7z is preinstalled on
-          # both windows-latest and ubuntu-latest.
-          (cd stage && 7z a "$name.zip" "$name" > /dev/null)
-          echo "package=$name" >> "$GITHUB_ENV"
-      - name: Attach to release
-        shell: bash
-        env:
-          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-        run: gh release upload "${{ github.event.release.tag_name }}" "stage/${{ env.package }}".* --clobber
-
-  deploy-web:
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@v4
-      - run: cargo install wasm-pack --locked
-      # `-- --locked` forwards to cargo: web/Cargo.lock is committed on
-      # purpose, so the wasm build must be pinned by it rather than silently
-      # re-resolving (which is how it drifted out of sync with the manifest).
-      - run: wasm-pack build --target web --release -- --locked
-        working-directory: web
-      - name: Stage static site
-        run: |
-          mkdir dist
-          cp web/index.html web/app.js web/worker.js web/style.css dist/
-          cp -r web/pkg dist/pkg
-      - uses: cloudflare/wrangler-action@v3
-        with:
-          apiToken: ${{ secrets.CLOUDFLARE_API_TOKEN }}
-          accountId: ${{ secrets.CLOUDFLARE_ACCOUNT_ID }}
-          command: pages deploy dist --project-name=senbei --branch=main