FastForm Phases 0–4: cookie/parse/match/compile/classify/transport pipeline

.gitignore

@@ -0,0 +1,5 @@
+config/cookies.txt
+__pycache__/
+*.pyc
+.DS_Store
+fixtures/*.curl.txt

config/answers.toml

@@ -0,0 +1,17 @@
+# Answer bank. Each entry matches a question by text and supplies a value.
+#   match — list of phrases; scored against question text (see fastform/match.py)
+#   regex — optional; a hit here is an exact match, outranking everything
+#   value — what gets submitted
+
+[[answer]]
+match = ["full name", "your name", "name"]
+value = "Test Person"
+
+[[answer]]
+match = ["email address", "email"]
+regex = "e-?mail"
+value = "test@example.com"
+
+[[answer]]
+match = ["phone number", "phone", "mobile"]
+value = "0800000000"

config/profile.toml

@@ -0,0 +1,22 @@
+# Runtime configuration.
+
+[chrome]
+# Which Chrome profile's cookies to submit with. REQUIRED before any real run —
+# the tool refuses to guess, because picking the wrong profile submits as the
+# wrong person. Leave unset until you know which Google account competes.
+#
+# To see the choices, run:
+#   python3 -c "from fastform import cookies; [print(f'{p.name}: {e}') for p,e in cookies.resolve_accounts()]"
+#
+# That prints each profile with the account it is signed into. Then set:
+#   profile = "Profile 1"
+#
+# Identified on this machine so far:
+#   Profile 1  ->  student@example.com
+#   Profile 5  ->  personal@example.com
+#
+# NEITHER is the competition account? Sign it into any Chrome profile first,
+# then re-run the command above — a freshly signed-in profile shows up there
+# and can be pinned like any other.
+
+# profile =