declapract-typescript-ehmpathy 0.49.8 → 0.49.9

package/dist/practices/cicd-app-react-native-expo/best-practice/.declapract.readme.md

@@ -0,0 +1,27 @@
+the cicd workflows and gitignore for an expo app
+
+this practice declares `android/` and `ios/` — the build output `expo prebuild` emits, which is
+scratch in a managed-workflow repo.
+
+📖 several practices declare this same `.gitignore`. the contract they share — one shared
+algorithm, the ordered tail, what a new declarer owes — is stated once at
+`.agent/repo=.this/role=any/briefs/howto.declare-the-repo-gitignore.md`. read that before you add
+a line here.
+
+## this declaration once went stale, and that is why it imports
+
+it was authored 2024-09-11, cloned from the `git` practice's shape at the time. `git` gained its
+ordered tail in #404 on 2026-01-31, and this copy never caught up — so it sorted every line,
+which hoisted the `!` negations above their target and turned them inert.
+
+fixed 2026-07-30 (#537) by an import of the shared algorithm rather than a re-derivation.
+consumers saw no content change: an expo repo already received the ordered tail from `git`; what
+changed is that this practice no longer hoists it.
+
+the clamp is `.gitignore.declapract.test.ts` → `convergence with the git practice`, which asserts
+both checks pass once both have run, that the settled file is a fixed point under either, and
+that the negations stay below `node_modules`.
+
+⚠️ its declared set is **disjoint** from git's, so neither practice's output alone satisfies the
+other's check — both must run. this differs from `rhachet`, whose one line is a subset of git's.
+do not copy an assertion between those two suites without that check.

package/dist/practices/cicd-app-react-native-expo/best-practice/.gitignore.declapract.ts

@@ -1,21 +1,28 @@
 import type { FileCheckFunction, FileFixFunction } from 'declapract';
-import { dedupe } from 'domain-objects';
 import expect from 'expect';
 
-const expectedIgnores = ['android/', 'ios/'].sort();
+import { defineExpectedGitignoreContents } from '../../../utils/defineExpectedGitignoreContents';
 
-const defineExpectedContents = (contents: string | null): string => {
-  const ignoresAlreadyDefined = contents ? contents.split('\n') : [];
-  const finalLines = dedupe([...ignoresAlreadyDefined, ...expectedIgnores])
-    .sort() // sorted
-    .filter((line) => !!line); // without empty lines
-  return [...finalLines.sort(), ''].join('\n');
-};
+/**
+ * .what = the ignores this practice declares — the build output an expo app emits
+ * .why  = `android/` and `ios/` are generated by `expo prebuild`, so they are scratch
+ *         in a managed-workflow repo.
+ * .note = this list is NOT sorted here, and that is deliberate.
+ *         `defineExpectedGitignoreContents` sorts the union of these lines with the
+ *         repo's own, so a `.sort()` at this site would be a second sort that changes
+ *         no output -- while it mutates a module-cached array in place. `readonly`
+ *         forbids that mutation outright.
+ */
+const ignoresSortable: readonly string[] = ['android/', 'ios/'];
 
 export const check: FileCheckFunction = (contents) => {
-  expect(contents).toEqual(defineExpectedContents(contents));
+  expect(contents).toEqual(
+    defineExpectedGitignoreContents({ contents, ignoresSortable }),
+  );
 };
 
 export const fix: FileFixFunction = (contents) => {
-  return { contents: defineExpectedContents(contents) };
+  return {
+    contents: defineExpectedGitignoreContents({ contents, ignoresSortable }),
+  };
 };