Architectural Refactor: Narrative Code & Hexagonal Core

[Giwan]

This PR implements a major architectural refactor following the Narrative Code and Hexagonal Architecture principles. Business logic for blog articles, view transitions, accessibility, and tool validation has been extracted into a pure TypeScript domain layer (src/domain). This improves readability, testability, and reduces coupling to the Astro/React framework.

Key changes:

1. Domain Core: Created src/domain/ to house pure business logic.
2. Deconstruction: Reduced TransitionController and AccessibilityManager complexity by delegating to pure functions.
3. SLAP & Narrative: Every new function follows the Single Level of Abstraction Principle and is designed to read like prose.
4. Ports & Adapters: Refactored articleService.ts to implement a repository pattern, decoupling it from the specific browser hydration mechanism.
5. Testing: Achieved high coverage for business rules in isolation.

---

PR created automatically by Jules for task 10118584833999136213 started by @Giwan

[google-labs-jules]

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.

---

For security, I will only act on instructions from the user who triggered this task.

[Giwan]

@jules there is still code in there that can be more DRY. Example:

const errors = issues.filter(i => i.type === 'error').map(i => `${prefix}: ${i.message}`);
  const warnings = issues.filter(i => i.type === 'warning').map(i => `${prefix}: ${i.message}`);

Be sure the maximise the use of small functions so that repeat is minimised.

[Giwan]

@jules also ensure that relevant documentation is updated accordingly. This is a major changed so it should be properly documented.

[google-labs-jules]

@jules there is still code in there that can be more DRY. Example:

const errors = issues.filter(i => i.type === 'error').map(i => `${prefix}: ${i.message}`);
  const warnings = issues.filter(i => i.type === 'warning').map(i => `${prefix}: ${i.message}`);

Be sure the maximise the use of small functions so that repeat is minimised.

Thank you for the feedback, @Giwan. I've refactored validateToolEntry to be more DRY by extracting the issue formatting and predicate logic into small, reusable functions. This maximizes the 'Narrative' style and ensures each piece of logic has a single responsibility.

[Giwan]

@jules from the perspective of a critical reviewer who is very keen on clean code and good architecture, what needs to be fixed in this PR? Divide your findings by severity.

[Giwan]

@jules the search does not seem to be working anymore and in the console there is this:

Uncaught SyntaxError: The requested module 'http://localhost:4321/src/domain/transitions/context.domain.ts' doesn't provide an export named: 'NavigationContext' transitionController.ts:18:3

Use TDD we should have tests to cover these issues.

[Giwan]

@jules there are a bunch more errors in the dev console. Are you not able to see these?

Example:

Uncaught SyntaxError: The requested module 'http://localhost:4321/src/domain/transitions/context.domain.ts' doesn't provide an export named: 'NavigationContext' transitionController.ts:18:3

Have a thorough look at this before replying to me.