fix(spec): complete a truncated @SPEC anchor in TaskSequenceMapper

gate-46 spec-anchor-existence was failing this branch on a file it does not
touch. The anchor on line 122 stops mid-word:

    #requirement-an-approval-is-an-ordered-task-sequence-with-o

Lines 26 and 62 in the same file carry the full, correct anchor
(`...-with-one-position-enabled-at-a-time`), and the heading it names exists.
So this is a truncation, not a rename, and it arrived with f3f4abc on
development -- which means development is red on this gate too, independently
of this PR.

Fixed here because it blocks this branch and is one line. After it, a full-tree
scan of lib/, tests/ and src/ reports zero unresolved @SPEC targets.

Author: Conduction Release Bot

lib/Db/TaskSequenceMapper.php

@@ -119,7 +119,7 @@ public function findRunning(string $anchorObjectUuid, string $templateId): ?Task
 	 *
 	 * @return TaskSequence|null The newest sequence for the template, or null when none has run.
 	 *
-	 * @spec openspec/changes/flow-approval-consolidation/specs/flow-approval-consolidation/spec.md#requirement-an-approval-is-an-ordered-task-sequence-with-o
+	 * @spec openspec/changes/flow-approval-consolidation/specs/flow-approval-consolidation/spec.md#requirement-an-approval-is-an-ordered-task-sequence-with-one-position-enabled-at-a-time
 	 */
 	public function findNewestForTemplate(string $templateId): ?TaskSequence {
 		$qb = $this->db->getQueryBuilder();