[oblomov-dev]

What changes

New pages

• Glossary (Getting Started): one word per thing — roundtrip, app instance, app draft (told apart from the RAP draft), view, model, binding, event, frontend action, sub-app, user exit — and a "if you know X, then here it is Y" table.
• AI Setup: The Recommended Path: three steps with one command each, what each costs, and a tool map. The other AI pages link to it instead of restating their own ladders.
• Lock: Full Source and RAP Draft: The Full Edit Screen: the long listings of the two 1,000-line pages; the original pages keep the overview and the short snippets.

Newcomer path

• Quickstart: the SICF step as numbered clicks; the verification names the expected result of each step (labels taken from the startup app's source).
• Every tutorial step says what you should see. Steps 6, 8 and 10 name what is new.
• check_on_navigated, n / v / ns, roundtrip and draft are explained where they first appear.

Configuration

• Productive Usage is now the Go-Live Checklist (same address) and opens the chapter: what, where, how to verify, plus a production exit class to copy.
• Security shows how to send the CSP as a response header, which the go-live table asked for and no page showed.
• Deployment Scenarios is a decision table; Authorization and User Exits state their rules as tables; Monitoring puts the operator part first.

Cookbook

• The index and the cheat sheet open with an "I want to… → call" table.
• Ten pages are named after the task (Building a View, Handling Events in ABAP, More than 100 Rows, …). File names and addresses are unchanged; changed headings keep their old anchor.
• Every example dispatches through one check_on_init / check_on_navigated / check_on_event chain.
• One word per thing: app draft, sub-app, frontend action, event binding.

Language

• Sentences over 35 words: 8.1% → 1.3% of the manual. npm run report:sentences lists the rest; it is a report and not part of npm run check.

Pictures

• Seven new diagrams: table binding, URL modes, frontend actions, the request path and who checks what, the lost update, RAP draft states, the AI tool map.
• Fresh English screenshots of the Developer Tools and the startup page, hosted here.
• The copied diagrams follow the insights originals again (readable secondary text).

Sidebar

• Go-Live Checklist first under Configuration; the two report pages under Tutorial → "Coming from Classic Reports"; Everyday Work lists the guides without RAP first.

Fixed along the way

• User Exits said a method is called "more than once" and "at most once" per request.
• The table examples appended 100 rows again on every return to the app.
• The glossary and cheat sheet use _bind( ) and follow_up_action( ), not the obsolete _bind_edit( ) / _event_client( ).

Worth a look in review

• The CSP-header snippet and the production exit class are derived from the framework source and pass check:examples; they were not run on an SAP system.
• Version minimums (monitor 1.147, cockpit 1.146, embed 1.145) are unchanged — the changelog does not confirm them either way.
• check:samples could not run locally (no samples checkout); CI runs it.
• Still to re-shoot on a real system: the abapGit screenshots and the two SICF dialogs.

Checks

npm run check passes locally: 180 tests and every gate except the skipped check:samples.

---

Generated by Claude Code