update ADRs

Author: riceyrice

docs/decisions/0001-use-atlassian-forge.md

@@ -10,7 +10,7 @@ Atlassian Marketplace.
 ## Decision Drivers
 
 - Overall requirement to quickly tick the box that Flagsmith has a Jira integration and offer MVP functionality which
-  can be iterated on later.
+  can be iterated on later
 
 ## Considered Options
 
@@ -37,4 +37,4 @@ capacity to scale to meet future requirements.
 
 ## Links
 
-- https://developer.atlassian.com/developer-guide/cloud-development-options/
+- <https://developer.atlassian.com/developer-guide/cloud-development-options/>

docs/decisions/0002-use-current-forge-runtime.md

@@ -1,6 +1,6 @@
 # Use Current Forge Runtime
 
-- Status: Accepted
+- Status: Superseded by [Use UI Kit 2](0004-use-ui-kit-2.md)
 
 ## Context and Problem Statement
 
@@ -10,7 +10,7 @@ calls, storage, authorisation, etc.
 ## Decision Drivers
 
 - Overall requirement to quickly tick the box that Flagsmith has a Jira integration and offer MVP functionality which
-  can be iterated on later.
+  can be iterated on later
 
 ## Considered Options
 
@@ -38,4 +38,4 @@ reliable, development without ruling out a future change of runtime.
 
 ## Links
 
-- https://developer.atlassian.com/platform/forge/runtime-reference/native-nodejs-runtime/
+- <https://developer.atlassian.com/platform/forge/runtime-reference/native-nodejs-runtime/>

docs/decisions/0003-use-ui-kit.md

@@ -1,6 +1,6 @@
 # Use UI Kit
 
-- Status: Accepted
+- Status: Superseded by [Use UI Kit 2](0004-use-ui-kit-2.md)
 
 ## Context and Problem Statement
 
@@ -10,7 +10,7 @@ project settings, issue panel, menus, modals, etc).
 ## Decision Drivers
 
 - Overall requirement to quickly tick the box that Flagsmith has a Jira integration and offer MVP functionality which
-  can be iterated on later.
+  can be iterated on later
 
 ## Considered Options
 
@@ -39,7 +39,7 @@ transition.
 
 ## Links
 
-- https://developer.atlassian.com/platform/forge/ui-kit-components/
-- https://developer.atlassian.com/platform/forge/ui-kit-2/
-- https://developer.atlassian.com/platform/forge/custom-ui/iframe/
-- https://trello.com/b/z2GIJ3xD/forge-roadmap-for-developers
+- <https://developer.atlassian.com/platform/forge/ui-kit-components/>
+- <https://developer.atlassian.com/platform/forge/ui-kit-2/>
+- <https://developer.atlassian.com/platform/forge/custom-ui/iframe/>
+- <https://trello.com/b/z2GIJ3xD/forge-roadmap-for-developers>

docs/decisions/0004-use-ui-kit-2.md

@@ -0,0 +1,44 @@
+# Use UI Kit 2 (and Node 22 Runtime)
+
+- Status: Accepted
+
+## Context and Problem Statement
+
+Need to choose a new JavaScript runtime that provides libraries for Jira and Flagsmith REST API
+calls, storage, authorisation, etc.
+
+Need to choose a new JavaScript library for UI components (text, tables, inputs, buttons, etc) and Jira UI (app settings,
+project settings, issue panel, etc).
+
+## Decision Drivers
+
+- Forge Legacy Runtime reached end-of-life in Feb 2024
+- UI Kit 1 reached end-of-life in Feb 2024
+- Overall requirement for fastest route to maintain service
+
+## Considered Options
+
+- Forge Node Runtime 20 and 22 (generally available)
+- UI Kit 2 (updated library, generally available)
+- Custom UI (provide own UI components, use bridge to Jira components)
+
+## Decision Outcome
+
+Chosen option: "UI Kit 2", because it offers the least worst route to upgrading the existing UI. "Node 22 Runtime" because it is the current LTS, probably supported by Forge (documentation is contradictory but intention is there), and found to work in testing.
+
+### Positive Consequences
+
+- Reduced effort compared to Custom UI as UI Kit 2 provides pre-built UI components, similar to those currently used, styled to fit with Jira
+- Greater compatibility as UI Kit 2 is expected to work well with Jira styling features such as dark mode, while providing finer style control than UI Kit 1
+- UI Kit 2 uses real React (16) rather than React-like hooks, so can use more standard techniques  
+
+### Negative Consequences
+
+- Some quite painful changes from UI Kit 1 in terms of component changes, React hook changes, and bridging between frontend and backend execution, but this is unavoidable
+
+## Links
+
+- <https://developer.atlassian.com/platform/forge/function-reference/nodejs-runtime/>
+- <https://developer.atlassian.com/platform/forge/ui-kit/components/>
+- <https://developer.atlassian.com/platform/forge/custom-ui/iframe/>
+- <https://ecosystem.atlassian.net/jira/polaris/projects/ROADMAP/ideas>