ci(examples): add continuous integration for murdoku (#220)

[KayProject]

Background

murdoku is the canonical full-stack reference example (ECS, session keys, multi-step authorization), yet it was the only tier-1 example without an entry in .github/workflows/, leaving regressions undetected until manual verification.

Changes

• Add .github/workflows/murdoku.yml invoking the shared example_reusable.yml, triggered on push/PR to main and develop when examples/murdoku/** (excluding markdown) or the workflow files change — consistent with the other example workflows.
• Remove the misplaced examples/murdoku/src/murdoku.yml that had been committed into the Rust source tree; the new workflow at the correct path supersedes it.
• Bump cougr-core 1.0.0 → 1.1.0 and add the empty [workspace] table every other example carries so the crate resolves standalone.
• Add the Known Limitations section required by EXAMPLE_STANDARD.md §4.

Closes #220

[drips-wave]

@KayProject Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits.

You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀

Learn more about application limits

[salazarsebas]

Review — request changes (blocked by pre-existing syntax error)

The workflow setup is correct: uses example_reusable.yml, removes the misplaced src/murdoku.yml, adds [workspace] to Cargo.toml, and improves the README Known Limitations section.

CI blocker

cargo fmt --check fails because examples/murdoku/src/lib.rs has a duplicate function signature at line 549:

pub fn place_suspect(..., _suspect_idx: u32) -> MoveResult {
pub fn place_suspect(..., suspect_idx: u32) -> MoveResult {

This is a pre-existing bug on main, not introduced by this PR. CI cannot pass until it is fixed.

A fix is being submitted separately to main (fix/murdoku-duplicate-fn-signature). Please rebase onto that commit once merged.

Minor note

The workflow excludes !examples/murdoku/**/*.md from path triggers, so README-only changes will not re-run CI. Consider removing that exclusion so documentation changes that affect build instructions still trigger validation.

Verdict

Rebase after the murdoku syntax fix lands on main, then re-run CI.