author --validate-protocols, instructor --check-protocols, @PROT_CHECK

[RYZENNAVI]

Command Protocol Checking Function

A new function for automated validation of command-line execution logs has been implemented for SeDriLa.

Main Features

• sedrila author --validate-protocols: Validate @PROT_CHECK annotation syntax in protocol files
• sedrila instructor --check-protocols: Compare student submissions against author-provided examples
• Single-file validation: Verify individual .prot files during development

Characteristics

• Support for flexible matching rules (exact, regex, multi-variant, skip)
• Stage-independent validation for all protocol files
• Output formats: Console summary, JSON, Markdown reports

[RYZENNAVI]

Feedback from @prechelt in #18

Some of the functionalities you have already implemented belong into sedrila author and should be performed each time the course is generated. This presumably includes --validate-snippets and --validate-protocols.

These functions need to be integrated into sedrila's incremental build mechanism (the heart of which is elements.py). This is complicated to understand, but is designed and documented well; see internal_notes.md. Take your time to understand it.

The point of this is to run those checks only in those cases, where relevant content actually has changed.
Keep the current, mostly task-level granularity of the incremental build; there is no need to make it finer still.

These functions should provide error messages and warnings in the same style as the other build functions. Expect the number of messages to be small; expect them to be used (and the problems cleaned up) immediately.
There is no point in generating a separate JSON or Markdown report in addition.

[RYZENNAVI]

Command Protocol Validation feedback implemented

• Integrated into incremental build: Validation runs automatically during sedrila author builds
• Removed --validate-protocols command-line arguments from author subcommand
• Removed report

Detailed documentation in docs/authors.md (section 2.3.2), docs/instructors.md (section 2.3)