BEAR\Resource\SemanticLog\DevLogPersister

Complexity

Total Complexity

9

Size/Duplication

Total Lines	68
Duplicated Lines	0 %

Importance

Changes	1
Bugs	0	Features	1

5 Methods

Rating	Name	Duplication	Size	Complexity
A	saveToFile()	0	14	2
A	generateFilename()	0	12	2
A	getAnalysisPrompt()	0	3	1
A	__construct()	0	10	2
A	persistLogs()	0	6	2

<?php

declare(strict_types=1);

namespace BEAR\Resource\SemanticLog;

use Koriym\SemanticLogger\LogJson;
use Koriym\SemanticLogger\SemanticLoggerInterface;
use Ray\Di\Di\Named;
use Throwable;

use function date;
use function file_put_contents;
use function getmypid;
use function json_encode;
use function sprintf;
use function str_replace;
use function sys_get_temp_dir;
use function uniqid;

use const JSON_PRETTY_PRINT;
use const JSON_UNESCAPED_SLASHES;
use const LOCK_EX;

/**
 * Development log persister for MCP server integration
 *
 * Handles file persistence of semantic logs with Profile data for AI-assisted debugging.
 * Uses single responsibility principle - only concerned with log persistence.
 */
final class DevLogPersister
{
    public function __construct(
        #[Named('dev_log_directory')]
        private string $logDirectory = '',
    ) {
        // Use system temp directory if no directory specified
        if ($this->logDirectory !== '') {
            return;
        }

        $this->logDirectory = sys_get_temp_dir();
    }

    /**
     * Persist semantic logs to file for development/debugging purposes
     */
    public function persistLogs(SemanticLoggerInterface $logger): void
    {
        try {
            $logData = $logger->flush();
            $this->saveToFile($logData);
        } catch (Throwable) {
            // Silent failure - don't break main processing
            // In development, log persistence should never affect application flow
        }
    }

    private function saveToFile(LogJson $logData): void
    {
        $jsonContent = json_encode($logData, JSON_PRETTY_PRINT | JSON_UNESCAPED_SLASHES);
        if ($jsonContent === false) {
            return; // Skip if JSON encoding fails
        }

        $filename = $this->generateFilename();
        file_put_contents($filename, $jsonContent, LOCK_EX);

        // Save analysis prompt alongside JSON for AI-native processing
        $promptFilename = str_replace('.json', '-prompt.md', $filename);
        $analysisPrompt = $this->getAnalysisPrompt() . "\n\n```json\n" . $jsonContent . "\n```";
        file_put_contents($promptFilename, $analysisPrompt, LOCK_EX);
    }

    /**
     * Generate unique filename for concurrent request safety
     */
    private function generateFilename(): string
    {
        $timestamp = date('Y-m-d_H-i-s-u'); // Microseconds for concurrency
        $processId = getmypid(); // Process ID for true uniqueness
        $uniqueId = uniqid();

        return sprintf(
            '%s/semantic-dev-%s-%s-%s.json',
            $this->logDirectory,
            $timestamp,
            $processId !== false ? $processId : 'unknown',
            $uniqueId,
        );
    }

    /**
     * Generate analysis prompt for AI-native semantic web processing
     */
    private function getAnalysisPrompt(): string
    {
        return <<<'PROMPT'
This is a BEAR.Resource application profiling log. Analyze YOUR APPLICATION CODE performance, not the framework itself.

The log contains schemaUrl fields. If necessary, refer to these schemas to understand the semantic meaning of the data structures.

Focus on business logic within resource methods and application-specific code. Ignore framework overhead and profiling overhead.

If no performance issues are found, provide:
- What the code is doing (business purpose)
- How it's implemented (technical approach)
- Implementation assessment (is this approach appropriate for the task?)
- Any architectural observations or suggestions for production readiness

Use the semantic profiling data to provide deep insights about code quality and appropriateness, not just performance metrics.
PROMPT;
    }
}