Release 2.2.2.202608291620

2.2.2.202608291620/p2.index

@@ -1,4 +1,4 @@
-#Sat Aug 29 17:54:45 CEST 2026
+#Sat Aug 29 18:20:23 CEST 2026
 artifact.repository.factory.order=artifacts.xml.xz,artifacts.xml,\!
 metadata.repository.factory.order=content.xml.xz,content.xml,\!
 version=1

README.md

@@ -108,6 +108,8 @@ GET http://127.0.0.1:3000/health
 
 **Window > Preferences > ABAP MCP Server** — change the server port, enable auto-start when you connect to a project, or set the full-source line threshold for element reads (default: 200 lines).
 
+The token buttons sit in the **ABAP MCP Server** view, not on the preference page. The **Copy client config** button copies the configuration block, with the bearer token, to the clipboard. The **Regenerate token** button creates a new token when the token leaks. The server stores the token and reuses it on every later start. The token survives an Eclipse restart, so the client configuration stays valid.
+
 
 ## Multi-System Support
 
@@ -124,6 +126,15 @@ When multiple ABAP projects are connected, pass `systemId` (the Eclipse project
 The `systemId` description in every tool's schema is dynamically populated from the live registry, so the AI always knows which systems are available.
 
 
+## Access Mode
+
+Each connected system has an access mode: write or read-only. A new connection starts in write. The mode lives in the third column of the **ABAP MCP Server** view table, next to Project and Status. The **Toggle Read-Only** button flips the mode of the selected system.
+
+A read-only system refuses the 9 write tools and makes no ADT call against SAP. Every other tool works on a read-only system. The 9 write tools are `sap_push_source`, `sap_push_source_from_file`, `sap_push_element`, `sap_create_object`, `sap_activate`, `sap_lock`, `sap_unlock`, `sap_transport_create`, and `sap_transport_release`.
+
+The mode survives an Eclipse restart and a reconnect. The plugin stores the mode per project name. `sap_list_systems` shows the mode of each connected system.
+
+
 ## MCP Tools
 
 The plugin exposes 27 tools covering the full ABAP development workflow:
@@ -148,7 +159,7 @@ The plugin exposes 27 tools covering the full ABAP development workflow:
 | `sap_push_source` | Write source code from context to an ABAP object in SAP — runs the full lock → write → unlock → activate pipeline in one call |
 | `sap_push_source_from_file` | Save a local file back to SAP through the same one-call pipeline |
 | `sap_push_element` | Write one member block. The server merges the block into the current full source and pushes it — the model never holds the class. CLAS, INTF, PROG, FUGR |
-| `sap_pretty_print` | Format (pretty-print) ABAP source via the server formatter |
+| `sap_pretty_print` | Format (pretty-print) ABAP source through the ADT pretty-printer service. The tool takes only the source and uses the server's stored settings |
 
 ### Lifecycle
 

compositeArtifacts.xml

@@ -4,10 +4,10 @@
     type='org.eclipse.equinox.internal.p2.artifact.repository.CompositeArtifactRepository'
     version='1.0.0'>
   <properties size='2'>
-    <property name='p2.timestamp' value='1788018889'/>
+    <property name='p2.timestamp' value='1788020429'/>
     <property name='p2.compressed' value='false'/>
   </properties>
   <children size='1'>
-    <child location='2.2.2.202608291554/'/>
+    <child location='2.2.2.202608291620/'/>
   </children>
 </repository>

compositeContent.xml

@@ -4,10 +4,10 @@
     type='org.eclipse.equinox.internal.p2.metadata.repository.CompositeMetadataRepository'
     version='1.0.0'>
   <properties size='2'>
-    <property name='p2.timestamp' value='1788018889'/>
+    <property name='p2.timestamp' value='1788020429'/>
     <property name='p2.compressed' value='false'/>
   </properties>
   <children size='1'>
-    <child location='2.2.2.202608291554/'/>
+    <child location='2.2.2.202608291620/'/>
   </children>
 </repository>