Nachbearbeitung: Meilensteinbezüge aus Produktiv-JavaDoc und

package-info entfernt

pdf-umbenenner-adapter-in-cli/src/main/java/de/gecheckt/pdf/umbenenner/adapter/in/cli/SchedulerBatchCommand.java

@@ -12,15 +12,11 @@ import de.gecheckt.pdf.umbenenner.domain.model.BatchRunContext;
  * interface. It receives the batch run outcome and makes it available to the Bootstrap layer
  * for exit code determination and logging.
  * <p>
- * AP-003 Implementation: Minimal no-op command to validate the call chain from CLI to Application.
- * <p>
- * M2-AP-002 Update: Returns {@link BatchRunOutcome} instead of boolean,
- * allowing Bootstrap to systematically derive exit codes (AP-007).
- * <p>
- * M2-AP-003 Update: Accepts {@link BatchRunContext} and passes it to the use case,
+ * Returns {@link BatchRunOutcome} to allow Bootstrap to systematically derive exit codes.
+ * Accepts {@link BatchRunContext} and passes it to the use case,
  * enabling run ID and timing tracking throughout the batch cycle.
  * <p>
- * M2-AP-005 Update: Dependency inversion achieved - this adapter depends only on the
+ * Dependency inversion achieved - this adapter depends only on the
  * BatchRunProcessingUseCase interface, not on any concrete implementation. Bootstrap
  * is responsible for injecting the appropriate use case implementation.
  */

pdf-umbenenner-adapter-in-cli/src/main/java/de/gecheckt/pdf/umbenenner/adapter/in/cli/package-info.java

@@ -8,10 +8,10 @@
  * Components:
  * <ul>
  *   <li>{@link de.gecheckt.pdf.umbenenner.adapter.in.cli.SchedulerBatchCommand}
- *       — CLI entry point that delegates to BatchRunProcessingUseCase interface (AP-005)</li>
+ *       — CLI entry point that delegates to BatchRunProcessingUseCase interface</li>
  * </ul>
  * <p>
- * M2-AP-005 Architecture:
+ * Adapter Architecture:
  * <ul>
  *   <li>Adapter depends on: {@link de.gecheckt.pdf.umbenenner.application.port.in.BatchRunProcessingUseCase} (interface)</li>
  *   <li>Adapter does not depend on: any concrete use case implementation</li>