Adjust calendarsync tsg

.github/skills/charlie-deployment-status/SKILL.md

@@ -0,0 +1,38 @@
+---
+name: charlie-deployment-status
+description: Fast path for checking Charlie stack deployment status in Gitea Actions. Use when asked whether a deploy ran, failed, is queued/running, or what job failed.
+---
+
+# Charlie deployment status
+
+Use this skill with `/charlie-stack-gitea` when the stack name or repository is
+not already known.
+
+Preferred flow:
+
+1. Map the stack to `Charlie/<stack>` from `docs/inventory.md`.
+2. Use repo-scoped Gitea workflow runs for that stack repository. Org-wide run
+   listing may be unavailable with repository-only tokens.
+3. List recent workflow runs first. Include run `id`, `status`, `conclusion`,
+   `event`, `head_branch`, `head_sha`, and `html_url` in notes.
+4. Use status filters when the user asks for failures, successes, or running
+   deployments.
+5. For the chosen run, list workflow jobs and report each job `id`, `name`,
+   `status`, `conclusion`, start/end times, and `html_url`.
+6. Use commit status on `main` or the run `head_sha` to quickly summarize the
+   latest deploy result and job target URL.
+7. Fetch job logs only for failed, cancelled, or non-completed jobs, or when the
+   user asks for details. Logs can be large; search for step markers such as
+   `Failure -`, `Success -`, and `exit status`.
+
+Normal stack deploys use the stack repo workflow under `.gitea/workflows/` and
+call `Charlie/project-charlie/.gitea/workflows/deploy-stack.yml`. The reusable
+workflow job is usually named `deploy`.
+
+Report deployment status in this order:
+
+1. Latest matching run status and conclusion.
+2. Failed or running job, if any.
+3. Commit SHA and event.
+4. Gitea run/job URL.
+5. Short log marker only when a job is not successful.

tsg/calendarsync.md

@@ -45,7 +45,8 @@ user's OAuth credentials are re-bootstrapped.
 **For revoked OAuth tokens (most common):**
 
 ```bash
-cd /mnt/seagate/Dev/charlie/calendarsync
+# Clone: https://gitea.alexandru.macocian.me/Charlie/calendarsync
+cd calendarsync
 
 # Re-bootstrap the user to get fresh tokens
 ./bootstrap/bootstrap.sh --user <username> --force
@@ -146,7 +147,8 @@ fail with this error.
 4. Run the pre-flight validation script:
 
    ```bash
-   cd /mnt/seagate/Dev/charlie/calendarsync
+   # Clone: https://gitea.alexandru.macocian.me/Charlie/calendarsync
+   cd calendarsync
    ./ofelia/validate-config.sh
    ```
 
@@ -155,7 +157,8 @@ fail with this error.
 **If the encryption key was rotated:**
 
 ```bash
-cd /mnt/seagate/Dev/charlie/calendarsync
+# Clone: https://gitea.alexandru.macocian.me/Charlie/calendarsync
+cd calendarsync
 
 # 1. Update the encryption key in secrets
 sops secrets/env.sops.env
@@ -201,7 +204,8 @@ sudo chmod -R 0600 /mnt/nas/data/calendarsync/*/state/auth-storage.yaml
 Then redeploy to re-decrypt files:
 
 ```bash
-cd /mnt/seagate/Dev/charlie/calendarsync && git push  # or manually: docker-compose up
+# Clone: https://gitea.alexandru.macocian.me/Charlie/calendarsync
+cd calendarsync && git push  # or manually: docker-compose up
 ```
 
 ______________________________________________________________________
@@ -281,6 +285,7 @@ long (large calendar):
 **To prevent future hangs, validate before deploying:**
 
 ```bash
-cd /mnt/seagate/Dev/charlie/calendarsync
+# Clone: https://gitea.alexandru.macocian.me/Charlie/calendarsync
+cd calendarsync
 ./ofelia/validate-config.sh
 ```