abapify · ThePlenkov · Mar 16, 2026 · Mar 16, 2026 · Mar 16, 2026 · Mar 16, 2026
diff --git a/.windsurf/rules/nx-monorepo-setup.md b/.windsurf/rules/nx-monorepo-setup.md
@@ -113,9 +113,9 @@ For packages in `packages/plugins/`:
 
 ```bash
 bunx nx g @nx/js:lib \
-  --name=oat \
-  --directory=packages/plugins/oat \
-  --importPath=@abapify/oat \
+  --name=custom-format \
+  --directory=packages/plugins/custom-format \
+  --importPath=@abapify/custom-format \
   --bundler=none \
   --unitTestRunner=none \
   --linter=eslint

diff --git a/.windsurf/rules/spec-first-then-code.md b/.windsurf/rules/spec-first-then-code.md
@@ -30,7 +30,6 @@ description: When making any changes for any of spec-driven packages
 ## Spec Domains
 
 - `openspec/specs/adk/` — ADK (ABAP Development Kit, TS native way to work with ABAP code and other objects)
-- `openspec/specs/oat/` — OAT (Alternative to AbapGit and gCTS way of representing ABAP objects in a file tree)
 - `openspec/specs/adt-cli/` — ADT CLI (alternative to piper CLI solution to operate with ABAP backend)
 - `openspec/specs/adt-client/` — ADT Client (abstracted ADT API communication)
 - `openspec/specs/cicd/` — CI/CD pipeline architecture
diff --git a/.windsurf/rules/tmp-folder-testing.md b/.windsurf/rules/tmp-folder-testing.md
@@ -21,10 +21,10 @@ description: If you want to create some test output which is not supposed to be
 
 ```bash
 # ✅ CORRECT - Use tmp/ for experiments
-npx adt import transport TR001 ./tmp/test-transport --format oat --debug
+npx adt import transport TR001 ./tmp/test-transport --format abapgit --debug
 
 # ❌ WRONG - Don't create test files in root
-npx adt import transport TR001 ./test-transport-import --format oat --debug
+npx adt import transport TR001 ./test-transport-import --format abapgit --debug
 ```
 
 ### Exception: E2E Tests

diff --git a/AGENTS.md b/AGENTS.md
@@ -62,7 +62,7 @@ bunx nx lint
 ├── samples/              # Example projects
 ├── tools/                # Nx plugins/tools
 ├── openspec/             # OpenSpec specs and changes (source of truth)
-│   ├── specs/            # Domain specifications (adk, adt-cli, oat, cicd, etc.)
+│   ├── specs/            # Domain specifications (adk, adt-cli, cicd, etc.)
 │   ├── changes/          # Proposed changes (one folder per change)
 │   └── config.yaml       # OpenSpec project configuration
 ├── docs/                 # Architecture docs, migration notes, examples
@@ -205,7 +205,6 @@ Specifications live in `openspec/specs/` organized by domain:
 - `openspec/specs/adt-cli/` — CLI design and plugin architecture
 - `openspec/specs/adt-client/` — ADT API client
 - `openspec/specs/cicd/` — CI/CD pipeline architecture
-- `openspec/specs/oat/` — OAT file format
 
 ### Before implementing a new feature:
 

diff --git a/docs/README.md b/docs/README.md
@@ -12,8 +12,7 @@ openspec/
 │   ├── adk/            # ABAP Development Kit
 │   ├── adt-cli/        # ADT CLI design and plugins
 │   ├── adt-client/     # ADT API client
-│   ├── cicd/           # CI/CD pipeline
-│   └── oat/            # OAT file format
+│   └── cicd/           # CI/CD pipeline
 ├── changes/            # Proposed changes (one folder per change)
 └── config.yaml         # Project configuration
 ```

diff --git a/docs/architecture/adk-overview.md b/docs/architecture/adk-overview.md
@@ -86,7 +86,7 @@ includeType: 'testclasses'      → zcl_example.clas.testclasses.abap
 
 ```
 ┌─────────────────────────────────────────────────────────────┐
-│ Format Plugins (@abapify/abapgit, @abapify/oat)            │
+│ Format Plugins (@abapify/adt-plugin-abapgit)                │
 │ - Serialize ADK → Files                                     │
 │ - Deserialize Files → ADK                                   │
 │ - NO direct ADT Client access                               │

diff --git a/docs/architecture/plugin-system.md b/docs/architecture/plugin-system.md
@@ -2,14 +2,14 @@
 
 ## Overview
 
-The ADT CLI now implements a plugin-based configuration system where format handlers (like OAT) can leverage ADK for proper serialization/deserialization of ABAP objects received from the ADT client.
+The ADT CLI implements a plugin-based configuration system where format handlers (like abapGit) can leverage ADK for proper serialization/deserialization of ABAP objects received from the ADT client.
 
 ## Architecture
 
 ### Core Components
 
 1. **Format Registry** (`/lib/formats/format-registry.ts`)
-   - Manages format plugins (OAT, abapGit, etc.)
+   - Manages format plugins (abapGit, etc.)
    - Auto-registers available object types from ObjectRegistry
    - Provides unified interface for format operations
 
@@ -23,14 +23,14 @@ The ADT CLI now implements a plugin-based configuration system where format hand
    - Preserves original ADT XML context for round-trip compatibility
    - Enhances ObjectData with ADK spec metadata
 
-### Enhanced OAT Format
+### Enhanced abapGit Format
 
-The OAT format now properly leverages ADK for serialization/deserialization:
+The abapGit format leverages ADK for serialization/deserialization:
 
 #### Serialization Flow
 
 ```
-ADT Client → ADK Bridge → ObjectData (with ADK spec) → OAT Format → YAML files
+ADT Client → ADK Bridge → ObjectData (with ADK spec) → abapGit Format → .abap + .xml files
 ```
 
 #### Key Improvements
@@ -43,13 +43,13 @@ ADT Client → ADK Bridge → ObjectData (with ADK spec) → OAT Format → YAML
 #### Code Example
 
 ```typescript
-// Enhanced serialization in OAT format
+// Pseudocode – illustrative only, not the exact implementation
+// Enhanced serialization in abapGit format
 const adkSpec = objectData.metadata?.adkSpec
   ? this.createAdkSpecFromExistingData(objectData, objectType)
   : this.convertObjectDataToAdkSpec(objectData, objectType);
 
-const serializer = SerializerRegistry.get('oat');
-const serialized = serializer.serialize(adkSpec);
+const serialized = serializeWithAbapGit(adkSpec);
 ```
 
 ### Object Type Support
@@ -81,23 +81,23 @@ The plugin system is automatically configured through:
 
 ## Usage
 
-### Transport Import with Enhanced OAT
+### Transport Import with abapGit
 
 ```bash
-adt import transport TR001234 ./output --format oat --debug
+adt import transport TR001234 ./output --format abapgit --debug
 ```
 
 This command now:
 
 1. Retrieves transport objects via ADT client
 2. Converts to ADK specs using appropriate adapters
-3. Serializes using OAT format with full ADK context
+3. Serializes using abapGit format with full ADK context
 4. Preserves all metadata for round-trip compatibility
 
 ### Supported Workflows
 
-- **Import**: ADT → ADK → OAT YAML files
-- **Export**: OAT YAML files → ADK → ADT (future)
+- **Import**: ADT → ADK → abapGit files (.abap + .xml)
+- **Export**: abapGit files → ADK → ADT
 - **Round-trip**: Maintains data integrity throughout the process
 
 ## Future Enhancements

diff --git a/docs/design/export-architecture.md b/docs/design/export-architecture.md
@@ -5,7 +5,7 @@
 The current export implementation in `ExportService` tries to iterate over files directly,
 but this is wrong because:
 
-1. **Each format has different file structures** - OAT uses `.oat.xml`, abapGit uses `.abap` + `.xml`
+1. **Each format has different file structures** - abapGit uses `.abap` + `.xml`
 2. **Only the plugin knows how to read its format** - file discovery is format-specific
 3. **Plugin should not be responsible for deployment** - only for format mapping
 
@@ -33,7 +33,7 @@ but this is wrong because:
 ┌─────────────────────────────────────────────────────────────┐
 │ Plugin (format.export generator)                            │
 │ - Receives FileTree                                         │
-│ - Iterates files in its format (*.oat.xml, *.abap, etc.)    │
+│ - Iterates files in its format (*.abap, *.xml, etc.)        │
 │ - Parses each file into ADK object                          │
 │ - Yields ADK objects (does NOT deploy)                      │
 └─────────────────────────────────────────────────────────────┘
@@ -148,28 +148,6 @@ async exportTransport(options: TransportExportOptions): Promise<ExportResult> {
 }
 ```
 
-### Plugin Implementation Example (OAT)
-
-```typescript
-// In @abapify/oat plugin
-async function* export(fileTree: FileTree): AsyncGenerator<AdkObject> {
-  // Plugin knows OAT format: *.oat.xml files
-  for await (const file of fileTree.glob('**/*.oat.xml')) {
-    const content = await fileTree.read(file);
-
-    // Parse OAT XML → extract type, name, source, metadata
-    const parsed = parseOatXml(content);
-
-    // Create ADK object with data
-    const adkObject = adk.get(parsed.name, parsed.type);
-    adkObject.setSource(parsed.source);
-    adkObject.setMetadata(parsed.metadata);
-
-    yield adkObject;
-  }
-}
-```
-
 ### Plugin Implementation Example (abapGit)
 
 ```typescript
@@ -253,10 +231,9 @@ async function* export(fileTree: FileTree): AsyncGenerator<AdkObject> {
 ### Remaining TODO
 
 1. Update `AdtPlugin` interface with `export` generator in `@abapify/adt-plugin`
-2. Implement `export` generator in OAT plugin
-3. Add bulk activation to ADK (if not exists)
-4. Remove export commands from `@abapify/adt-cli` (now in separate plugin)
-5. Wire up full export flow in adt-export command
+2. Add bulk activation to ADK (if not exists)
+3. Remove export commands from `@abapify/adt-cli` (now in separate plugin)
+4. Wire up full export flow in adt-export command
 
 ## Usage
 
@@ -271,7 +248,7 @@ export default {
 Then use:
 
 ```bash
-adt export --source ./my-objects --format oat --transport DEVK900123
+adt export --source ./my-objects --format abapgit --transport DEVK900123
 ```
 
 ## Open Questions

diff --git a/docs/examples/intelligent-adk-usage.md b/docs/examples/intelligent-adk-usage.md
@@ -82,8 +82,8 @@ if (domainObj.kind === 'Domain') {
 ## Plugin Integration
 
 ```typescript
-// Example: Enhanced OAT Plugin using intelligent objects
-class EnhancedOatPlugin implements FormatPlugin {
+// Example: Enhanced abapGit Plugin using intelligent objects
+class EnhancedAbapGitPlugin implements FormatPlugin {
   async serialize(
     objects: AdkObjectBase[],
     targetPath: string,
@@ -101,7 +101,7 @@ class EnhancedOatPlugin implements FormatPlugin {
         const methods = classObj.getMethods();
         const isAbstract = classObj.isAbstract();
 
-        // Enhanced metadata for OAT format
+        // Enhanced metadata for abapGit format
         const enhancedMetadata = {
           ...metadata,
           methodCount: methods.length,

diff --git a/docs/planning/abap-code-review.md b/docs/planning/abap-code-review.md
@@ -22,7 +22,7 @@ Implement a complete CI/CD pipeline for ABAP code review using transport request
 
 - **[#3] Transport Import Stage** - Extract and serialize transport objects
   - Status: `status:ready`
-  - Dependencies: ADT CLI auth, ADK adapters, OAT format
+  - Dependencies: ADT CLI auth, ADK adapters, abapGit format
   - Estimated effort: 2-3 days
 - **[#4] Quality Check Stage** - ATC integration with multi-platform output
   - Status: `status:ready`
@@ -69,7 +69,7 @@ Implement a complete CI/CD pipeline for ABAP code review using transport request
 
 - ADT CLI authentication system (✅ exists)
 - ADK object adapters (✅ exists)
-- OAT format specification (✅ exists)
+- abapGit format specification (✅ exists)
 - ATC API integration (❓ needs investigation)
 
 ### Risks
@@ -81,7 +81,7 @@ Implement a complete CI/CD pipeline for ABAP code review using transport request
 
 ## Success Metrics
 
-- [ ] Complete transport import with OAT output
+- [ ] Complete transport import with abapGit output
 - [ ] ATC integration with GitLab Code Quality format
 - [ ] Markdown report generation with quality metrics
 - [ ] End-to-end pipeline execution < 5 minutes for typical transport
@@ -92,7 +92,7 @@ Implement a complete CI/CD pipeline for ABAP code review using transport request
 1. Start with Issue #3 (Transport Import Stage)
 2. Implement basic ADT API integration for transport object retrieval
 3. Add ADK integration for type-safe serialization
-4. Create OAT format output generation
+4. Create abapGit format output generation
 5. Move to Quality Check Stage (Issue #4)
 
 ## Notes

diff --git a/docs/planning/current-sprint.md b/docs/planning/current-sprint.md
@@ -58,7 +58,7 @@ _Ready for next phase implementation_
 1. **Transport Import Implementation** (#3) ✅ COMPLETED
    - [x] ADT API integration for transport object retrieval
    - [x] ADK integration for type-safe object serialization
-   - [x] OAT format output generation
+   - [x] abapGit format output generation
    - [x] Error handling and logging
    - [ ] Unit tests and integration tests
 
@@ -86,7 +86,7 @@ _None identified_
 
 - ✅ ADT CLI authentication system (available)
 - ✅ ADK object adapters (available)
-- ✅ OAT format specification (available)
+- ✅ abapGit format specification (available)
 - ❓ ATC API documentation (needs research)
 
 ## Daily Progress
@@ -103,7 +103,7 @@ _None identified_
 - Begin Transport Import Stage implementation (#3)
 - Start with ADT API integration research
 - Set up development environment for testing
-- Focus on transport object retrieval and OAT serialization
+- Focus on transport object retrieval and abapGit serialization
 
 ## Notes
 

diff --git a/docs/planning/roadmap.md b/docs/planning/roadmap.md
@@ -18,8 +18,8 @@ Create a platform-agnostic, developer-friendly CI/CD pipeline for ABAP code revi
   - CI/CD pipeline specification
 - [ ] **Transport Import Stage** (#3)
   - Extract ABAP objects from transport requests
-  - OAT format serialization
-  - Multiple output format support (OAT, abapGit, JSON)
+  - abapGit format serialization
+  - Multiple output format support (abapGit, JSON)
 - [ ] **Quality Check Stage** (#4)
   - ATC integration with transport objects
   - Multi-platform output (GitLab, GitHub, SARIF, console)

diff --git a/openspec/specs/adk/intelligent-object-factory.md b/openspec/specs/adk/intelligent-object-factory.md
@@ -207,8 +207,8 @@ class ClassObjectImpl implements ClassObject {
 Plugins will receive intelligent ADK objects instead of raw data:
 
 ```typescript
-// OAT Plugin usage
-class OatPlugin implements FormatPlugin {
+// abapGit Plugin usage
+class AbapGitPlugin implements FormatPlugin {
   async serialize(
     objects: AdkObjectBase[],
     targetPath: string,
@@ -239,7 +239,7 @@ class OatPlugin implements FormatPlugin {
 2. **Implement object factory** - Create AdkObjectFactory with ADT client integration
 3. **Create object implementations** - Implement ClassObjectImpl, InterfaceObjectImpl, etc.
 4. **Integrate with existing adapters** - Reuse current XML parsing logic
-5. **Update plugins** - Modify OAT plugin to use new intelligent objects
+5. **Update plugins** - Modify abapGit plugin to use new intelligent objects
 
 ## Benefits
 

diff --git a/openspec/specs/adk/spec.md b/openspec/specs/adk/spec.md
@@ -187,9 +187,9 @@ this.handlers.set(
 );
 ```
 
-### With OAT Format
+### With abapGit Format
 
-ADK specifications serve as the canonical representation for OAT metadata storage, ensuring type safety and consistency across the entire toolchain.
+ADK specifications serve as the canonical representation for abapGit metadata storage, ensuring type safety and consistency across the entire toolchain.
 
 ## Quality Requirements