[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M76V3R2ZXYQGEX78VRE8KZCT":3,"skill-same:01M76V3R2ZXYQGEX78VRE8KZCT":69},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":46,"commitSha":47,"skillDirectory":48,"forksCount":49,"repositoryHtmlUrl":50,"repositoryHomepageUrl":51,"ownerHtmlUrl":52,"ownerBlogUrl":6,"ownerDescription":53,"updatedAt":54,"install":55,"resources":68},"01M76V3R2ZXYQGEX78VRE8KZCT","test-seed-uniqueness",null,"Ensure test seed data never causes unique constraint violations — UUID-based, timestamp-based, counter-based, or Faker patterns for any field with a UNIQUE index, primary key, or slug constraint.","lukemcqueen\u002Fsteadfaste-fleet","lukemcqueen","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F405240?v=4","01M757MHPAGRXTJAT46SKZP98R","Luke McQueen","01M757MHPZ573KP8DT9GB8SBQ7",4,"MIT","https:\u002F\u002Fgithub.com\u002Flukemcqueen\u002Fsteadfaste-fleet\u002Fblob\u002Fmain\u002Fskills\u002Fsoftware-development\u002Ftest-seed-uniqueness\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: test-seed-uniqueness\nversion: 1.0.0\ncategory: software-development\ndescription: \"Ensure test seed data never causes unique constraint violations — UUID-based, timestamp-based, counter-based, or Faker patterns for any field with a UNIQUE index, primary key, or slug constraint.\"\nauthor: Hermes Agent\nlicense: MIT\nplatforms: [linux, macos, windows]\nmetadata:\n  hermes:\n    tags: [testing, seed-data, factories, fixtures, database, uniqueness, pytest, factory-boy]\n    related_skills: [change-test-loop, subagent-driven-development, root-cause-debugging]\n---\n\n# Test Seed Data — Uniqueness Discipline\n\n## The Problem\n\nEvery test needs seed data. Agents instinctively write:\n\n```python\nuser = User.objects.create(email=\"alice@example.com\", username=\"alice\")\n```\n\nThis works *once*. On the next test run, or when tests run in parallel, or when a second test also creates an alice:\n\n```\ndjango.db.utils.IntegrityError: duplicate key value violates unique constraint\n```\n\nThe agent didn't do anything wrong — it just picked a *natural-looking* value for a field that happens to have a `UNIQUE` constraint. The database doesn't care how pretty the data is; it cares about uniqueness.\n\n## The Rule\n\n**Every value inserted into a uniquely-constrained field MUST be dynamically unique at runtime.**\n\nHardcoded strings in seed data are only safe for:\n- Non-unique fields (e.g., `display_name`, `bio`, `age`)\n- Enum-like fields (e.g., `status=\"active\"`, `role=\"admin\"`)\n- Reference data that's de-duplicated by the test setup (e.g., loaded once from JSON)\n\nEverything else — emails, usernames, slugs, external IDs, phone numbers, API keys, invite codes, profile handles — gets the dynamic treatment.\n\n## Failure Detection\n\nWhen you see any of these in test output, stop and fix the seed data:\n\n| Error Pattern | Likely Source |\n|---|---|\n| `duplicate key value violates unique constraint` | PostgreSQL |\n| `UNIQUE constraint failed` | SQLite |\n| `E11000 duplicate key error` | MongoDB |\n| `Duplicate entry '...' for key` | MySQL |\n| `unique constraint \"...\" violated` | Generic ORM |\n| `already exists.` | Rails \u002F Active Record |\n| `IntegrityError: (1062, \"Duplicate entry` | MySQL via ORM |\n\n**First debugging step when seeing these:** Look at the test's seed data or fixtures. Find the field whose value is hardcoded. Make it dynamic.\n\n## Dynamic Uniqueness Patterns\n\n### Pattern 1 — UUID (Best for Primary Keys & External IDs)\n\n```python\nimport uuid\n\ndef test_create_user():\n    user = User.objects.create(\n        id=uuid.uuid4(),\n        email=f\"user-{uuid.uuid4()}@example.com\",\n    )\n```\n\n**Use when:** The value is never shown to a human in tests. IDs, tokens, API keys.\n\n### Pattern 2 — Timestamp (Best for Ordered, Human-Readable Slugs)\n\n```python\nfrom datetime import datetime\n\nslug = f\"test-project-{datetime.now().strftime('%Y%m%d%H%M%S%f')}\"\n```\n\n**Use when:** You want roughly ordered test data, or the field appears in logs\u002Foutput.\n\n### Pattern 3 — Counter (Best for Sequential Batch Tests)\n\n```python\nfrom itertools import count\n\n_user_counter = count(1)\n\ndef make_user(email=None):\n    n = next(_user_counter)\n    return User.objects.create(\n        email=email or f\"user{n}@example.com\",\n        username=f\"user{n}\",\n    )\n```\n\n**Use when:** Creating multiple objects in a loop or parameterized test.\n\n### Pattern 4 — Random Hex Suffix (Best for Short, Readable Values)\n\n```python\nimport secrets\n\nsuffix = secrets.token_hex(4)  # 8-char hex, e.g. \"a3f1b2c8\"\nemail = f\"alice-{suffix}@example.com\"\n```\n\n**Use when:** You want something shorter than a full UUID but still practically unique.\n\n### Pattern 5 — Faker (Best for Realistic, Human-Readable Data)\n\n```python\nfrom faker import Faker\nfake = Faker()\n\nemail = fake.unique.email()\nname = fake.unique.name()\n```\n\n**Use when:** Tests need realistic-looking data, or you're already using Faker. The `.unique` property ensures no collisions within the generator session.\n\n### Pattern 6 — factory_boy Sequences (Best for Complex Fixtures)\n\n```python\nimport factory\n\nclass UserFactory(factory.django.DjangoModelFactory):\n    class Meta:\n        model = User\n\n    email = factory.Sequence(lambda n: f\"user{n}@example.com\")\n    username = factory.Sequence(lambda n: f\"user{n}\")\n\n# Usage — each call gets a unique email\u002Fusername\nuser1 = UserFactory()\nuser2 = UserFactory()\n```\n\n**Use when:** You have many fields and many tests. factory_boy Sequences are the gold standard — zero boilerplate, fully automatic, works with `SubFactory`.\n\n### Pattern 7 — pytest Fixture with Scope\n\n```python\nimport pytest\n\n@pytest.fixture\ndef unique_user():\n    suffix = secrets.token_hex(4)\n    user = User.objects.create(\n        email=f\"test-{suffix}@example.com\",\n        username=f\"test-{suffix}\",\n    )\n    yield user\n    user.delete()\n```\n\n**Use when:** Many tests need a user and you want DRY setup with guaranteed cleanup.\n\n## Complementary Anti-Patterns (What NOT to Do)\n\n| ❌ Anti-Pattern | Why It Fails | ✅ Fix |\n|---|---|---|\n| `email=\"alice@example.com\"` | Second test or re-run collision | `f\"alice-{uuid.uuid4()}@example.com\"` |\n| `User.objects.create()` without cleanup in non-transactional tests | Data leaks between tests | Use `@pytest.mark.django_db(transaction=True)` or fixture with teardown |\n| `User.objects.all().delete()` at start of test | Race condition in parallel tests | Use `secrets.token_hex()` or factory |\n| Copy-pasting seed data across test files | Same hardcoded values in multiple files | Extract a shared factory or fixture |\n| Using `datetime.now()` at second precision | Collision when tests run in same second | Use microsecond precision (`%f`) or UUID |\n| `UserFactory()` without unique guarantees on special fields | Factory inherits hardcoded defaults | Override with `Sequence` or pass unique values |\n\n## Model-Specific Ref Detection\n\nBefore writing seed data, identify the model's unique constraints:\n\n```python\n# Django\nclass Meta:\n    unique_together = [[\"organization\", \"slug\"]]\n    constraints = [\n        models.UniqueConstraint(fields=[\"tenant\", \"external_id\"], name=\"unique_tenant_external\")\n    ]\n\n# SQLAlchemy\n__table_args__ = (\n    UniqueConstraint(\"tenant_id\", \"external_id\", name=\"uq_tenant_external\"),\n)\n\n# Prisma \u002F Rails \u002F etc. — check schema.rb, schema.prisma, or migrations\n```\n\n**Fields to always make unique:**\n- `id` \u002F `pk` (unless using auto-increment — then let the DB handle it)\n- `email`\n- `username`\n- `slug`\n- `external_id` \u002F `stripe_id` \u002F `github_id` — any third-party ID\n- `api_key` \u002F `token` \u002F `secret`\n- `invite_code` \u002F `referral_code`\n- `phone_number`\n- `handle` \u002F `display_handle` \u002F `profile_url`\n- Any field with `unique=True`, `unique_together`, or `UniqueConstraint`\n\n## Integration with change-test-loop\n\nWhen the RED phase fails not because the test logic is wrong but because of a unique constraint violation:\n\n1. Don't change the test logic — the test is correct\n2. Fix the **seed data** to use a dynamic uniqueness pattern\n3. Re-score RED: the test should now fail for the intended reason (feature missing)\n\nWhen GREEN phase passes but seed data has hardcoded unique fields: this is a REFACTOR concern — dynamize the seed data while keeping tests green.\n\n## Verification\n\nBefore declaring seed data done:\n\n```\n✅ Every uniquely-constrained field uses a dynamic pattern (UUID, timestamp, counter, or Faker)\n✅ No hardcoded alice@example.com, testuser, demo-slug, or similar in seed data\n✅ Tests pass on re-run without cleanup\n✅ Tests pass in parallel (xdist or similar)\n✅ factory_boy fixtures use Sequence() for all unique fields\n✅ Non-unique fields are still readable\u002Fhuman-friendly (don't over-randomize)\n```\n","# Test Seed Data — Uniqueness Discipline\n\n## The Problem\n\nEvery test needs seed data. Agents instinctively write:\n\n```python\nuser = User.objects.create(email=\"alice@example.com\", username=\"alice\")\n```\n\nThis works *once*. On the next test run, or when tests run in parallel, or when a second test also creates an alice:\n\n```\ndjango.db.utils.IntegrityError: duplicate key value violates unique constraint\n```\n\nThe agent didn't do anything wrong — it just picked a *natural-looking* value for a field that happens to have a `UNIQUE` constraint. The database doesn't care how pretty the data is; it cares about uniqueness.\n\n## The Rule\n\n**Every value inserted into a uniquely-constrained field MUST be dynamically unique at runtime.**\n\nHardcoded strings in seed data are only safe for:\n- Non-unique fields (e.g., `display_name`, `bio`, `age`)\n- Enum-like fields (e.g., `status=\"active\"`, `role=\"admin\"`)\n- Reference data that's de-duplicated by the test setup (e.g., loaded once from JSON)\n\nEverything else — emails, usernames, slugs, external IDs, phone numbers, API keys, invite codes, profile handles — gets the dynamic treatment.\n\n## Failure Detection\n\nWhen you see any of these in test output, stop and fix the seed data:\n\n| Error Pattern | Likely Source |\n|---|---|\n| `duplicate key value violates unique constraint` | PostgreSQL |\n| `UNIQUE constraint failed` | SQLite |\n| `E11000 duplicate key error` | MongoDB |\n| `Duplicate entry '...' for key` | MySQL |\n| `unique constraint \"...\" violated` | Generic ORM |\n| `already exists.` | Rails \u002F Active Record |\n| `IntegrityError: (1062, \"Duplicate entry` | MySQL via ORM |\n\n**First debugging step when seeing these:** Look at the test's seed data or fixtures. Find the field whose value is hardcoded. Make it dynamic.\n\n## Dynamic Uniqueness Patterns\n\n### Pattern 1 — UUID (Best for Primary Keys & External IDs)\n\n```python\nimport uuid\n\ndef test_create_user():\n    user = User.objects.create(\n        id=uuid.uuid4(),\n        email=f\"user-{uuid.uuid4()}@example.com\",\n    )\n```\n\n**Use when:** The value is never shown to a human in tests. IDs, tokens, API keys.\n\n### Pattern 2 — Timestamp (Best for Ordered, Human-Readable Slugs)\n\n```python\nfrom datetime import datetime\n\nslug = f\"test-project-{datetime.now().strftime('%Y%m%d%H%M%S%f')}\"\n```\n\n**Use when:** You want roughly ordered test data, or the field appears in logs\u002Foutput.\n\n### Pattern 3 — Counter (Best for Sequential Batch Tests)\n\n```python\nfrom itertools import count\n\n_user_counter = count(1)\n\ndef make_user(email=None):\n    n = next(_user_counter)\n    return User.objects.create(\n        email=email or f\"user{n}@example.com\",\n        username=f\"user{n}\",\n    )\n```\n\n**Use when:** Creating multiple objects in a loop or parameterized test.\n\n### Pattern 4 — Random Hex Suffix (Best for Short, Readable Values)\n\n```python\nimport secrets\n\nsuffix = secrets.token_hex(4)  # 8-char hex, e.g. \"a3f1b2c8\"\nemail = f\"alice-{suffix}@example.com\"\n```\n\n**Use when:** You want something shorter than a full UUID but still practically unique.\n\n### Pattern 5 — Faker (Best for Realistic, Human-Readable Data)\n\n```python\nfrom faker import Faker\nfake = Faker()\n\nemail = fake.unique.email()\nname = fake.unique.name()\n```\n\n**Use when:** Tests need realistic-looking data, or you're already using Faker. The `.unique` property ensures no collisions within the generator session.\n\n### Pattern 6 — factory_boy Sequences (Best for Complex Fixtures)\n\n```python\nimport factory\n\nclass UserFactory(factory.django.DjangoModelFactory):\n    class Meta:\n        model = User\n\n    email = factory.Sequence(lambda n: f\"user{n}@example.com\")\n    username = factory.Sequence(lambda n: f\"user{n}\")\n\n# Usage — each call gets a unique email\u002Fusername\nuser1 = UserFactory()\nuser2 = UserFactory()\n```\n\n**Use when:** You have many fields and many tests. factory_boy Sequences are the gold standard — zero boilerplate, fully automatic, works with `SubFactory`.\n\n### Pattern 7 — pytest Fixture with Scope\n\n```python\nimport pytest\n\n@pytest.fixture\ndef unique_user():\n    suffix = secrets.token_hex(4)\n    user = User.objects.create(\n        email=f\"test-{suffix}@example.com\",\n        username=f\"test-{suffix}\",\n    )\n    yield user\n    user.delete()\n```\n\n**Use when:** Many tests need a user and you want DRY setup with guaranteed cleanup.\n\n## Complementary Anti-Patterns (What NOT to Do)\n\n| ❌ Anti-Pattern | Why It Fails | ✅ Fix |\n|---|---|---|\n| `email=\"alice@example.com\"` | Second test or re-run collision | `f\"alice-{uuid.uuid4()}@example.com\"` |\n| `User.objects.create()` without cleanup in non-transactional tests | Data leaks between tests | Use `@pytest.mark.django_db(transaction=True)` or fixture with teardown |\n| `User.objects.all().delete()` at start of test | Race condition in parallel tests | Use `secrets.token_hex()` or factory |\n| Copy-pasting seed data across test files | Same hardcoded values in multiple files | Extract a shared factory or fixture |\n| Using `datetime.now()` at second precision | Collision when tests run in same second | Use microsecond precision (`%f`) or UUID |\n| `UserFactory()` without unique guarantees on special fields | Factory inherits hardcoded defaults | Override with `Sequence` or pass unique values |\n\n## Model-Specific Ref Detection\n\nBefore writing seed data, identify the model's unique constraints:\n\n```python\n# Django\nclass Meta:\n    unique_together = [[\"organization\", \"slug\"]]\n    constraints = [\n        models.UniqueConstraint(fields=[\"tenant\", \"external_id\"], name=\"unique_tenant_external\")\n    ]\n\n# SQLAlchemy\n__table_args__ = (\n    UniqueConstraint(\"tenant_id\", \"external_id\", name=\"uq_tenant_external\"),\n)\n\n# Prisma \u002F Rails \u002F etc. — check schema.rb, schema.prisma, or migrations\n```\n\n**Fields to always make unique:**\n- `id` \u002F `pk` (unless using auto-increment — then let the DB handle it)\n- `email`\n- `username`\n- `slug`\n- `external_id` \u002F `stripe_id` \u002F `github_id` — any third-party ID\n- `api_key` \u002F `token` \u002F `secret`\n- `invite_code` \u002F `referral_code`\n- `phone_number`\n- `handle` \u002F `display_handle` \u002F `profile_url`\n- Any field with `unique=True`, `unique_together`, or `UniqueConstraint`\n\n## Integration with change-test-loop\n\nWhen the RED phase fails not because the test logic is wrong but because of a unique constraint violation:\n\n1. Don't change the test logic — the test is correct\n2. Fix the **seed data** to use a dynamic uniqueness pattern\n3. Re-score RED: the test should now fail for the intended reason (feature missing)\n\nWhen GREEN phase passes but seed data has hardcoded unique fields: this is a REFACTOR concern — dynamize the seed data while keeping tests green.\n\n## Verification\n\nBefore declaring seed data done:\n\n```\n✅ Every uniquely-constrained field uses a dynamic pattern (UUID, timestamp, counter, or Faker)\n✅ No hardcoded alice@example.com, testuser, demo-slug, or similar in seed data\n✅ Tests pass on re-run without cleanup\n✅ Tests pass in parallel (xdist or similar)\n✅ factory_boy fixtures use Sequence() for all unique fields\n✅ Non-unique fields are still readable\u002Fhuman-friendly (don't over-randomize)\n```\n",{"name":5,"author":24,"license":15,"version":25,"category":26,"metadata":27,"platforms":42,"description":7},"Hermes Agent","1.0.0","software-development",{"hermes":28},{"tags":29,"related_skills":38},[30,31,32,33,34,35,36,37],"testing","seed-data","factories","fixtures","database","uniqueness","pytest","factory-boy",[39,40,41],"change-test-loop","subagent-driven-development","root-cause-debugging",[43,44,45],"linux","macos","windows","main","6509c2742680f6f230c89044437ab43c0e29d530","skills\u002Fsoftware-development\u002Ftest-seed-uniqueness",1,"https:\u002F\u002Fgithub.com\u002Flukemcqueen\u002Fsteadfaste-fleet","steadfaste.com","https:\u002F\u002Fgithub.com\u002Flukemcqueen","AI Architect | Building Hermes Cortex: governed multi-agent AI for autonomous software engineering | Enterprise Tech Consultant","2026-11-14 22:33:34",{"source":8,"skillName":5,"commands":56,"prompt":66,"zipAvailable":67},[57,60,63],{"tool":58,"command":59},"npx","npx skills add lukemcqueen\u002Fsteadfaste-fleet --skill test-seed-uniqueness",{"tool":61,"command":62},"bunx","bunx skills add lukemcqueen\u002Fsteadfaste-fleet --skill test-seed-uniqueness",{"tool":64,"command":65},"pnpm","pnpm dlx skills add lukemcqueen\u002Fsteadfaste-fleet --skill test-seed-uniqueness","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flukemcqueen\u002Fsteadfaste-fleet\u002Fblob\u002Fmain\u002Fskills\u002Fsoftware-development\u002Ftest-seed-uniqueness\u002FSKILL.md",true,[],[70,78,85,92,99,106],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":77},"01M7DXY4G8NSVB59K8B6S2AQNP","macbook-linux-maintenance","Legacy MacBook Linux fixes: GPU wedge, reboot hang, thermal.","https:\u002F\u002Fgithub.com\u002Flukemcqueen\u002Fsteadfaste-fleet\u002Fblob\u002Fmain\u002Fskills\u002Fdevops\u002Fmacbook-linux-maintenance\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":77},"01M7DXXYJCXFJ3TGB84ZQ8KFE6","governance-regression-triage","Triage a host's governance issues: what changed.","https:\u002F\u002Fgithub.com\u002Flukemcqueen\u002Fsteadfaste-fleet\u002Fblob\u002Fmain\u002Fskills\u002Fdevops\u002Fgovernance-regression-triage\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":77},"01M7DXXSAP1G8FDRJAMXQGBBMK","enforcement-immutability","Use when enforcement files lose their immutable flag.","https:\u002F\u002Fgithub.com\u002Flukemcqueen\u002Fsteadfaste-fleet\u002Fblob\u002Fmain\u002Fskills\u002Fdevops\u002Fenforcement-immutability\u002FSKILL.md",[],[],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":77},"01M78SSDQVRYX64Y16X32TC0NS","steadfaste-fleet-repo-deploy","Use when committing to the steadfaste-fleet repo.","https:\u002F\u002Fgithub.com\u002Flukemcqueen\u002Fsteadfaste-fleet\u002Fblob\u002Fmain\u002Fskills\u002Fdevops\u002Fsteadfaste-fleet-repo-deploy\u002FSKILL.md",[],[],{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":77},"01M78SS928F3R2RJAYVW4E30CE","steadfaste-fleet-maintenance","Maintain an installed Steadfaste Fleet instance — update both the upstream Hermes Agent and the fleet repo layer, merge diverged histories, sync skills safely, and troubleshoot common issues. Covers the dual-update workflow (hermes update + fleet-update.sh), encrypted brain data backup, mycortex import, and recovery techniques.","https:\u002F\u002Fgithub.com\u002Flukemcqueen\u002Fsteadfaste-fleet\u002Fblob\u002Fmain\u002Fskills\u002Fdevops\u002Fsteadfaste-fleet-maintenance\u002FSKILL.md",[],[],{"skillNo":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":110,"categories":111,"keywords":112,"publishedAt":77},"01M78SP1CHW0T0BWE5ZT6JBPX8","fleet-preflight","DEPRECATED alias — merged into survey-before-action (2026-08-20). Load survey-before-action instead; its \"Repo-Specific Pre-Flight\" section covers git search, Hermes boundary, and deployment verification.","https:\u002F\u002Fgithub.com\u002Flukemcqueen\u002Fsteadfaste-fleet\u002Fblob\u002Fmain\u002Fskills\u002Fdevops\u002Ffleet-preflight\u002FSKILL.md",[],[]]