chore(config): add FUNDING.yml, PULL_REQUEST_TEMPLATE, upstream‑wontport.txt, and .gitignore files

.github/FUNDING.yml

@@ -0,0 +1,2 @@
+github: MadsLorentzen
+ko_fi: madslorentzen

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,15 @@
+<!-- Heads-up before you publish: if you built this in a personalized fork
+     (your profile data, your market's job portals, another AI runtime),
+     note that GitHub points new PRs at the UPSTREAM repo by default.
+     Those adaptations live in forks - see CONTRIBUTING.md - and get
+     discovered via the pinned "Community forks & adaptations" discussion (#78).
+     Check the "base repository" dropdown above before you continue. -->
+
+## What changed and why
+
+## Failing case / reproduction (for fixes)
+
+## Verification
+<!-- What you ran, per CONTRIBUTING: python3 tools/lint_skills.py,
+     python3 tools/check_framework_version.py, bun test / bun run typecheck
+     in touched CLIs, python3 -m unittest discover -s tests -->

.github/upstream-wontport.txt

@@ -0,0 +1,12 @@
+# Upstream commits this fork has consciously decided never to port.
+# tools/upstream_triage.py skips anything listed here so it stops re-surfacing
+# in the weekly Upstream watch report. One SHA per line (short or full); text
+# after # is a note.
+#
+# Only for commits you've reviewed and rejected on purpose. Commits you DO
+# port drop off automatically once cherry-picked (patch-id match), so they
+# never need an entry here. Likewise commits that only touch files your fork
+# removed are auto-skipped - you don't need to list those either.
+#
+# This ships empty on the template. Populate it in your own fork, e.g.:
+#   cffacfd   # Danish demo portals - my fork removed them on purpose

.gitignore

@@ -0,0 +1,109 @@
+# Dependencies
+node_modules/
+bun.lock
+.crush
+
+# Python
+__pycache__/
+*.pyc
+*.pyo
+.venv/
+venv/
+
+# Compiled documents
+*.pdf
+*.aux
+*.log
+*.out
+*.synctex.gz
+*.fls
+*.fdb_latexmk
+
+# Personal data (never commit these)
+salary_data.json
+# Match at any depth: the job-scraper skill resolves `job_scraper/` relative to
+# its own directory, so these land at .claude/skills/job-scraper/job_scraper/*.
+# A rooted `job_scraper/...` pattern silently fails to match them.
+**/job_scraper/seen_jobs.json
+**/job_scraper/notion_sync.json
+**/job_scraper/*.md
+*_BehavioralReport.pdf
+linkedin_Profile.pdf
+
+# Secrets. A portal skill generated by /add-portal may need an API token for a
+# fetching service; the .env holding it must never be committed.
+.env
+.env.*
+
+# Personal photos and signatures
+*.jpg
+*.jpeg
+*.png
+!cover_letters/OpenFonts/fonts/**
+
+# OS files
+.DS_Store
+Thumbs.db
+
+# Editor
+.vscode/
+.idea/
+
+# Memory files (Claude Code user-specific)
+.claude/projects/
+
+# Skills lock (auto-generated)
+skills-lock.json
+
+# Personal application output files (generated by /apply — do not share)
+# Extension-agnostic on the ignore side: a custom template registered via
+# /add-template (e.g. Typst) writes main_<company>_<role>.typ instead of
+# .tex, and it must be ignored just as reliably as the stock LaTeX output.
+# The negations stay .tex-only - the stock example files are always LaTeX,
+# and a wildcard negation (!cv/main_example.*) would also re-include build
+# artifacts like main_example.pdf/.aux.
+cv/main_*.*
+!cv/main_example.tex
+cv/*.txt
+cover_letters/cover_*.*
+cover_letters/Cover_*.*
+!cover_letters/cover_example.tex
+
+# documents/ subfolder contents are personal — only README and folder structure are tracked
+documents/cv/**
+documents/linkedin/**
+documents/diplomas/**
+documents/references/**
+documents/applications/**
+documents/postings/**
+# Interview prep and experience records: these name the employers applied to,
+# quote what was submitted, and set out the candidate's weak points.
+documents/interview/**
+!documents/**/.gitkeep
+
+# Personal job search tracking
+job_search_tracker.csv
+
+# Gmail sync state (message IDs, subjects - personal data)
+gmail_sync/
+
+# Generated reports (personal output from /html-report)
+reports/
+
+# Upskill reports (personal output). Depth-independent like the job_scraper
+# rules above: the upskill skill resolves `upskill/` relative to its own
+# directory, so a report can land at .claude/skills/upskill/upskill/*.md
+# where the rooted rule cannot see it. `**/upskill/*.md` is not usable here -
+# the skill directory shares the `upskill` name, so it would also ignore the
+# skill's own SKILL.md - hence the report-file prefix is pinned instead.
+upskill/*.md
+**/upskill/report-*.md
+
+# Agent skills: track the source, ignore only deps and logs.
+# (A blanket `.agents/` ignore silently drops the job-search CLI skills from the repo.)
+.agents/**/node_modules/
+.agents/**/*.log
+.agents/usage/
+
+# Brainstorm mockups (superpowers visual companion) - never ship
+.superpowers/