Refactor MQTT course and bound backend message processing

Move lesson source into the teaching structure, align the course path with the learner's Go and DevOps experience, and add the interactive lesson guides. Add advanced DevOps lifecycle study as a separate section.

Bound MQTT message work and drain accepted jobs during shutdown; align the backend implementation with the revised course through Section 6.

docs/agents/domain.md

@@ -0,0 +1,17 @@
+# Domain Docs
+
+This is a single-context repository. Engineering skills should use the root glossary and ADR directory when exploring domain concepts or decisions.
+
+## Before exploring
+
+- Read `GLOSSARY.md` at the repository root when it exists.
+- Read relevant decisions under `docs/adr/` when that directory exists.
+- If either is absent, proceed without flagging it or creating it just for setup. Domain-modeling work can create these documents when it resolves terminology or a decision.
+
+## Use the glossary's vocabulary
+
+When an output names a domain concept, use the term defined in `GLOSSARY.md`. If a needed concept is not defined, note the gap for domain-modeling work rather than inventing a competing term.
+
+## Flag ADR conflicts
+
+If a proposed change conflicts with an existing ADR, identify the ADR and explain the conflict instead of silently overriding it.

docs/agents/issue-tracker.md

@@ -0,0 +1,21 @@
+# Issue tracker: Local Markdown with Gitea as a companion
+
+The local issue tracker is the source of truth for this repository. Store issues and specifications as Markdown files under `.scratch/`.
+
+## Local conventions
+
+- Use one directory per feature or effort: `.scratch/<feature-slug>/`.
+- Store its specification at `.scratch/<feature-slug>/spec.md`.
+- Store implementation issues in `.scratch/<feature-slug>/issues/<NN>-<slug>.md`, numbered from `01`, one issue per file.
+- Record triage state in a `Status:` line near the top of each issue file; use the mappings in `docs/agents/triage-labels.md`.
+- Append comments and conversation history under a `## Comments` heading.
+
+## Gitea Issues
+
+Gitea Issues may also be used as a companion tracker. The repository remote supplied by the user is `ssh://git@git.my-rm.com:2222/Robot-Market/mqtt-5-learning.git`. There is no automatic synchronization: when an issue is represented in both places, keep the local Markdown file authoritative and include the corresponding Gitea issue link there. Do not assume a Gitea CLI or API workflow is configured.
+
+## Skill operations
+
+- When a skill says to publish an issue or specification, create the local Markdown file under `.scratch/<feature-slug>/`.
+- When a skill says to fetch a ticket, read the referenced local file; the user may provide its path or issue number.
+- For wayfinding, store the map at `.scratch/<effort>/map.md` and child tickets under `.scratch/<effort>/issues/`. Child tickets use `Type:` (`research`, `prototype`, `grilling`, or `task`), `Status:` (`claimed` or `resolved`), and an optional `Blocked by:` list. Claim by setting `Status: claimed`; resolve by adding an `## Answer`, setting `Status: resolved`, and adding a context pointer to the map's Decisions-so-far.

docs/agents/triage-labels.md

@@ -0,0 +1,13 @@
+# Triage Labels
+
+The skills use five canonical triage roles. Use these same strings in local issue `Status:` lines and, when mirroring an issue in Gitea, as its labels.
+
+| Label in mattpocock/skills | Label in this repo | Meaning |
+| --- | --- | --- |
+| `needs-triage` | `needs-triage` | Maintainer needs to evaluate this issue |
+| `needs-info` | `needs-info` | Waiting on the reporter for more information |
+| `ready-for-agent` | `ready-for-agent` | Fully specified and ready for an agent |
+| `ready-for-human` | `ready-for-human` | Requires human implementation |
+| `wontfix` | `wontfix` | Will not be actioned |
+
+When a skill mentions a triage role, use the corresponding label string from this table.