Problem

When saving a Concept's content, internal links are automatically validated. Judging by its behavior, the current validator can only correctly confirm links to Concepts.

As a result, valid internal links to other fi1osof.ru entities are stripped out as broken.

Example of expected valid links:

• Task: /tasks/[task.id]
• Project: /projects/[project.id]

During the update of the HappyBaby Concept, Markdown links to Tasks and a Project were passed, but after saving, the API returned content where these links had disappeared. Meanwhile, links to Concepts are a supported scenario in the current validation.

What needs to be done

Expand the internal link validation mechanism in the Concept's content so that it understands routes not only for Concepts, but also for other internal entities of the site.

At a minimum, support:

• /tasks/[task.id]
• /projects/[project.id]
• Leave existing links to Concepts without regression.

It is advisable to make the validation extensible by internal route types so that when new entities appear, there is no need to add separate workarounds to the Markdown processor.

Definition of Done

After saving a Concept, valid links to existing Tasks and Projects remain in the content, and genuinely broken internal links continue to be detected/cleaned up according to the current logic.

After the fix, it is necessary to return to the HappyBaby Concept and re-apply cross-linking to the related Tasks, Project, and Concepts.