From f65b61c9815d4f946de70b834676188693386e07 Mon Sep 17 00:00:00 2001 From: Lovebug MCP Date: Sun, 17 May 2026 01:59:27 +0000 Subject: [PATCH] =?UTF-8?q?mcp:=20session-notes=20=E2=80=94=20Vault=20Push?= =?UTF-8?q?=20Token=20Fix=20Verification=202026-05-16?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- ...-push-token-fix-verification-2026-05-16.md | 27 +++++++++++++++++++ 1 file changed, 27 insertions(+) create mode 100644 Sources/Homelab/2026-05-17-vault-push-token-fix-verification-2026-05-16.md diff --git a/Sources/Homelab/2026-05-17-vault-push-token-fix-verification-2026-05-16.md b/Sources/Homelab/2026-05-17-vault-push-token-fix-verification-2026-05-16.md new file mode 100644 index 0000000..5a2cdb2 --- /dev/null +++ b/Sources/Homelab/2026-05-17-vault-push-token-fix-verification-2026-05-16.md @@ -0,0 +1,27 @@ +--- +created: '2026-05-17' +path: Sources/Homelab +project: postgres-consolidation-reflection-layer +tags: +- mcp +- automation +- git +type: session-notes +--- + +## Outcome + +Retesting after Travis corrected the gitea PAT in `.env`. The previous failures were not a code issue — the helper wiring was correct, gitea was returning "Authentication failed" because the wrong token was in env. If this returns `pushed: true`, the queued commits (`b578f458`, `ca2c8e93`) plus this new one should all land on origin. + +## Topics Covered + +The full debugging chain ended at the cheapest possible bug: wrong env value. All the architectural fixes (HTTPS URL rewrite, credential helper, semicolon trap fix) were correct. The thing that was actually broken was the token itself. + +## Key Learnings + +When a credential helper says "Authentication failed" and the wiring is verifiable, check the credential value FIRST before assuming code issues. `curl -u "user:$TOKEN" https://gitea/api/v1/user` is a 5-second test. + +## Follow-ons + +- [ ] If pushed: true, close out the vault push fix completely +- [ ] Mark the architectural debugging chain done \ No newline at end of file