feat(boards2): add core flagging logic

[x1unix]

Closes #3146

[Gno2D2]

🛠 PR Checks Summary

🔴 Maintainers must be able to edit this pull request (more info)

Manual Checks (for Reviewers):

• IGNORE the bot requirements for this PR (force green CI check)
• The pull request description provides enough details

Read More

🤖 This bot helps streamline PR reviews by verifying automated checks and providing guidance for contributors and reviewers.

✅ Automated Checks (for Contributors):

🔴 Maintainers must be able to edit this pull request (more info)

☑️ Contributor Actions:

1. Fix any issues flagged by automated checks.
2. Follow the Contributor Checklist to ensure your PR is ready for review.
   • Add new tests, or document why they are unnecessary.
   • Provide clear examples/screenshots, if necessary.
   • Update documentation, if required.
   • Ensure no breaking changes, or include BREAKING CHANGE notes.
   • Link related issues/PRs, where applicable.

☑️ Reviewer Actions:

1. Complete manual checks for the PR, including the guidelines and additional checks if applicable.

📚 Resources:

• Report a bug with the bot.
• View the bot’s configuration file.

Debug

Automated Checks

Maintainers must be able to edit this pull request (more info)

If

🟢 Condition met
└── 🟢 The pull request was created from a fork (head branch repo: gnostudio/gno)

Then

🔴 Requirement not satisfied
└── 🔴 Maintainer can modify this pull request

Manual Checks

**IGNORE** the bot requirements for this PR (force green CI check)

If

🟢 Condition met
└── 🟢 On every pull request

Can be checked by

• Any user with comment edit permission

The pull request description provides enough details

If

🟢 Condition met
└── 🟢 Not (🔴 Pull request author is a member of the team: core-contributors)

Can be checked by

• team core-contributors

[codecov]

Codecov Report

Attention: Patch coverage is 70.17544% with 289 lines in your changes missing coverage. Please review.

Files with missing lines	Patch %	Lines
gno.land/pkg/integration/testscript_gnoland.go	68.76%	137 Missing and 32 partials ⚠️
gno.land/pkg/integration/process.go	69.53%	62 Missing and 23 partials ⚠️
gno.land/pkg/integration/pkgloader.go	65.68%	26 Missing and 9 partials ⚠️

📢 Thoughts on this report? Let us know!

[jeronimoalbi]

@x1unix #3386 was merged so anytime you can bring the changes to this branch which have the assertHasBoardPermission() assertion needed for this PR

[x1unix]

@jeronimoalbi does assertHasBoardPermission supports global superusers (someone who can manage a whole realm)?

[jeronimoalbi]

@jeronimoalbi does assertHasBoardPermission supports global superusers (someone who can manage a whole realm)?

No, only members of the board being checked

[x1unix]

@jeronimoalbi so both checks are necessary?

If true - maybe assertHasBoardPerm needs to be updated.

[jeronimoalbi]

@jeronimoalbi so both checks are necessary?

If true - maybe assertHasBoardPerm needs to be updated.

I can't think of a case where both should be checked. Boards are independent communities which are independent of the governing body (permissions) assigned to the realm. In fact the realm can have a minimal impact on boards in very specific cases and only if the board creator opts in to be like that, like for example adding new members to a board in cases where access is lost, but overall each board is independent, so permissions for functionalities triggered by board members/users must be checked against that specific board instance.

[x1unix]

@jeronimoalbi

Boards are independent communities which are independent of the governing body (permissions) assigned to the realm.

This can be risky, especially if board decide to post something NSFW or something that violates a law. I believe we should've some safeguard mechanism for that case.

[x1unix]

@jeronimoalbi PR reopened in #3451