add known issues section for 6.1

[tecpromotion]

We need this so that we can include it in the release notes.

[qodo-code-review]

Review Summary by Qodo

Add known issues documentation for Joomla 6.1

📝 Documentation

Walkthroughs

Description

• Add known issues documentation section for Joomla 6.1
• Create migration guide structure for release notes
• Document workarounds for identified issues

Diagram

flowchart LR
  A["Release Notes"] -- "includes" --> B["Known Issues Section"]
  B -- "documents" --> C["Joomla 6.1 Issues"]
  C -- "provides" --> D["Workarounds"]

Loading

File Changes

1. migrations/60-61/known-issues/index.md 📝 Documentation +9/-0

Create Joomla 6.1 known issues documentation

• Create new known issues documentation file for Joomla 6.1
• Add frontmatter with sidebar position and title metadata
• Include introductory section describing purpose of known issues documentation

migrations/60-61/known-issues/index.md

---

ⓘ You are approaching your monthly quota for Qodo. Upgrade your plan

[qodo-code-review]

Code Review by Qodo

🐞 Bugs (1) 📘 Rule violations (0)

1. Ambiguous empty known-issues 🐞 Bug ⚙ Maintainability

Description

migrations/60-61/known-issues/index.md only contains an intro paragraph and does not list any issues
or explicitly state that there are none, leaving the release-notes section ambiguous. Readers can’t
tell whether there are truly no known issues or the page is incomplete.

Code

migrations/60-61/known-issues/index.md[R6-9]

Evidence

The new page contains only a generic description with no entries or statement of absence. Similar
pages in the repo either list known-issue pages (6.0) or explicitly state there are none yet (6.1
deprecations), demonstrating an established pattern to avoid ambiguity.

migrations/60-61/known-issues/index.md[6-9]
migrations/54-60/known-issues/index.md[6-12]
migrations/60-61/new-deprecations.md[14-16]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

### Issue description
The new 6.1 Known Issues landing page is effectively empty (intro only). This creates ambiguity for release notes: readers can’t tell whether there are no known issues or content is missing.

### Issue Context
Other migration pages in this repo either:
- explicitly state that there are none yet (e.g., New Deprecations), or
- include a list of known-issue subpages/entries (e.g., 6.0 Known Issues index).

### Fix Focus Areas
- Add a short explicit placeholder (e.g., an admonition like `:::tip[Reader Note] No known issues have been documented for Joomla 6.1 yet :::`) and/or a starter list section.

- migrations/60-61/known-issues/index.md[6-9]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

---

ⓘ You are approaching your monthly quota for Qodo. Upgrade your plan

[muhme]

Tested with local installation, empty 6.1 known issues page is working.

[HLeithner]

I'm not happy polluting the area if it might will never be needed.