abapgit-agent 1.14.4 → 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,53 +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.
-
----
-
 ### 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"?>
@@ -308,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`
+### Function Group (FUGR)
 
-> **XML-only object** — no `.abap` source file. abapGit uses the same TABL serializer for STRU.
-> Pull with: `pull --files src/zmy_struct.stru.xml`
+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.
 
-```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>
-```
-
-**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
 ---
@@ -17,7 +17,7 @@ Use `debug` when:
 
 **Step 1 — set a breakpoint** on the first executable statement you want to inspect:
 
-Use `view --objects ZCL_MY_CLASS --full --lines` to see the full source with **both** global assembled-source line numbers and include-relative `[N]` numbers:
+Use `view --objects ZCL_MY_CLASS --full --lines` to see the full source with line numbers and ready-to-use `debug set` commands:
 
 ```bash
 abapgit-agent view --objects ZCL_MY_CLASS --full --lines
@@ -25,16 +25,11 @@ abapgit-agent view --objects ZCL_MY_CLASS --full --lines
 
 > **Tip**: `view --full` (without `--lines`) shows the same full source as clean readable code without line numbers — useful for understanding logic. Add `--lines` when you need line numbers for breakpoints.
 
-Each line is shown as `G [N]  code` where:
-- **G** = assembled-source global line → use with `debug set --objects CLASS:G` or `debug set --files src/cls.clas.abap:G`
-- **[N]** = include-relative (restarts at 1 per method) → for code navigation only, not for breakpoints
+The output varies by section type:
 
-The method header shows the ready-to-use `debug set` command pointing to the first executable line:
+**Regular methods (CM\* sections)** — dual line numbers `G [N]` per line, with a `debug set` hint at the method header:
 
 ```
-   1  CLASS zcl_my_class DEFINITION.
-   2    PUBLIC SECTION.
-   3  ENDCLASS.
   * ---- Method: EXECUTE (CM002) — breakpoint: debug set --objects ZCL_MY_CLASS:9 ----
    7 [  1]  METHOD execute.
    8 [  2]    DATA lv_x TYPE i.
@@ -42,44 +37,91 @@ The method header shows the ready-to-use `debug set` command pointing to the fir
   10 [  4]  ENDMETHOD.
 ```
 
-**Two scenarios:**
+- **G** = assembled-source global line → use with `debug set --objects CLASS:G` or `--files src/cls.clas.abap:G`
+- **[N]** = include-relative (restarts at 1 per method) → for code navigation only, not for breakpoints
+
+The hint already points to the first **executable** line, skipping `METHOD`, blank lines, comments, and all declaration forms (`DATA`, `DATA:`, `DATA(`).
+
+**Two scenarios for CM* methods:**
 
 | Scenario | Command |
 |---|---|
 | Source available locally (your own classes) | `debug set --files src/zcl_my_class.clas.abap:9` |
 | No local source (abapGit library, SAP standard) | `debug set --objects ZCL_MY_CLASS:9` |
 
-Both use the same assembled-source global line number **G** shown in the output. To set a breakpoint at `lv_x = 1.` (global line 9):
 ```bash
-# With local file:
-abapgit-agent debug set --files src/zcl_my_class.clas.abap:9
-# Without local file:
 abapgit-agent debug set --objects ZCL_MY_CLASS:9
 abapgit-agent debug list    # confirm it was registered
 ```
 
-> **Line number must point to an executable statement.** The method header hint already skips the `METHOD` line, blank lines, and `DATA`/`FINAL`/`TYPES`/`CONSTANTS` declarations automatically. Two cases still require manual attention when picking a line from the output:
->
-> 1. **Comment lines** — lines starting with `"` are never executable. ADT silently rejects the breakpoint.
->    Pick the next non-comment line instead.
->    ```
->     95 [ 70]    " --- Conflict detection ---   ← NOT valid (comment)
->     96 [ 71]    " Build remote file entries…   ← NOT valid (comment)
->     97 [ 73]    DATA(lt_file_entries) = …      ← valid ✅ (use global 97)
->    ```
->
-> 2. **First line of a multi-line inline `DATA(x) = call(`** — the ABAP debugger treats the
->    `DATA(x) =` line as a declaration, not an executable step. Set the breakpoint on the
->    **next standalone executable statement** after the closing `).` instead.
->    ```
->    100 [ 92]    DATA(ls_checks) = prepare_deserialize_checks(   ← NOT valid (inline decl)
->    101 [ 93]      it_files = it_files                           ← NOT valid (continuation)
->    104 [ 96]      io_repo_desc = lo_repo_desc1 ).               ← NOT valid (continuation)
->    106 [ 98]    mo_repo->create_new_log( ).                     ← valid ✅ (use global 106)
->    ```
+**Unit test methods (CCAU section)** and **local class methods (CCIMP section)** live in separate ADT includes — they cannot be addressed by the assembled-source global line. Their sections show section-local line numbers with a `--include` hint per method:
+
+```
+  * ---- Section: Unit Test (from .clas.testclasses.abap) ----
+  * ---- Method: SETUP — breakpoint: debug set --objects ZCL_MY_CLASS:12 --include testclasses ----
+    10    METHOD setup.
+    11      DATA lv_x TYPE i.
+    12      mo_cut = NEW #( ).
+    13    ENDMETHOD.
+  * ---- Method: TEST_PULL_SUCCESS — breakpoint: debug set --objects ZCL_MY_CLASS:18 --include testclasses ----
+    15    METHOD test_pull_success.
+    ...
+
+  * ---- Section: Local Implementations (from .clas.locals_imp.abap) ----
+  * ---- Method: ZIF_FOO~DO_SOMETHING — breakpoint: debug set --objects ZCL_MY_CLASS:5 --include locals_imp ----
+    3     METHOD zif_foo~do_something.
+    4       DATA lv_x TYPE i.
+    5       lv_x = iv_input.
+    6     ENDMETHOD.
+```
+
+The line numbers in these sections are **section-local** (same coordinate system as the `.clas.testclasses.abap` / `.clas.locals_imp.abap` file). Use the `--include` flag to target the correct ADT sub-include:
+
+| Section | `--include` value |
+|---|---|
+| Unit Test (`.clas.testclasses.abap`) | `testclasses` |
+| Local Implementations (`.clas.locals_imp.abap`) | `locals_imp` |
+| Local Definitions (`.clas.locals_def.abap`) | `locals_def` |
+
+```bash
+# Unit test method:
+abapgit-agent debug set --objects ZCL_MY_CLASS:12 --include testclasses
+# Local class method:
+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:
 >
-> Other non-executable lines: blank lines, `METHOD`/`ENDMETHOD`, `DATA:` declarations,
-> `CLASS`/`ENDCLASS`. When in doubt, prefer a simple method call or assignment.
+> **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 `).`:
+> ```
+>  100 [  1]    DATA(ls_checks) = prepare_deserialize_checks(   ← NOT valid (inline decl)
+>  101 [  2]      it_files = it_files                           ← NOT valid (continuation)
+>  104 [  5]      io_repo_desc = lo_repo_desc1 ).               ← NOT valid (continuation)
+>  106 [  7]    mo_repo->create_new_log( ).                     ← valid ✅ (use global 106)
+>  ```
 
 **Step 2 — attach and trigger**
 
@@ -257,24 +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 a live debugging session (2026-03) and should be fixed to make future debugging easier:
-
-#### ~~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 (usable directly with `--objects CLASS:G` or `--files src/cls.clas.abap:G`) and `[N]` is the include-relative counter for navigation. Method headers show the ready-to-use `debug set --objects CLASS:G` command pointing to the first executable statement. `view --full` (without `--lines`) shows the same full source as clean readable code without line numbers.
-
-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`
-
-Both strategies scan for `METHOD <name>.` as the first token on the line to find `global_start`. The method header hint automatically points to the **first executable statement** (skipping the `METHOD` line, blank lines, and `DATA`/`FINAL`/`TYPES`/`CONSTANTS` declarations) so it can be used directly without adjustment.
-
-#### ~~2. 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.
-
-#### ~~3. `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.4",
+  "version": "1.15.0",
   "description": "ABAP Git Agent - Pull and activate ABAP code via abapGit from any git repository",
   "files": [
     "bin/",