<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"><channel><title>Leon’s engineering notes</title><link>https://leon-ai-workflows.pages.dev/engineering</link><description>Independent engineering: concrete problems, evidence and limits.</description><language>en</language><item><title>Why AI remediation advice isn't a SARIF fix</title><link>https://leon-ai-workflows.pages.dev/engineering/sarif-remediation</link><guid isPermaLink="true">https://leon-ai-workflows.pages.dev/engineering/sarif-remediation</guid><description>A prose recommendation broke SARIF validation. Here is the representation change, regression evidence and migration boundary in a merged AI-Infra-Guard contribution.</description></item><item><title>Preserving an MCP gateway catalog after empty OAuth discovery</title><link>https://leon-ai-workflows.pages.dev/engineering/mcp-empty-discovery</link><guid isPermaLink="true">https://leon-ai-workflows.pages.dev/engineering/mcp-empty-discovery</guid><description>An empty OAuth discovery result should not erase a saved catalog. This merged contribution preserves entries and checks retained aliases within their actual visibility scope.</description></item><item><title>Keeping Git metadata out of security scan inventories</title><link>https://leon-ai-workflows.pages.dev/engineering/git-scan-inventory</link><guid isPermaLink="true">https://leon-ai-workflows.pages.dev/engineering/git-scan-inventory</guid><description>Nested repositories, linked worktrees and scopes inside .git need explicit inventory boundaries. A merged contribution and the regressions behind it.</description></item></channel></rss>
