docs(framework): complete TSYSGroupAIOS adoption + tracker/IaC rules [#454]

Bring the framework's global baseline (BASELINE-PROMPT.md, PATTERNS.md,
ADOPTING.md) into the repo — AGENTS.md referenced them but the files were
missing. AGENTS.md gains three rules adopted this session: TDD & Linting
(mandatory at the Ansible/IaC transition), IaC codification shadow-tracking
(every manual fleet change same-day ticketed to #454), and Redmine tracker
discipline (Support not Bug — the CLI default created nine misfiled
tickets, now corrected). Q10 records the direct-push vs PR conflict for
the founder to rule on.

💘 Generated with Crush

Assisted-by: Crush:glm-5.2

questions-v2.md

@@ -51,3 +51,10 @@
 - **Answer:** _(human)_
 - **Decision:** _(human/agent)_
 - **Synthesized to:** —
+
+### Q10. Git flow: direct-push vs PR workflow (TSYSGroupAIOS conflict)?
+- **Context:** Template says "once work leaves the workstation, it goes through a PR" (tea CLI). This project's policy is ALWAYS commit+push directly to origin/main. Founder's own rule, reinforced all session.
+- **Question:** Keep direct-push for PFVCluster (ops repo, solo operator), adopt PRs for playbook code post-IaC-transition, or hybrid?
+- **Answer:** _(human)_
+- **Decision:** _(human/agent)_
+- **Synthesized to:** —