Correct the copyright headers and pin the examples to '@v1'.

Following 3504431: only the files carrying the lineage of the 2024 script keep "Copyright © 2024-2026 Patrick
Lehmann". 'action.yml' is that script and 'LICENSE.md' is the repository's licence, so both keep it;
'Pipeline.yml' and the 'check-outputs' action are new work and now carry the pyTooling Authors alone, like
'UpdateVersionBranch.yml' already does.

The README's usage example pins '@v1' and the note saying no version has been released is gone - it would have
been false the moment the release it ships in is published. A sentence explaining the major-version branch and
'@v1.0.0' for a single release takes its place.

Co-Authored-By: Patrick Lehmann <Paebbels@gmail.com>
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01RnpaXYDwfNwnJrQew78j3f

Author: 3 people

.github/actions/check-outputs/action.yml

@@ -1,6 +1,5 @@
 # The MIT License (MIT)
 #
-# Copyright © 2024-2026 Patrick Lehmann
 # Copyright © 2026 The pyTooling Authors
 #
 # Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated

.github/workflows/Pipeline.yml

@@ -1,6 +1,5 @@
 # The MIT License (MIT)
 #
-# Copyright © 2024-2026 Patrick Lehmann
 # Copyright © 2026 The pyTooling Authors
 #
 # Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated

README.md

@@ -50,7 +50,7 @@ jobs:
         uses: actions/checkout@v6
 
       - name: 🔄 Synchronize forked repositories
-        uses: pyTooling/SynchronizeForks@main
+        uses: pyTooling/SynchronizeForks@v1
         with:
           github-token: ${{ secrets.GH_TOKEN }}
 ```
@@ -59,8 +59,8 @@ That is the whole workflow. The forks are expected in the namespace the workflow
 (`${{ github.repository_owner }}`) and the configuration files are read from the repository's root directory; see
 [Input Parameters](#input-parameters) to change either.
 
-> [!NOTE]
-> No version tag has been released yet, so the examples reference `@main`. Once released, pin a version tag as usual.
+`@v1` is the major-version branch, moved to each release by the [pipeline](#pipeline). Pin `@v1.0.0` instead to hold
+a single release.
 
 ### The Entry Point: `.ALL.repos`