@caddis/cli 0.4.26 → 0.4.28
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/bundles/antigravity-plugin/plugin.json +1 -1
- package/bundles/antigravity-plugin/skills/adopt-app/SKILL.md +4 -0
- package/bundles/antigravity-plugin/skills/adopt-app/references/standard.md +18 -5
- package/bundles/antigravity-plugin-extras/plugin.json +1 -1
- package/bundles/antigravity-plugin-extras/skills/hld/references/gold-standard-hld.md +1 -1
- package/bundles/codex/.codex/skills/devops/adopt-app/SKILL.md +4 -0
- package/bundles/codex/.codex/skills/devops/adopt-app/references/standard.md +18 -5
- package/bundles/manifest.json +3 -3
- package/package.json +1 -1
|
@@ -65,6 +65,10 @@ facts - services, scheduled tasks, web sites - can only be read on the box itsel
|
|
|
65
65
|
recorded as NOT SCANNED, never as empty, and it prevents later checks from passing.
|
|
66
66
|
- **Neither committed nor ignored.** Folders in this state are the real hazard: one `git add -A`
|
|
67
67
|
puts them in the history for ever. A filename pattern cannot find them - only git can.
|
|
68
|
+
- **COMMITTED versus not committed**, on every row of "what the repository must not carry". Only
|
|
69
|
+
the committed rows need a history rewrite; the rest need a `.gitignore` line, or already have
|
|
70
|
+
one. The distinction is per FILE, because one folder is routinely both: committed documents
|
|
71
|
+
beside ignored output. Read the row's state before planning any work.
|
|
68
72
|
- **Possible credentials.** The heuristics are tuned to be readable rather than exhaustive: they
|
|
69
73
|
skip comments, type declarations, template references and expressions. **Read every file they
|
|
70
74
|
flag yourself.** A credential that was ever committed must be ROTATED, not only deleted.
|
|
@@ -59,12 +59,25 @@ wrong branch before this is answered means CI builds and tests code nobody ships
|
|
|
59
59
|
|
|
60
60
|
**Blocking.**
|
|
61
61
|
|
|
62
|
-
**Decided by:** `GAP` if either of these is true
|
|
62
|
+
**Decided by:** `GAP` if either of these is true. First, a FILE that git actually tracks also
|
|
63
63
|
matches an excludable content category (dependency, runtime, build-output, cache, db-data,
|
|
64
|
-
archive, data-export
|
|
65
|
-
|
|
66
|
-
`-UntrackedThresholdMB` (default 10 MB). Otherwise `PASS` -
|
|
67
|
-
|
|
64
|
+
archive, data-export or media - `log` is exempt) - something was committed that should not have
|
|
65
|
+
been. Second, a top-level folder is git-untracked, is not `.git`, and is at least
|
|
66
|
+
`-UntrackedThresholdMB` (default 10 MB). Otherwise `PASS` - downgraded to `ASK` if any folder was
|
|
67
|
+
skipped with `-SkipFolder`, or if git could not be run (see "Coverage" below).
|
|
68
|
+
|
|
69
|
+
**Tracked state is per FILE, and that distinction is the whole check.** An earlier version asked
|
|
70
|
+
git for the state of the FOLDER and applied it to every byte inside. A folder is routinely both
|
|
71
|
+
things at once: on a real app, `reports/` held 40 committed markdown documents beside 1,060 MB of
|
|
72
|
+
correctly-ignored run output, under an ignore rule that already existed. The check reported
|
|
73
|
+
`COMMITTED data-export: reports (1018.47 MB)`. The true figure was 0.01 MB in 4 files - wrong by
|
|
74
|
+
about seven thousand times, and wrong in the expensive direction, because it said "rewrite your
|
|
75
|
+
history" when the answer was "nothing to do". The summary now prints `COMMITTED` or
|
|
76
|
+
`not committed` per row, and only the first kind needs a rewrite.
|
|
77
|
+
|
|
78
|
+
`git check-ignore` alone cannot make this distinction: by default it does not report a path that
|
|
79
|
+
git tracks, so the same folder answers "not ignored" plainly and "ignored" under `--no-index`.
|
|
80
|
+
Both answers are true. Only a per-file tracked set says which files are which.
|
|
68
81
|
|
|
69
82
|
**Why it is on the list:** a `.gitignore` added later does not remove what is already committed -
|
|
70
83
|
that needs a history rewrite. And a folder that is neither committed nor ignored is the genuinely
|
|
@@ -139,7 +139,7 @@ The sequence diagram below illustrates the batch execution sequence from cycle t
|
|
|
139
139
|
```mermaid
|
|
140
140
|
sequenceDiagram
|
|
141
141
|
autonumber
|
|
142
|
-
participant Sched as
|
|
142
|
+
participant Sched as Batch Scheduler (PROPOSED - not built)
|
|
143
143
|
participant Orch as Batch Orchestrator
|
|
144
144
|
participant Reader as Tagged-Record Ingestor
|
|
145
145
|
participant Reconcile as Financial Reconciliation Gate
|
|
@@ -65,6 +65,10 @@ facts - services, scheduled tasks, web sites - can only be read on the box itsel
|
|
|
65
65
|
recorded as NOT SCANNED, never as empty, and it prevents later checks from passing.
|
|
66
66
|
- **Neither committed nor ignored.** Folders in this state are the real hazard: one `git add -A`
|
|
67
67
|
puts them in the history for ever. A filename pattern cannot find them - only git can.
|
|
68
|
+
- **COMMITTED versus not committed**, on every row of "what the repository must not carry". Only
|
|
69
|
+
the committed rows need a history rewrite; the rest need a `.gitignore` line, or already have
|
|
70
|
+
one. The distinction is per FILE, because one folder is routinely both: committed documents
|
|
71
|
+
beside ignored output. Read the row's state before planning any work.
|
|
68
72
|
- **Possible credentials.** The heuristics are tuned to be readable rather than exhaustive: they
|
|
69
73
|
skip comments, type declarations, template references and expressions. **Read every file they
|
|
70
74
|
flag yourself.** A credential that was ever committed must be ROTATED, not only deleted.
|
|
@@ -59,12 +59,25 @@ wrong branch before this is answered means CI builds and tests code nobody ships
|
|
|
59
59
|
|
|
60
60
|
**Blocking.**
|
|
61
61
|
|
|
62
|
-
**Decided by:** `GAP` if either of these is true
|
|
62
|
+
**Decided by:** `GAP` if either of these is true. First, a FILE that git actually tracks also
|
|
63
63
|
matches an excludable content category (dependency, runtime, build-output, cache, db-data,
|
|
64
|
-
archive, data-export
|
|
65
|
-
|
|
66
|
-
`-UntrackedThresholdMB` (default 10 MB). Otherwise `PASS` -
|
|
67
|
-
|
|
64
|
+
archive, data-export or media - `log` is exempt) - something was committed that should not have
|
|
65
|
+
been. Second, a top-level folder is git-untracked, is not `.git`, and is at least
|
|
66
|
+
`-UntrackedThresholdMB` (default 10 MB). Otherwise `PASS` - downgraded to `ASK` if any folder was
|
|
67
|
+
skipped with `-SkipFolder`, or if git could not be run (see "Coverage" below).
|
|
68
|
+
|
|
69
|
+
**Tracked state is per FILE, and that distinction is the whole check.** An earlier version asked
|
|
70
|
+
git for the state of the FOLDER and applied it to every byte inside. A folder is routinely both
|
|
71
|
+
things at once: on a real app, `reports/` held 40 committed markdown documents beside 1,060 MB of
|
|
72
|
+
correctly-ignored run output, under an ignore rule that already existed. The check reported
|
|
73
|
+
`COMMITTED data-export: reports (1018.47 MB)`. The true figure was 0.01 MB in 4 files - wrong by
|
|
74
|
+
about seven thousand times, and wrong in the expensive direction, because it said "rewrite your
|
|
75
|
+
history" when the answer was "nothing to do". The summary now prints `COMMITTED` or
|
|
76
|
+
`not committed` per row, and only the first kind needs a rewrite.
|
|
77
|
+
|
|
78
|
+
`git check-ignore` alone cannot make this distinction: by default it does not report a path that
|
|
79
|
+
git tracks, so the same folder answers "not ignored" plainly and "ignored" under `--no-index`.
|
|
80
|
+
Both answers are true. Only a per-file tracked set says which files are which.
|
|
68
81
|
|
|
69
82
|
**Why it is on the list:** a `.gitignore` added later does not remove what is already committed -
|
|
70
83
|
that needs a history rewrite. And a folder that is neither committed nor ignored is the genuinely
|
package/bundles/manifest.json
CHANGED
package/package.json
CHANGED