Undocumented Forge platform behaviour, measured and worked around.
A one-line import at the top of a resolver file makes the whole resolver stop existing, and forge lint reports no issues. That is the shape of most of what is collected here.
Egress rules the backend ignores and the client enforces. Display conditions reading app properties nobody documented. A key-value store where FAIL_IF_EXISTS gives you a real lock and a TTL lease quietly does not. Each piece names the behaviour, shows the smallest thing that reproduces it, and gives the workaround that held up in production. Where Atlassian has since documented something, that is said. Where it is still undocumented, you get how it was confirmed, so you can check it yourself.
What Jira workflow validators could not do, and what it took to put an LLM behind a transition without sending your data anywhere.
Notes from building a Microsoft-Project-style planner inside Jira Cloud, on Forge, against limits that are not negotiable.
Undocumented Atlassian Forge behaviour that passes lint, passes deploy, and breaks anyway.
The problems that only appear after deploy: testing against the live product, a security scan that passes wrongly, and rate limits counted in points.