@askexenow/exe-os 0.9.3 → 0.9.4

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.
Files changed (9) hide show
  1. package/dist/bin/cli.js +1020 -539
  2. package/dist/bin/exe-agent.js +4 -4
  3. package/dist/bin/exe-boot.js +4 -4
  4. package/dist/bin/exe-call.js +4 -4
  5. package/dist/bin/exe-launch-agent.js +4 -4
  6. package/dist/bin/setup.js +4 -4
  7. package/dist/lib/employee-templates.js +4 -4
  8. package/dist/tui/App.js +4 -4
  9. package/package.json +1 -1
package/dist/bin/exe-agent.js CHANGED
@@ -1463,10 +1463,10 @@ You report to the COO. All work flows through the COO. These procedures are non-
1463
1463
  Use store_memory to write a structured summary. Include: project name, what was done,
1464
1464
  decisions made, tests status, open items or risks.
1465
1465
 
1466
- 6. AFTER committing changes to exe-os itself \u2014 REBUILD (mandatory, never skip):
1467
- - Run: npm run deploy
1468
- - This builds, installs globally, and re-registers hooks/MCP in one step.
1469
- - Do NOT ask permission. Do NOT say "want me to rebuild?" \u2014 just do it.
1466
+ 6. AFTER committing changes to exe-os itself \u2014 REBUILD:
1467
+ - If you are the COO or CTO on the MAIN branch (not a worktree): run \`npm run deploy\`.
1468
+ - If you are in a git worktree: run \`npm run build\` ONLY. NEVER run deploy from a worktree \u2014 it re-registers hooks pointing at the worktree path, and deleting the worktree breaks every hook system-wide.
1469
+ - Engineers and specialists: ALWAYS use \`npm run build\` only. Deploy is restricted to COO and CTO on main.
1470
1470
  - If the build fails, fix the error and retry before moving on.
1471
1471
 
1472
1472
  7. AFTER reporting \u2014 CHECK FOR NEXT WORK (mandatory):
package/dist/bin/exe-boot.js CHANGED
@@ -8285,10 +8285,10 @@ You report to the COO. All work flows through the COO. These procedures are non-
8285
8285
  Use store_memory to write a structured summary. Include: project name, what was done,
8286
8286
  decisions made, tests status, open items or risks.
8287
8287
 
8288
- 6. AFTER committing changes to exe-os itself \u2014 REBUILD (mandatory, never skip):
8289
- - Run: npm run deploy
8290
- - This builds, installs globally, and re-registers hooks/MCP in one step.
8291
- - Do NOT ask permission. Do NOT say "want me to rebuild?" \u2014 just do it.
8288
+ 6. AFTER committing changes to exe-os itself \u2014 REBUILD:
8289
+ - If you are the COO or CTO on the MAIN branch (not a worktree): run \`npm run deploy\`.
8290
+ - If you are in a git worktree: run \`npm run build\` ONLY. NEVER run deploy from a worktree \u2014 it re-registers hooks pointing at the worktree path, and deleting the worktree breaks every hook system-wide.
8291
+ - Engineers and specialists: ALWAYS use \`npm run build\` only. Deploy is restricted to COO and CTO on main.
8292
8292
  - If the build fails, fix the error and retry before moving on.
8293
8293
 
8294
8294
  7. AFTER reporting \u2014 CHECK FOR NEXT WORK (mandatory):
package/dist/bin/exe-call.js CHANGED
@@ -596,10 +596,10 @@ You report to the COO. All work flows through the COO. These procedures are non-
596
596
  Use store_memory to write a structured summary. Include: project name, what was done,
597
597
  decisions made, tests status, open items or risks.
598
598
 
599
- 6. AFTER committing changes to exe-os itself \u2014 REBUILD (mandatory, never skip):
600
- - Run: npm run deploy
601
- - This builds, installs globally, and re-registers hooks/MCP in one step.
602
- - Do NOT ask permission. Do NOT say "want me to rebuild?" \u2014 just do it.
599
+ 6. AFTER committing changes to exe-os itself \u2014 REBUILD:
600
+ - If you are the COO or CTO on the MAIN branch (not a worktree): run \`npm run deploy\`.
601
+ - If you are in a git worktree: run \`npm run build\` ONLY. NEVER run deploy from a worktree \u2014 it re-registers hooks pointing at the worktree path, and deleting the worktree breaks every hook system-wide.
602
+ - Engineers and specialists: ALWAYS use \`npm run build\` only. Deploy is restricted to COO and CTO on main.
603
603
  - If the build fails, fix the error and retry before moving on.
604
604
 
605
605
  7. AFTER reporting \u2014 CHECK FOR NEXT WORK (mandatory):
package/dist/bin/exe-launch-agent.js CHANGED
@@ -2019,10 +2019,10 @@ You report to the COO. All work flows through the COO. These procedures are non-
2019
2019
  Use store_memory to write a structured summary. Include: project name, what was done,
2020
2020
  decisions made, tests status, open items or risks.
2021
2021
 
2022
- 6. AFTER committing changes to exe-os itself \u2014 REBUILD (mandatory, never skip):
2023
- - Run: npm run deploy
2024
- - This builds, installs globally, and re-registers hooks/MCP in one step.
2025
- - Do NOT ask permission. Do NOT say "want me to rebuild?" \u2014 just do it.
2022
+ 6. AFTER committing changes to exe-os itself \u2014 REBUILD:
2023
+ - If you are the COO or CTO on the MAIN branch (not a worktree): run \`npm run deploy\`.
2024
+ - If you are in a git worktree: run \`npm run build\` ONLY. NEVER run deploy from a worktree \u2014 it re-registers hooks pointing at the worktree path, and deleting the worktree breaks every hook system-wide.
2025
+ - Engineers and specialists: ALWAYS use \`npm run build\` only. Deploy is restricted to COO and CTO on main.
2026
2026
  - If the build fails, fix the error and retry before moving on.
2027
2027
 
2028
2028
  7. AFTER reporting \u2014 CHECK FOR NEXT WORK (mandatory):
package/dist/bin/setup.js CHANGED
@@ -4400,10 +4400,10 @@ You report to the COO. All work flows through the COO. These procedures are non-
4400
4400
  Use store_memory to write a structured summary. Include: project name, what was done,
4401
4401
  decisions made, tests status, open items or risks.
4402
4402
 
4403
- 6. AFTER committing changes to exe-os itself \u2014 REBUILD (mandatory, never skip):
4404
- - Run: npm run deploy
4405
- - This builds, installs globally, and re-registers hooks/MCP in one step.
4406
- - Do NOT ask permission. Do NOT say "want me to rebuild?" \u2014 just do it.
4403
+ 6. AFTER committing changes to exe-os itself \u2014 REBUILD:
4404
+ - If you are the COO or CTO on the MAIN branch (not a worktree): run \`npm run deploy\`.
4405
+ - If you are in a git worktree: run \`npm run build\` ONLY. NEVER run deploy from a worktree \u2014 it re-registers hooks pointing at the worktree path, and deleting the worktree breaks every hook system-wide.
4406
+ - Engineers and specialists: ALWAYS use \`npm run build\` only. Deploy is restricted to COO and CTO on main.
4407
4407
  - If the build fails, fix the error and retry before moving on.
4408
4408
 
4409
4409
  7. AFTER reporting \u2014 CHECK FOR NEXT WORK (mandatory):
package/dist/lib/employee-templates.js CHANGED
@@ -307,10 +307,10 @@ You report to the COO. All work flows through the COO. These procedures are non-
307
307
  Use store_memory to write a structured summary. Include: project name, what was done,
308
308
  decisions made, tests status, open items or risks.
309
309
 
310
- 6. AFTER committing changes to exe-os itself \u2014 REBUILD (mandatory, never skip):
311
- - Run: npm run deploy
312
- - This builds, installs globally, and re-registers hooks/MCP in one step.
313
- - Do NOT ask permission. Do NOT say "want me to rebuild?" \u2014 just do it.
310
+ 6. AFTER committing changes to exe-os itself \u2014 REBUILD:
311
+ - If you are the COO or CTO on the MAIN branch (not a worktree): run \`npm run deploy\`.
312
+ - If you are in a git worktree: run \`npm run build\` ONLY. NEVER run deploy from a worktree \u2014 it re-registers hooks pointing at the worktree path, and deleting the worktree breaks every hook system-wide.
313
+ - Engineers and specialists: ALWAYS use \`npm run build\` only. Deploy is restricted to COO and CTO on main.
314
314
  - If the build fails, fix the error and retry before moving on.
315
315
 
316
316
  7. AFTER reporting \u2014 CHECK FOR NEXT WORK (mandatory):
package/dist/tui/App.js CHANGED
@@ -16773,10 +16773,10 @@ You report to the COO. All work flows through the COO. These procedures are non-
16773
16773
  Use store_memory to write a structured summary. Include: project name, what was done,
16774
16774
  decisions made, tests status, open items or risks.
16775
16775
 
16776
- 6. AFTER committing changes to exe-os itself \u2014 REBUILD (mandatory, never skip):
16777
- - Run: npm run deploy
16778
- - This builds, installs globally, and re-registers hooks/MCP in one step.
16779
- - Do NOT ask permission. Do NOT say "want me to rebuild?" \u2014 just do it.
16776
+ 6. AFTER committing changes to exe-os itself \u2014 REBUILD:
16777
+ - If you are the COO or CTO on the MAIN branch (not a worktree): run \`npm run deploy\`.
16778
+ - If you are in a git worktree: run \`npm run build\` ONLY. NEVER run deploy from a worktree \u2014 it re-registers hooks pointing at the worktree path, and deleting the worktree breaks every hook system-wide.
16779
+ - Engineers and specialists: ALWAYS use \`npm run build\` only. Deploy is restricted to COO and CTO on main.
16780
16780
  - If the build fails, fix the error and retry before moving on.
16781
16781
 
16782
16782
  7. AFTER reporting \u2014 CHECK FOR NEXT WORK (mandatory):
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@askexenow/exe-os",
3
- "version": "0.9.3",
3
+ "version": "0.9.4",
4
4
  "description": "AI employee operating system — persistent memory, task management, and multi-agent coordination for Claude Code.",
5
5
  "license": "CC-BY-NC-4.0",
6
6
  "type": "module",