mass publis with cascade

[SalvadorDalia]

Added information about cascade publishing from objects table

[rgembalik]

@ReviewPhin review

[reviewphin-flotiq]

Review summary

Overall assessment

I did not find an actionable issue in the changed files. The panel page now separates single-object and mass actions more clearly, and the API page adds an important limitation for batch endpoints.

Merge readiness

• Status: Ready
• Confidence: High
• Rationale: Ready to merge as documented; the changed content reads coherently and does not introduce a concrete correctness problem in the reviewed scope.

Snapshot

• Overall severity: Low
• Scope reviewed: 2 changed files on feature/mass-publish -> main

Highlights

• Bulk publish, unpublish, and archive flows are easier to scan after splitting them into dedicated subsections.
• The added API warning makes the batch-endpoint cascade limitation explicit.

Next Steps

• Once you and your team are satisfied with the changes you can merge this branch since there are no actionable findings left.
• Apply suggested changes directly from eligible inline review comments, or reply when a finding needs clarification.
• Use the Run Review action on the ReviewPhin Check Run after pushing changes, or comment /reviewphin review, to request another review.