[kilfor.ru](https://kilfor.ru/) is an active website and internal system of the Kilfor business center.

The project runs on MODX. This version of the system has been in use on-site since 2016; its foundation was previously developed in 2009 for the business center at 21 Novy Arbat.

The project encompasses a public website, a user account dashboard, and application logic related to pass requests, vehicle entry, utilities, and other internal business center processes.

MODX remains the backend of the active system. The public part of the project is being developed separately on a new frontend.

The general state, history, and development of the project are documented in the [main concept](https://fi1osof.ru/concepts/kilfor-modernizatsiya-legacy-modx-proekta).

Kilfor.ru is an active website and internal system of the Kilfor business center. The public-facing part runs on MODX, while the backend maintains the application logic for the user account, pass requests, vehicle entry, utilities (housing and communal services), and other internal processes. Main project concept: https://fi1osof.ru/concepts/kilfor-modernizatsiya-legacy-modx-proekta

Kilfor.ru

Current error&#x20;

```text
Fatal error: Uncaught DOMPDF_Exception: No block-level parent found. 
```

Fix PDF export

## Context

Kilfor user sessions are currently stored and managed by MODX. The new frontend based on haih-agent already implements part of the application logic independently, so it periodically needs detailed information about the currently authenticated user.

MODX has an internal PHP API for working with the current user inside the MODX runtime, but there is no out-of-the-box standard external HTTP endpoint at the `current user` level for the frontend context. modSociety has its own endpoint for retrieving the user, but the new frontend must not depend on this legacy component.

## Goal

Implement an infrastructure layer in haih-agent capable of determining the user authorized in a given frontend context (`web` or another) based on the existing MODX session cookie, and providing normalized user data to the application code of the new frontend.

## What to Research and Implement

- Understand the actual frontend session storage format in the used version of MODX and on Kilfor.
- Determine how to retrieve the user for a specific context key using the session ID and `modx_session` data.
- Correctly parse PHP session serialization without relying on regex hacks.
- Retrieve necessary user data from `modUser`, `modUserProfile`, and project relations.
- Make the MODX-specific implementation a separate adapter/provider so that application code works with the `currentUser` abstraction rather than knowing the MODX session structure.
- Do not hardcode `web` into the low-level parser: the context key should be set via configuration or by the calling auth layer.
- Handle session expiration/invalidity and lack of authorization in the requested context.
- Do not port the entire MODX ACL/security runtime without a specific need; at the first stage, the task is to reliably identify the user and their data.
- Provide for the possibility of a different session storage/handler in the future, without tightly coupling all auth code to SQL queries against `modx_session`.
- Cover the parser and user identification with fixture/integration tests using real MODX frontend session examples.

## Expected Result

A normalized current user for the specified frontend context, retrieved directly from the existing MODX session, is available in the haih-agent GraphQL/request context. This eliminates the need for a separate request to the legacy modSociety endpoint or a MODX bootstrap on every new frontend request.

Teach the new Kilfor frontend to identify the current user directly via the existing MODX session without depending on a legacy HTTP endpoint.

Tasks

Integrate MODX frontend sessions into the haih-agent auth context

Fix PDF export