abapgit-agent 1.14.5 → 1.15.0

package/abap/guidelines/abapgit.md

@@ -6,9 +6,10 @@ parent: ABAP Coding Guidelines
 grand_parent: ABAP Development
 ---
 
-# abapGit Object XML Metadata
+# abapGit XML Metadata — CLAS, INTF, PROG
 
-Each ABAP object requires an XML metadata file for abapGit to understand how to serialize/deserialize it. This guide provides templates for common object types.
+This guide covers objects that have **both a source file and an XML metadata file**.
+For objects with no source file (XML only), see `abapgit-agent ref --topic abapgit-xml-only`.
 
 ## QUICK REFERENCE
 
@@ -16,19 +17,16 @@ Each ABAP object requires an XML metadata file for abapGit to understand how to
 File Type          | ABAP File                    | XML File
 -------------------|------------------------------|-------------------
 Class              | zcl_*.clas.abap              | zcl_*.clas.xml
-Test Class         | zcl_*.clas.testclasses.abap | zcl_*.clas.xml
-Interface          | zif_*.intf.abap             | zif_*.intf.xml
-Program            | z*.prog.abap                | z*.prog.xml
-CDS View (DDLS)    | zc_*.ddls.asddls            | zc_*.ddls.xml
-Table (TABL)       | (no .abap file)             | z*.tabl.xml
-Structure (STRU)   | (no .abap file)             | z*.stru.xml
-Data Element (DTEL)| (no .abap file)             | z*.dtel.xml
-Table Type (TTYP)  | (no .abap file)             | z*.ttyp.xml
+Test Class         | zcl_*.clas.testclasses.abap  | zcl_*.clas.xml
+Interface          | zif_*.intf.abap              | zif_*.intf.xml
+Program            | z*.prog.abap                 | z*.prog.xml
+CDS View (DDLS)    | zc_*.ddls.asddls             | zc_*.ddls.xml
+CDS Access Control | zc_*.dcls.asdcls             | zc_*.dcls.xml
+Function Group     | z*fugr*.abap (6 files)       | z*.fugr.xml
 ```
 
-> **XML-only objects (TABL, STRU, DTEL, TTYP)** have **no ABAP source file**. abapGit serializes
-> them as XML metadata only. When using `--files`, pass the `.xml` file directly:
-> `abapgit-agent pull --files abap/zmy_table.tabl.xml --sync-xml`
+> **XML-only objects** (TABL, STRU, DTEL, TTYP, DOMA, MSAG) have **no ABAP source file** and are not covered here.
+> See `abapgit-agent ref --topic abapgit-xml-only`.
 
 > **CRITICAL: Always write XML files with a UTF-8 BOM (`\ufeff`) as the very first character**, before `<?xml ...`.
 > Without the BOM, abapGit shows the object as **"M" (modified)** after every pull because the
@@ -37,7 +35,7 @@ Table Type (TTYP)  | (no .abap file)             | z*.ttyp.xml
 > **CRITICAL: Only include fields that abapGit's serializer actually writes. Never add fields with
 > default values.** Extra fields cause a permanent "M" (modified) diff. Follow the exact templates below.
 
-**Searchable keywords**: class xml, interface xml, table xml, cds xml, test class, exposure, serializer, abapgit
+**Searchable keywords**: class xml, interface xml, program xml, cds view xml, ddls, dcls, access control xml, function group xml, fugr, test class, exposure, serializer, abapgit
 
 ## Why XML Metadata?
 
@@ -244,203 +242,9 @@ abapGit's serializer **omits fields that have their default value**. Writing ext
 
 ---
 
-### Table (TABL)
-
-**Filename**: `src/zmy_table.tabl.xml`
-
-> **XML-only object** — no `.abap` source file. Pull with: `pull --files src/zmy_table.tabl.xml`
-
-```xml
-<?xml version="1.0" encoding="utf-8"?>
-<abapGit version="v1.0.0" serializer="LCL_OBJECT_TABL" serializer_version="v1.0.0">
- <asx:abap xmlns:asx="http://www.sap.com/abapxml" version="1.0">
-  <asx:values>
-   <DD02V>
-    <TABNAME>ZMY_TABLE</TABNAME>
-    <DDLANGUAGE>E</DDLANGUAGE>
-    <TABCLASS>TRANSP</TABCLASS>
-    <DDTEXT>Description of the table</DDTEXT>
-    <CONTFLAG>A</CONTFLAG>
-   </DD02V>
-  </asx:values>
- </asx:abap>
-</abapGit>
-```
-
-**Key Fields**:
-- `TABNAME`: Table name
-- `DDTEXT`: Description (**not** `DESCRIPT`)
-- `TABCLASS`: `TRANSP`=Transparent (most common), `POOL`, `CLUSTER`
-- `CONTFLAG`: Delivery class — `A`=Application, `C`=Customizing, `S`=System, `G`=Customizing protected
-
-**Note**: When abapGit serializes an existing table it also writes `<DD09L>` (technical settings) and `<DD03P_TABLE>` (field definitions). These sections are generated automatically from the ABAP Dictionary on pull — you only need the `<DD02V>` header when creating a new table. After the first pull the XML will be expanded with those sections.
-
-**`DD03P` field-level rules** (apply when editing an existing table XML that includes `<DD03P_TABLE>`):
-
-| Rule | Detail |
-|---|---|
-| `SHLPORIGIN` | Include `<SHLPORIGIN>D</SHLPORIGIN>` on fields where the Dictionary provides a value help (e.g. fields with a domain that has fixed values or a search help). Omit on fields with no value help. |
-| Field order for raw-type fields | For fields with no `ROLLNAME` (raw type, e.g. `CHAR`, `NUMC`), the serializer writes `<MASK>` **before** `<DDTEXT>`. For fields with a `ROLLNAME`, only `ROLLNAME` appears (no `MASK` or `DDTEXT`). |
-
-**Why this matters**: Missing `SHLPORIGIN` or wrong `MASK`/`DDTEXT` order causes a permanent diff between git and the system-serialized XML.
-
-#### Text Tables and Foreign Keys
-
-A **text table** stores translatable texts for another table (the "main table"). It shares the same key fields as the main table plus a language field (`SPRAS` with data element `SPRAS`, or `LANGU` with data element `LANGU`).
-
-**How to recognise a text table relationship in the XML:**
-- `<DD09L>` has `<UEBERSETZ>X</UEBERSETZ>` — marks this table as a text table
-- `<DD08V>` has `<FRKART>TEXT</FRKART>` — marks the foreign key as a text-table relationship (ordinary foreign keys omit this field)
-
-**Three sections required in the text table XML:**
-
-| Section | Purpose |
-|---|---|
-| `DD03P_TABLE` | Field definitions — same key fields as main table + language field + text fields |
-| `DD05M_TABLE` | Foreign key field mappings — one entry per key field of the main table (excluding the language field) |
-| `DD08V_TABLE` | Foreign key relationship — one entry with `FRKART>TEXT` |
-
-**`DD03P` rules for the text table:**
-- First key field (`MANDT`) must have `<CHECKTABLE>` pointing to the main table and `<SHLPORIGIN>P</SHLPORIGIN>`
-- Language field (`SPRAS` or `LANGU`) gets `<SHLPORIGIN>D</SHLPORIGIN>` (added by serializer after activation — omit when writing manually)
-
-**`DD05M` rules:**
-- `FIELDNAME` = the anchor field in the text table (typically `MANDT` — the first key field)
-- `FORTABLE` = text table name
-- `FORKEY` = key field name in the main table
-- `CHECKFIELD` = same as `FORKEY`
-- `CHECKTABLE` = main table name
-- `PRIMPOS` = position sequence (0001, 0002, …)
-- `DOMNAME` / `DATATYPE` = domain and type of the check field (omit `DOMNAME` if unknown — serializer fills it in)
-
-**`DD08V` rules:**
-- `FIELDNAME` = same anchor field as used in `DD05M` (typically `MANDT`)
-- `CHECKTABLE` = main table name
-- `FRKART` = `TEXT` (text table) or omit (ordinary foreign key)
-- `CARD` = `CN` (n:1 cardinality)
-- `CARDLEFT` = `1`
-
-**Example — text table `ZMY_TABLE_T` for main table `ZMY_TABLE` (keys: MANDT, ID1, ID2):**
-
-```xml
-<?xml version="1.0" encoding="utf-8"?>
-<abapGit version="v1.0.0" serializer="LCL_OBJECT_TABL" serializer_version="v1.0.0">
- <asx:abap xmlns:asx="http://www.sap.com/abapxml" version="1.0">
-  <asx:values>
-   <DD02V>
-    <TABNAME>ZMY_TABLE_T</TABNAME>
-    <DDLANGUAGE>E</DDLANGUAGE>
-    <TABCLASS>TRANSP</TABCLASS>
-    <CLIDEP>X</CLIDEP>
-    <DDTEXT>My Table: Texts</DDTEXT>
-    <CONTFLAG>C</CONTFLAG>
-   </DD02V>
-   <DD09L>
-    <TABNAME>ZMY_TABLE_T</TABNAME>
-    <AS4LOCAL>A</AS4LOCAL>
-    <TABKAT>0</TABKAT>
-    <TABART>APPL0</TABART>
-    <UEBERSETZ>X</UEBERSETZ>
-    <BUFALLOW>N</BUFALLOW>
-   </DD09L>
-   <DD03P_TABLE>
-    <DD03P>
-     <FIELDNAME>MANDT</FIELDNAME>
-     <KEYFLAG>X</KEYFLAG>
-     <ROLLNAME>MANDT</ROLLNAME>
-     <CHECKTABLE>ZMY_TABLE</CHECKTABLE>
-     <ADMINFIELD>0</ADMINFIELD>
-     <NOTNULL>X</NOTNULL>
-     <SHLPORIGIN>P</SHLPORIGIN>
-     <COMPTYPE>E</COMPTYPE>
-    </DD03P>
-    <DD03P>
-     <FIELDNAME>ID1</FIELDNAME>
-     <KEYFLAG>X</KEYFLAG>
-     <ROLLNAME>ZMY_ID1</ROLLNAME>
-     <ADMINFIELD>0</ADMINFIELD>
-     <NOTNULL>X</NOTNULL>
-     <COMPTYPE>E</COMPTYPE>
-    </DD03P>
-    <DD03P>
-     <FIELDNAME>ID2</FIELDNAME>
-     <KEYFLAG>X</KEYFLAG>
-     <ROLLNAME>ZMY_ID2</ROLLNAME>
-     <ADMINFIELD>0</ADMINFIELD>
-     <NOTNULL>X</NOTNULL>
-     <COMPTYPE>E</COMPTYPE>
-    </DD03P>
-    <DD03P>
-     <FIELDNAME>SPRAS</FIELDNAME>
-     <KEYFLAG>X</KEYFLAG>
-     <ROLLNAME>SPRAS</ROLLNAME>
-     <ADMINFIELD>0</ADMINFIELD>
-     <NOTNULL>X</NOTNULL>
-     <COMPTYPE>E</COMPTYPE>
-    </DD03P>
-    <DD03P>
-     <FIELDNAME>DESCRIPTION</FIELDNAME>
-     <ROLLNAME>ZMY_DESCRIPTION</ROLLNAME>
-     <ADMINFIELD>0</ADMINFIELD>
-     <COMPTYPE>E</COMPTYPE>
-    </DD03P>
-   </DD03P_TABLE>
-   <DD05M_TABLE>
-    <DD05M>
-     <FIELDNAME>MANDT</FIELDNAME>
-     <FORTABLE>ZMY_TABLE_T</FORTABLE>
-     <FORKEY>MANDT</FORKEY>
-     <CHECKTABLE>ZMY_TABLE</CHECKTABLE>
-     <CHECKFIELD>MANDT</CHECKFIELD>
-     <PRIMPOS>0001</PRIMPOS>
-     <DOMNAME>MANDT</DOMNAME>
-     <DATATYPE>CLNT</DATATYPE>
-    </DD05M>
-    <DD05M>
-     <FIELDNAME>MANDT</FIELDNAME>
-     <FORTABLE>ZMY_TABLE_T</FORTABLE>
-     <FORKEY>ID1</FORKEY>
-     <CHECKTABLE>ZMY_TABLE</CHECKTABLE>
-     <CHECKFIELD>ID1</CHECKFIELD>
-     <PRIMPOS>0002</PRIMPOS>
-     <DATATYPE>CHAR</DATATYPE>
-    </DD05M>
-    <DD05M>
-     <FIELDNAME>MANDT</FIELDNAME>
-     <FORTABLE>ZMY_TABLE_T</FORTABLE>
-     <FORKEY>ID2</FORKEY>
-     <CHECKTABLE>ZMY_TABLE</CHECKTABLE>
-     <CHECKFIELD>ID2</CHECKFIELD>
-     <PRIMPOS>0003</PRIMPOS>
-     <DATATYPE>CHAR</DATATYPE>
-    </DD05M>
-   </DD05M_TABLE>
-   <DD08V_TABLE>
-    <DD08V>
-     <FIELDNAME>MANDT</FIELDNAME>
-     <CHECKTABLE>ZMY_TABLE</CHECKTABLE>
-     <FRKART>TEXT</FRKART>
-     <CARD>CN</CARD>
-     <CARDLEFT>1</CARDLEFT>
-    </DD08V>
-   </DD08V_TABLE>
-  </asx:values>
- </asx:abap>
-</abapGit>
-```
-
-**Key rules:**
-- Always activate the main table **before** the text table — the foreign key check requires the main table to exist
-- Language field can be `SPRAS` (data element `SPRAS`) or `LANGU` (data element `LANGU`) — both are recognised by the system
-- For an **ordinary foreign key** (not a text table): same `DD05M`/`DD08V` structure, but omit `<FRKART>TEXT</FRKART>` from `DD08V`
-
----
-
 ### CDS View / View Entity (DDLS)
 
-**Filename**: `src/zc_my_view.ddls.xml`
-
-The XML format is identical for both types — only `SOURCE_TYPE` differs:
+**Files**: `src/zc_my_view.ddls.asddls` (source) + `src/zc_my_view.ddls.xml` (metadata)
 
 ```xml
 <?xml version="1.0" encoding="utf-8"?>
@@ -458,121 +262,42 @@ The XML format is identical for both types — only `SOURCE_TYPE` differs:
 </abapGit>
 ```
 
-- `SOURCE_TYPE W` → View Entity (`define view entity`, modern, **use by default**)
-- `SOURCE_TYPE V` → View (`define view` + `@AbapCatalog.sqlViewName`, legacy — only if explicitly requested)
+- `SOURCE_TYPE W` → View Entity (`define view entity`, modern — **use by default**)
+- `SOURCE_TYPE V` → View (`define view` + `@AbapCatalog.sqlViewName`, legacy)
 
-→ For DDL source syntax and full guidance: `abapgit-agent ref --topic cds-abapgit`
+→ For DDL source syntax: `abapgit-agent ref --topic cds-abapgit`
 
 ---
 
-### Data Element (DTEL)
-
-**Filename**: `src/zmy_dtel.dtel.xml`
+### CDS Access Control (DCLS)
 
-> **XML-only object** — no `.abap` source file. Pull with: `pull --files src/zmy_dtel.dtel.xml`
+**Files**: `src/zc_my_view.dcls.asdcls` (source) + `src/zc_my_view.dcls.xml` (metadata)
 
 ```xml
 <?xml version="1.0" encoding="utf-8"?>
-<abapGit version="v1.0.0" serializer="LCL_OBJECT_DTEL" serializer_version="v1.0.0">
+<abapGit version="v1.0.0" serializer="LCL_OBJECT_DCLS" serializer_version="v1.0.0">
  <asx:abap xmlns:asx="http://www.sap.com/abapxml" version="1.0">
   <asx:values>
-   <DD04V>
-    <ROLLNAME>ZMY_DTEL</ROLLNAME>
-    <DDLANGUAGE>E</DDLANGUAGE>
-    <DDTEXT>Description of data element</DDTEXT>
-    <REPTEXT>Description</REPTEXT>
-    <SCRTEXT_S>Short text</SCRTEXT_S>
-    <SCRTEXT_M>Medium text</SCRTEXT_M>
-    <SCRTEXT_L>Long description text</SCRTEXT_L>
-    <DTELMASTER>E</DTELMASTER>
-    <DATATYPE>CHAR</DATATYPE>
-    <LENG>000010</LENG>
-   </DD04V>
+   <DCLS>
+    <DCLNAME>ZC_MY_VIEW</DCLNAME>
+    <DCLLANGUAGE>E</DCLLANGUAGE>
+    <DDTEXT>Access control for ZC_MY_VIEW</DDTEXT>
+   </DCLS>
   </asx:values>
  </asx:abap>
 </abapGit>
 ```
 
-**Key Fields**:
-- `ROLLNAME`: Data element name
-- `DDTEXT`: Description (**not** `DESCRIPT`)
-- `REPTEXT` / `SCRTEXT_S` / `SCRTEXT_M` / `SCRTEXT_L`: Field labels (report heading, short, medium, long)
-- `DTELMASTER`: Language key for label master (`E` for English)
-- `DATATYPE`: Data type (`CHAR`, `NUMC`, `DATS`, `TIMS`, `INT4`, etc.)
-- `LENG`: Length padded to 6 digits (e.g. `000010` for 10 characters)
-
-**Omit `<PARAMID>`** unless you specifically need a SET/GET parameter ID — the serializer omits it when empty, so including an empty tag causes a permanent diff.
+- `DCLNAME` matches the CDS view name
+- Source file contains the DCL (`@MappingRole ... define role ...`)
 
 ---
 
-### Structure (STRU)
-
-**Filename**: `src/zmy_struct.stru.xml`
-
-> **XML-only object** — no `.abap` source file. abapGit uses the same TABL serializer for STRU.
-> Pull with: `pull --files src/zmy_struct.stru.xml`
+### Function Group (FUGR)
 
-```xml
-<?xml version="1.0" encoding="utf-8"?>
-<abapGit version="v1.0.0" serializer="LCL_OBJECT_TABL" serializer_version="v1.0.0">
- <asx:abap xmlns:asx="http://www.sap.com/abapxml" version="1.0">
-  <asx:values>
-   <DD02V>
-    <TABNAME>ZMY_STRUCT</TABNAME>
-    <DDLANGUAGE>E</DDLANGUAGE>
-    <TABCLASS>INTTAB</TABCLASS>
-    <DDTEXT>Description of the structure</DDTEXT>
-    <CONTFLAG>A</CONTFLAG>
-   </DD02V>
-  </asx:values>
- </asx:abap>
-</abapGit>
-```
+FUGR serializes as multiple files (main XML + TOP include + SAPL include + one source file per FM). The format is straightforward for screenless function groups — Claude can generate it from scratch.
 
-**Key difference from TABL**: `TABCLASS` is `INTTAB` (internal table / structure) instead of `TRANSP`.
-
-**Note**: Like TABL, after the first pull abapGit expands the XML with `<DD03P_TABLE>` field definitions. When creating a new structure you only need the `<DD02V>` header.
-
----
-
-### Table Type (TTYP)
-
-**Filename**: `src/zmy_ttyp.ttyp.xml`
-
-> **XML-only object** — no `.abap` source file.
-> Pull with: `pull --files src/zmy_ttyp.ttyp.xml`
-
-```xml
-<?xml version="1.0" encoding="utf-8"?>
-<abapGit version="v1.0.0" serializer="LCL_OBJECT_TTYP" serializer_version="v1.0.0">
- <asx:abap xmlns:asx="http://www.sap.com/abapxml" version="1.0">
-  <asx:values>
-   <DD40V>
-    <TYPENAME>ZMY_TTYP</TYPENAME>
-    <DDLANGUAGE>E</DDLANGUAGE>
-    <DDTEXT>Description of table type</DDTEXT>
-    <ROWTYPE>ZMY_STRUCT</ROWTYPE>
-    <ROWKIND>S</ROWKIND>
-    <DATATYPE>TABLE_T</DATATYPE>
-    <ACCESSMODE>T</ACCESSMODE>
-    <KEYDEF>D</KEYDEF>
-    <KEYKIND>N</KEYKIND>
-   </DD40V>
-  </asx:values>
- </asx:abap>
-</abapGit>
-```
-
-**Key Fields**:
-- `TYPENAME`: Table type name
-- `ROWTYPE`: Row type (a structure or data element name)
-- `ROWKIND`: Row kind — `S`=Structure/Type, `D`=Data element, `R`=Reference
-- `DATATYPE`: Always `TABLE_T` for table types
-- `ACCESSMODE`: Table kind — `T`=Standard, `S`=Sorted, `H`=Hashed
-- `KEYDEF`: Key definition — `D`=Default (standard key), `K`=User-defined
-- `KEYKIND`: Key uniqueness — `N`=Non-unique, `U`=Unique
-
-**Note**: After the first pull abapGit may expand the XML with `<DD42V>` (component definitions) if key fields are explicitly defined.
+→ Full template and file-set rules: `abapgit-agent ref --topic abapgit-fugr`
 
 ---
 

package/abap/guidelines/abaplint-local.md

@@ -1,7 +1,7 @@
 ---
 layout: default
 title: abaplint Local Rules
-nav_order: 18
+nav_order: 21
 parent: ABAP Coding Guidelines
 grand_parent: ABAP Development
 ---

package/abap/guidelines/abaplint.md

@@ -1,7 +1,7 @@
 ---
 layout: default
 title: abaplint Rule Guidelines
-nav_order: 17
+nav_order: 20
 parent: ABAP Coding Guidelines
 grand_parent: ABAP Development
 ---

package/abap/guidelines/branch-workflow.md

@@ -1,7 +1,7 @@
 ---
 layout: default
 title: Branch Workflow
-nav_order: 14
+nav_order: 17
 parent: ABAP Coding Guidelines
 grand_parent: ABAP Development
 ---

package/abap/guidelines/cds-testing.md

@@ -1,7 +1,7 @@
 ---
 layout: default
 title: CDS Testing
-nav_order: 19
+nav_order: 22
 parent: ABAP Coding Guidelines
 grand_parent: ABAP Development
 ---

package/abap/guidelines/common-errors.md

@@ -1,7 +1,7 @@
 ---
 layout: default
 title: Common ABAP Errors
-nav_order: 11
+nav_order: 14
 parent: ABAP Coding Guidelines
 grand_parent: ABAP Development
 ---

package/abap/guidelines/debug-dump.md

@@ -1,7 +1,7 @@
 ---
 layout: default
 title: Dump Analysis Guide
-nav_order: 13
+nav_order: 16
 parent: ABAP Coding Guidelines
 grand_parent: ABAP Development
 ---

package/abap/guidelines/debug-session.md

@@ -1,7 +1,7 @@
 ---
 layout: default
 title: Debug Session Guide
-nav_order: 12
+nav_order: 15
 parent: ABAP Coding Guidelines
 grand_parent: ABAP Development
 ---
@@ -91,6 +91,28 @@ abapgit-agent debug set --objects ZCL_MY_CLASS:5 --include locals_imp
 abapgit-agent debug list    # confirm both were registered
 ```
 
+**Function module (FUGR) methods** live in per-FM source includes (`L<GROUP>U<NN>`). Use `view` with `--full --fm <name> --lines` to see the source and breakpoint hint:
+
+```bash
+abapgit-agent view --objects SUSR --type FUGR --full --fm AUTHORITY_CHECK --lines
+```
+
+```
+  * ---- FM: AUTHORITY_CHECK (LSUSRU04) — breakpoint: debug set --objects LSUSRU04:50 ----
+     1  function authority_check.
+    ...
+    36    constants:
+    ...
+    45    data:
+    ...
+    50    ld_syuname = cl_abap_syst=>get_user_name( ).
+```
+
+```bash
+abapgit-agent debug set --objects LSUSRU04:50
+abapgit-agent debug list    # confirm it was registered
+```
+
 > **Line number must point to an executable statement.** The hints already skip `METHOD`, blank lines, comments (`"`, `*`), and all declaration forms (`DATA`, `DATA:`, `DATA(`). One case still requires manual attention:
 >
 > **Multi-line inline `DATA(x) = call(`** — the ABAP debugger treats the whole expression as a declaration. Set the breakpoint on the **next standalone statement** after the closing `).`:
@@ -277,26 +299,3 @@ HTTP Request
 > inside `find_remote_dot_abapgit()` via `COMMIT WORK AND WAIT` — i.e., the lock is released before
 > BP2 fires. There is no active lock between BP1 and the end of CM00L.
 
-### Known Limitations and Planned Improvements
-
-The following issues were identified during live debugging sessions and resolved:
-
-#### ~~1. `view --full` global line numbers don't match ADT line numbers~~ ✅ Fixed
-
-**Fixed**: `view --full --lines` now shows dual line numbers per line: `G [N]  code` where G is the assembled-source global line and `[N]` is the include-relative counter. Method headers show the ready-to-use `debug set --objects CLASS:G` command pointing to the first executable statement (skipping `METHOD`, blank lines, comments, and all `DATA`/`DATA:`/`DATA(` declaration forms).
-
-Global line numbers are computed **client-side** in Node.js, not in ABAP:
-- **Own classes** (local `.clas.abap` file exists): reads the local file — guaranteed exact match with ADT
-- **Library classes** (no local file, e.g. abapGit): fetches assembled source from `/sap/bc/adt/oo/classes/<name>/source/main`
-
-#### ~~2. No breakpoint support for unit test and local class methods~~ ✅ Fixed
-
-**Fixed**: CCAU (unit test) and CCIMP (local class implementation) sections in `view --full --lines` now show per-method `debug set --objects CLASS:N --include <type>` hints. These use the `/includes/<type>` ADT sub-include URI which ADT accepts for CCAU/CCIMP includes. See Step 1 above for details.
-
-#### ~~3. Include-relative breakpoint form (`=====CMxxx:N`) not implemented in the CLI~~ ✅ Superseded
-
-**Superseded**: The `/programs/includes/` ADT endpoint was found to not accept breakpoints for OO class method includes — ADT only accepts the `/oo/classes/.../source/main` URI with assembled-source line numbers. The `=====CMxxx:N` approach was dropped. Instead, `view --full --lines` now provides the correct assembled-source global line number G directly, and both `--objects CLASS:G` and `--files src/cls.clas.abap:G` work reliably.
-
-#### ~~4. `stepContinue` re-attach pattern missing from docs~~ ✅ Fixed
-
-**Fixed**: Step 3 of the debug guide now documents the two possible return values of `step --type continue` and includes the re-attach pattern for when the program hits a second breakpoint instead of finishing.

package/abap/guidelines/object-creation.md

@@ -1,7 +1,7 @@
 ---
 layout: default
 title: Object Creation
-nav_order: 16
+nav_order: 19
 parent: ABAP Coding Guidelines
 grand_parent: ABAP Development
 ---

package/abap/guidelines/probe-poc.md

@@ -1,7 +1,7 @@
 ---
 layout: default
 title: Probe and PoC Guide
-nav_order: 21
+nav_order: 24
 parent: ABAP Coding Guidelines
 grand_parent: ABAP Development
 ---

package/abap/guidelines/run-probe-classes.md

@@ -1,7 +1,7 @@
 ---
 layout: default
 title: run Command Guide
-nav_order: 20
+nav_order: 23
 parent: ABAP Coding Guidelines
 grand_parent: ABAP Development
 ---

package/abap/guidelines/unit-testable-code.md

@@ -1,7 +1,7 @@
 ---
 layout: default
 title: Unit Testable Code
-nav_order: 10
+nav_order: 13
 parent: ABAP Coding Guidelines
 grand_parent: ABAP Development
 ---
@@ -557,45 +557,3 @@ DATA(lo_command) = NEW zcl_abgagt_command_pull(
   io_agent = NEW zcl_abgagt_agent( ) ).
 ```
 
-**Test usage:**
-```abap
-CLASS ltd_mock_agent DEFINITION FOR TESTING.
-  PUBLIC SECTION.
-    INTERFACES zif_abgagt_agent PARTIALLY IMPLEMENTED.
-ENDCLASS.
-
-CLASS ltd_mock_agent IMPLEMENTATION.
-  METHOD zif_abgagt_agent~pull.
-    rs_result-success = abap_true.
-    rs_result-message = 'Mocked success'.
-  ENDMETHOD.
-ENDCLASS.
-
-CLASS ltcl_test DEFINITION FOR TESTING.
-  METHOD test_pull_success.
-    DATA(lo_mock) = NEW ltd_mock_agent( ).
-    DATA(lo_cut) = NEW zcl_abgagt_command_pull( io_agent = lo_mock ).
-
-    DATA(lv_result) = lo_cut->execute( ... ).
-
-    " Assert mocked behavior
-  ENDMETHOD.
-ENDCLASS.
-```
-
----
-
-## Key Takeaways
-
-1. **Always use interfaces** for dependencies
-2. **Use constructor injection** to pass dependencies
-3. **Never hardcode `NEW` for dependencies** - pass them in
-4. **Avoid static calls** - use instance methods with injected dependencies
-5. **Keep constructors simple** - only assign dependencies
-
-Following these guidelines ensures that:
-- Unit tests can mock all dependencies
-- Tests run fast without external systems
-- Tests are reliable and repeatable
-- Error conditions can be tested easily
-- Code is modular and loosely coupled

package/abap/guidelines/workflow-detailed.md

@@ -1,7 +1,7 @@
 ---
 layout: default
 title: Development Workflow (Detailed)
-nav_order: 15
+nav_order: 18
 parent: ABAP Coding Guidelines
 grand_parent: ABAP Development
 ---

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "abapgit-agent",
-  "version": "1.14.5",
+  "version": "1.15.0",
   "description": "ABAP Git Agent - Pull and activate ABAP code via abapGit from any git repository",
   "files": [
     "bin/",

package/src/commands/debug.js

@@ -89,6 +89,10 @@ const INCLUDE_TYPE_TO_ADT = {
  * e.g. ZCL_ABGAGT_AGENT=============CM00D
  * These must be routed to the programs/includes ADT endpoint.
  *
+ * FUGR source includes follow L<group><suffix> naming (e.g. LSUSRU04, LSUSRTOP,
+ * LSUSRF10, L_ABAU01). They start with 'L' and are routed to programs/includes.
+ * Customer-namespace programs always start with Z/Y, so this branch is safe.
+ *
  * When includeType is supplied (testclasses|locals_imp|locals_def),
  * the URI targets the sub-include of the class instead of /source/main.
  * Line numbers are then section-local (from the .clas.<file>.abap file).
@@ -103,6 +107,11 @@ function objectUri(name, includeType) {
     }
     return `/sap/bc/adt/oo/classes/${lower}/source/main`;
   }
+  // FUGR source includes: L<group>U<NN>, L<group>TOP, L<group>F<NN>, etc.
+  // All start with 'L'. Customer Z/Y programs never start with 'L'.
+  if (/^L/.test(upper)) {
+    return `/sap/bc/adt/programs/includes/${lower}`;
+  }
   return `/sap/bc/adt/programs/programs/${lower}`;
 }