@codedrifters/configulator 0.0.233 → 0.0.234

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/lib/index.d.mts CHANGED
@@ -1174,10 +1174,12 @@ declare const requirementsAnalystBundle: AgentRuleBundle;
1174
1174
  * returns `true` per this batch's directive that bundles assume peers
1175
1175
  * are present.
1176
1176
  *
1177
- * Ships a single consolidated sub-agent (`requirements-reviewer`) with
1178
- * all 11 review checks lifted from the openhi-planning reviewer skill,
1179
- * a user-invocable skill (`/review-requirements`) that supports four
1180
- * review scopes, and the `req:review` phase label.
1177
+ * Ships a single consolidated sub-agent (`requirements-reviewer`) that
1178
+ * runs in one of two phases per session — `req:review` (the 11-check
1179
+ * audit) or `req:deprecate` (narrow-write deprecation with back-
1180
+ * reference sweep). Two user-invocable skills dispatch the two phases:
1181
+ * `/review-requirements` and `/deprecate-requirement`. Labels declared
1182
+ * here are `req:review` and `req:deprecate`.
1181
1183
  *
1182
1184
  * **Soft dependency on the `requirements-writer` bundle.** This bundle
1183
1185
  * does **not** ship its own copy of the requirement category
@@ -1189,10 +1191,10 @@ declare const requirementsAnalystBundle: AgentRuleBundle;
1189
1191
  *
1190
1192
  * `type:requirement` is intentionally **not** declared here — it is
1191
1193
  * already declared by the `requirements-analyst` bundle and reused.
1192
- * `type:review` is intentionally **not** declared either; review
1193
- * issues use `type:requirement` plus the `req:review` phase label so
1194
- * they share the same queue and triage flow as the rest of the
1195
- * requirements pipeline.
1194
+ * `type:review` is intentionally **not** declared either; review and
1195
+ * deprecate issues both use `type:requirement` plus the matching
1196
+ * phase label so they share the same queue and triage flow as the
1197
+ * rest of the requirements pipeline.
1196
1198
  */
1197
1199
  declare const requirementsReviewerBundle: AgentRuleBundle;
1198
1200
 
package/lib/index.d.ts CHANGED
@@ -1223,10 +1223,12 @@ declare const requirementsAnalystBundle: AgentRuleBundle;
1223
1223
  * returns `true` per this batch's directive that bundles assume peers
1224
1224
  * are present.
1225
1225
  *
1226
- * Ships a single consolidated sub-agent (`requirements-reviewer`) with
1227
- * all 11 review checks lifted from the openhi-planning reviewer skill,
1228
- * a user-invocable skill (`/review-requirements`) that supports four
1229
- * review scopes, and the `req:review` phase label.
1226
+ * Ships a single consolidated sub-agent (`requirements-reviewer`) that
1227
+ * runs in one of two phases per session — `req:review` (the 11-check
1228
+ * audit) or `req:deprecate` (narrow-write deprecation with back-
1229
+ * reference sweep). Two user-invocable skills dispatch the two phases:
1230
+ * `/review-requirements` and `/deprecate-requirement`. Labels declared
1231
+ * here are `req:review` and `req:deprecate`.
1230
1232
  *
1231
1233
  * **Soft dependency on the `requirements-writer` bundle.** This bundle
1232
1234
  * does **not** ship its own copy of the requirement category
@@ -1238,10 +1240,10 @@ declare const requirementsAnalystBundle: AgentRuleBundle;
1238
1240
  *
1239
1241
  * `type:requirement` is intentionally **not** declared here — it is
1240
1242
  * already declared by the `requirements-analyst` bundle and reused.
1241
- * `type:review` is intentionally **not** declared either; review
1242
- * issues use `type:requirement` plus the `req:review` phase label so
1243
- * they share the same queue and triage flow as the rest of the
1244
- * requirements pipeline.
1243
+ * `type:review` is intentionally **not** declared either; review and
1244
+ * deprecate issues both use `type:requirement` plus the matching
1245
+ * phase label so they share the same queue and triage flow as the
1246
+ * rest of the requirements pipeline.
1245
1247
  */
1246
1248
  declare const requirementsReviewerBundle: AgentRuleBundle;
1247
1249