@askexenow/exe-os 0.9.71 → 0.9.73

package/dist/hooks/instructions-loaded.js

@@ -233,6 +233,9 @@ var init_config = __esm({
         autoInstall: false,
         checkIntervalMs: 24 * 60 * 60 * 1e3
       },
+      support: {
+        bugReportEndpoint: "https://askexe.com/v1/support/bug-reports"
+      },
       orchestration: {
         phase: "phase_1_coo",
         phaseSetBy: "default"
@@ -4133,7 +4136,7 @@ var init_platform_procedures = __esm({
         title: "Customer patch triage \u2014 upstream bug vs customization",
         domain: "support",
         priority: "p0",
-        content: "When an agent encounters a suspected Exe OS bug, update breakage, MCP/tool failure, installer issue, memory/orchestration defect, or customer-local patch need, it MUST use create_bug_report. Do this before or alongside any local workaround so the report reaches AskExe support directly via the customer's license. Classify first: upstream_bug = reproducible exe-os/platform defect; customer_customization = identity, behavior, procedure, config, branding, workflow preference that belongs in customer-owned layers; emergency_hotfix = temporary local patch. For upstream bugs/emergency hotfixes include version, repro steps, expected/actual, files changed, workaround, and local diff summary. Avoid permanent platform-code patches unless founder approves; if a hotfix is unavoidable, document it in the bug report and re-check after npm update."
+        content: "When an agent encounters a suspected Exe OS bug, update breakage, MCP/tool failure, installer issue, memory/orchestration defect, or customer-local patch need, it MUST use create_bug_report. Do this before or alongside any local workaround so the report reaches AskExe support directly via the customer's license. Do NOT ask the founder for permission to file a required bug report. If create_bug_report is deferred/lazy-loaded, load it and call it. If it is unavailable in the live MCP surface, report 'create_bug_report unavailable in this session' and save a local report in exe/output \u2014 never claim the tool does not exist unless the live MCP surface was checked. Classify first: upstream_bug = reproducible exe-os/platform defect; customer_customization = identity, behavior, procedure, config, branding, workflow preference that belongs in customer-owned layers; emergency_hotfix = temporary local patch. For upstream bugs/emergency hotfixes include version, repro steps, expected/actual, files changed, workaround, and local diff summary. Avoid permanent platform-code patches unless founder approves; if a hotfix is unavoidable, document it in the bug report and re-check after npm update."
       },
       // --- Operations ---
       {

package/dist/hooks/notification.js

@@ -233,6 +233,9 @@ var init_config = __esm({
         autoInstall: false,
         checkIntervalMs: 24 * 60 * 60 * 1e3
       },
+      support: {
+        bugReportEndpoint: "https://askexe.com/v1/support/bug-reports"
+      },
       orchestration: {
         phase: "phase_1_coo",
         phaseSetBy: "default"
@@ -4133,7 +4136,7 @@ var init_platform_procedures = __esm({
         title: "Customer patch triage \u2014 upstream bug vs customization",
         domain: "support",
         priority: "p0",
-        content: "When an agent encounters a suspected Exe OS bug, update breakage, MCP/tool failure, installer issue, memory/orchestration defect, or customer-local patch need, it MUST use create_bug_report. Do this before or alongside any local workaround so the report reaches AskExe support directly via the customer's license. Classify first: upstream_bug = reproducible exe-os/platform defect; customer_customization = identity, behavior, procedure, config, branding, workflow preference that belongs in customer-owned layers; emergency_hotfix = temporary local patch. For upstream bugs/emergency hotfixes include version, repro steps, expected/actual, files changed, workaround, and local diff summary. Avoid permanent platform-code patches unless founder approves; if a hotfix is unavoidable, document it in the bug report and re-check after npm update."
+        content: "When an agent encounters a suspected Exe OS bug, update breakage, MCP/tool failure, installer issue, memory/orchestration defect, or customer-local patch need, it MUST use create_bug_report. Do this before or alongside any local workaround so the report reaches AskExe support directly via the customer's license. Do NOT ask the founder for permission to file a required bug report. If create_bug_report is deferred/lazy-loaded, load it and call it. If it is unavailable in the live MCP surface, report 'create_bug_report unavailable in this session' and save a local report in exe/output \u2014 never claim the tool does not exist unless the live MCP surface was checked. Classify first: upstream_bug = reproducible exe-os/platform defect; customer_customization = identity, behavior, procedure, config, branding, workflow preference that belongs in customer-owned layers; emergency_hotfix = temporary local patch. For upstream bugs/emergency hotfixes include version, repro steps, expected/actual, files changed, workaround, and local diff summary. Avoid permanent platform-code patches unless founder approves; if a hotfix is unavoidable, document it in the bug report and re-check after npm update."
       },
       // --- Operations ---
       {

package/dist/hooks/post-compact.js

@@ -244,6 +244,9 @@ var init_config = __esm({
         autoInstall: false,
         checkIntervalMs: 24 * 60 * 60 * 1e3
       },
+      support: {
+        bugReportEndpoint: "https://askexe.com/v1/support/bug-reports"
+      },
       orchestration: {
         phase: "phase_1_coo",
         phaseSetBy: "default"
@@ -4571,7 +4574,7 @@ var init_platform_procedures = __esm({
         title: "Customer patch triage \u2014 upstream bug vs customization",
         domain: "support",
         priority: "p0",
-        content: "When an agent encounters a suspected Exe OS bug, update breakage, MCP/tool failure, installer issue, memory/orchestration defect, or customer-local patch need, it MUST use create_bug_report. Do this before or alongside any local workaround so the report reaches AskExe support directly via the customer's license. Classify first: upstream_bug = reproducible exe-os/platform defect; customer_customization = identity, behavior, procedure, config, branding, workflow preference that belongs in customer-owned layers; emergency_hotfix = temporary local patch. For upstream bugs/emergency hotfixes include version, repro steps, expected/actual, files changed, workaround, and local diff summary. Avoid permanent platform-code patches unless founder approves; if a hotfix is unavoidable, document it in the bug report and re-check after npm update."
+        content: "When an agent encounters a suspected Exe OS bug, update breakage, MCP/tool failure, installer issue, memory/orchestration defect, or customer-local patch need, it MUST use create_bug_report. Do this before or alongside any local workaround so the report reaches AskExe support directly via the customer's license. Do NOT ask the founder for permission to file a required bug report. If create_bug_report is deferred/lazy-loaded, load it and call it. If it is unavailable in the live MCP surface, report 'create_bug_report unavailable in this session' and save a local report in exe/output \u2014 never claim the tool does not exist unless the live MCP surface was checked. Classify first: upstream_bug = reproducible exe-os/platform defect; customer_customization = identity, behavior, procedure, config, branding, workflow preference that belongs in customer-owned layers; emergency_hotfix = temporary local patch. For upstream bugs/emergency hotfixes include version, repro steps, expected/actual, files changed, workaround, and local diff summary. Avoid permanent platform-code patches unless founder approves; if a hotfix is unavoidable, document it in the bug report and re-check after npm update."
       },
       // --- Operations ---
       {

package/dist/hooks/post-tool-combined.js

@@ -309,6 +309,9 @@ var init_config = __esm({
         autoInstall: false,
         checkIntervalMs: 24 * 60 * 60 * 1e3
       },
+      support: {
+        bugReportEndpoint: "https://askexe.com/v1/support/bug-reports"
+      },
       orchestration: {
         phase: "phase_1_coo",
         phaseSetBy: "default"
@@ -4384,7 +4387,7 @@ var init_platform_procedures = __esm({
         title: "Customer patch triage \u2014 upstream bug vs customization",
         domain: "support",
         priority: "p0",
-        content: "When an agent encounters a suspected Exe OS bug, update breakage, MCP/tool failure, installer issue, memory/orchestration defect, or customer-local patch need, it MUST use create_bug_report. Do this before or alongside any local workaround so the report reaches AskExe support directly via the customer's license. Classify first: upstream_bug = reproducible exe-os/platform defect; customer_customization = identity, behavior, procedure, config, branding, workflow preference that belongs in customer-owned layers; emergency_hotfix = temporary local patch. For upstream bugs/emergency hotfixes include version, repro steps, expected/actual, files changed, workaround, and local diff summary. Avoid permanent platform-code patches unless founder approves; if a hotfix is unavoidable, document it in the bug report and re-check after npm update."
+        content: "When an agent encounters a suspected Exe OS bug, update breakage, MCP/tool failure, installer issue, memory/orchestration defect, or customer-local patch need, it MUST use create_bug_report. Do this before or alongside any local workaround so the report reaches AskExe support directly via the customer's license. Do NOT ask the founder for permission to file a required bug report. If create_bug_report is deferred/lazy-loaded, load it and call it. If it is unavailable in the live MCP surface, report 'create_bug_report unavailable in this session' and save a local report in exe/output \u2014 never claim the tool does not exist unless the live MCP surface was checked. Classify first: upstream_bug = reproducible exe-os/platform defect; customer_customization = identity, behavior, procedure, config, branding, workflow preference that belongs in customer-owned layers; emergency_hotfix = temporary local patch. For upstream bugs/emergency hotfixes include version, repro steps, expected/actual, files changed, workaround, and local diff summary. Avoid permanent platform-code patches unless founder approves; if a hotfix is unavoidable, document it in the bug report and re-check after npm update."
       },
       // --- Operations ---
       {

package/dist/hooks/pre-compact.js

@@ -309,6 +309,9 @@ var init_config = __esm({
         autoInstall: false,
         checkIntervalMs: 24 * 60 * 60 * 1e3
       },
+      support: {
+        bugReportEndpoint: "https://askexe.com/v1/support/bug-reports"
+      },
       orchestration: {
         phase: "phase_1_coo",
         phaseSetBy: "default"
@@ -7896,7 +7899,7 @@ var init_platform_procedures = __esm({
         title: "Customer patch triage \u2014 upstream bug vs customization",
         domain: "support",
         priority: "p0",
-        content: "When an agent encounters a suspected Exe OS bug, update breakage, MCP/tool failure, installer issue, memory/orchestration defect, or customer-local patch need, it MUST use create_bug_report. Do this before or alongside any local workaround so the report reaches AskExe support directly via the customer's license. Classify first: upstream_bug = reproducible exe-os/platform defect; customer_customization = identity, behavior, procedure, config, branding, workflow preference that belongs in customer-owned layers; emergency_hotfix = temporary local patch. For upstream bugs/emergency hotfixes include version, repro steps, expected/actual, files changed, workaround, and local diff summary. Avoid permanent platform-code patches unless founder approves; if a hotfix is unavoidable, document it in the bug report and re-check after npm update."
+        content: "When an agent encounters a suspected Exe OS bug, update breakage, MCP/tool failure, installer issue, memory/orchestration defect, or customer-local patch need, it MUST use create_bug_report. Do this before or alongside any local workaround so the report reaches AskExe support directly via the customer's license. Do NOT ask the founder for permission to file a required bug report. If create_bug_report is deferred/lazy-loaded, load it and call it. If it is unavailable in the live MCP surface, report 'create_bug_report unavailable in this session' and save a local report in exe/output \u2014 never claim the tool does not exist unless the live MCP surface was checked. Classify first: upstream_bug = reproducible exe-os/platform defect; customer_customization = identity, behavior, procedure, config, branding, workflow preference that belongs in customer-owned layers; emergency_hotfix = temporary local patch. For upstream bugs/emergency hotfixes include version, repro steps, expected/actual, files changed, workaround, and local diff summary. Avoid permanent platform-code patches unless founder approves; if a hotfix is unavoidable, document it in the bug report and re-check after npm update."
       },
       // --- Operations ---
       {

package/dist/hooks/pre-tool-use.js

@@ -244,6 +244,9 @@ var init_config = __esm({
         autoInstall: false,
         checkIntervalMs: 24 * 60 * 60 * 1e3
       },
+      support: {
+        bugReportEndpoint: "https://askexe.com/v1/support/bug-reports"
+      },
       orchestration: {
         phase: "phase_1_coo",
         phaseSetBy: "default"
@@ -5042,7 +5045,7 @@ var init_platform_procedures = __esm({
         title: "Customer patch triage \u2014 upstream bug vs customization",
         domain: "support",
         priority: "p0",
-        content: "When an agent encounters a suspected Exe OS bug, update breakage, MCP/tool failure, installer issue, memory/orchestration defect, or customer-local patch need, it MUST use create_bug_report. Do this before or alongside any local workaround so the report reaches AskExe support directly via the customer's license. Classify first: upstream_bug = reproducible exe-os/platform defect; customer_customization = identity, behavior, procedure, config, branding, workflow preference that belongs in customer-owned layers; emergency_hotfix = temporary local patch. For upstream bugs/emergency hotfixes include version, repro steps, expected/actual, files changed, workaround, and local diff summary. Avoid permanent platform-code patches unless founder approves; if a hotfix is unavoidable, document it in the bug report and re-check after npm update."
+        content: "When an agent encounters a suspected Exe OS bug, update breakage, MCP/tool failure, installer issue, memory/orchestration defect, or customer-local patch need, it MUST use create_bug_report. Do this before or alongside any local workaround so the report reaches AskExe support directly via the customer's license. Do NOT ask the founder for permission to file a required bug report. If create_bug_report is deferred/lazy-loaded, load it and call it. If it is unavailable in the live MCP surface, report 'create_bug_report unavailable in this session' and save a local report in exe/output \u2014 never claim the tool does not exist unless the live MCP surface was checked. Classify first: upstream_bug = reproducible exe-os/platform defect; customer_customization = identity, behavior, procedure, config, branding, workflow preference that belongs in customer-owned layers; emergency_hotfix = temporary local patch. For upstream bugs/emergency hotfixes include version, repro steps, expected/actual, files changed, workaround, and local diff summary. Avoid permanent platform-code patches unless founder approves; if a hotfix is unavoidable, document it in the bug report and re-check after npm update."
       },
       // --- Operations ---
       {

package/dist/hooks/prompt-submit.js

@@ -309,6 +309,9 @@ var init_config = __esm({
         autoInstall: false,
         checkIntervalMs: 24 * 60 * 60 * 1e3
       },
+      support: {
+        bugReportEndpoint: "https://askexe.com/v1/support/bug-reports"
+      },
       orchestration: {
         phase: "phase_1_coo",
         phaseSetBy: "default"
@@ -4541,7 +4544,7 @@ var init_platform_procedures = __esm({
         title: "Customer patch triage \u2014 upstream bug vs customization",
         domain: "support",
         priority: "p0",
-        content: "When an agent encounters a suspected Exe OS bug, update breakage, MCP/tool failure, installer issue, memory/orchestration defect, or customer-local patch need, it MUST use create_bug_report. Do this before or alongside any local workaround so the report reaches AskExe support directly via the customer's license. Classify first: upstream_bug = reproducible exe-os/platform defect; customer_customization = identity, behavior, procedure, config, branding, workflow preference that belongs in customer-owned layers; emergency_hotfix = temporary local patch. For upstream bugs/emergency hotfixes include version, repro steps, expected/actual, files changed, workaround, and local diff summary. Avoid permanent platform-code patches unless founder approves; if a hotfix is unavoidable, document it in the bug report and re-check after npm update."
+        content: "When an agent encounters a suspected Exe OS bug, update breakage, MCP/tool failure, installer issue, memory/orchestration defect, or customer-local patch need, it MUST use create_bug_report. Do this before or alongside any local workaround so the report reaches AskExe support directly via the customer's license. Do NOT ask the founder for permission to file a required bug report. If create_bug_report is deferred/lazy-loaded, load it and call it. If it is unavailable in the live MCP surface, report 'create_bug_report unavailable in this session' and save a local report in exe/output \u2014 never claim the tool does not exist unless the live MCP surface was checked. Classify first: upstream_bug = reproducible exe-os/platform defect; customer_customization = identity, behavior, procedure, config, branding, workflow preference that belongs in customer-owned layers; emergency_hotfix = temporary local patch. For upstream bugs/emergency hotfixes include version, repro steps, expected/actual, files changed, workaround, and local diff summary. Avoid permanent platform-code patches unless founder approves; if a hotfix is unavoidable, document it in the bug report and re-check after npm update."
       },
       // --- Operations ---
       {

package/dist/hooks/session-end.js

@@ -309,6 +309,9 @@ var init_config = __esm({
         autoInstall: false,
         checkIntervalMs: 24 * 60 * 60 * 1e3
       },
+      support: {
+        bugReportEndpoint: "https://askexe.com/v1/support/bug-reports"
+      },
       orchestration: {
         phase: "phase_1_coo",
         phaseSetBy: "default"
@@ -8105,7 +8108,7 @@ var init_platform_procedures = __esm({
         title: "Customer patch triage \u2014 upstream bug vs customization",
         domain: "support",
         priority: "p0",
-        content: "When an agent encounters a suspected Exe OS bug, update breakage, MCP/tool failure, installer issue, memory/orchestration defect, or customer-local patch need, it MUST use create_bug_report. Do this before or alongside any local workaround so the report reaches AskExe support directly via the customer's license. Classify first: upstream_bug = reproducible exe-os/platform defect; customer_customization = identity, behavior, procedure, config, branding, workflow preference that belongs in customer-owned layers; emergency_hotfix = temporary local patch. For upstream bugs/emergency hotfixes include version, repro steps, expected/actual, files changed, workaround, and local diff summary. Avoid permanent platform-code patches unless founder approves; if a hotfix is unavoidable, document it in the bug report and re-check after npm update."
+        content: "When an agent encounters a suspected Exe OS bug, update breakage, MCP/tool failure, installer issue, memory/orchestration defect, or customer-local patch need, it MUST use create_bug_report. Do this before or alongside any local workaround so the report reaches AskExe support directly via the customer's license. Do NOT ask the founder for permission to file a required bug report. If create_bug_report is deferred/lazy-loaded, load it and call it. If it is unavailable in the live MCP surface, report 'create_bug_report unavailable in this session' and save a local report in exe/output \u2014 never claim the tool does not exist unless the live MCP surface was checked. Classify first: upstream_bug = reproducible exe-os/platform defect; customer_customization = identity, behavior, procedure, config, branding, workflow preference that belongs in customer-owned layers; emergency_hotfix = temporary local patch. For upstream bugs/emergency hotfixes include version, repro steps, expected/actual, files changed, workaround, and local diff summary. Avoid permanent platform-code patches unless founder approves; if a hotfix is unavoidable, document it in the bug report and re-check after npm update."
       },
       // --- Operations ---
       {

package/dist/hooks/session-start.js

@@ -309,6 +309,9 @@ var init_config = __esm({
         autoInstall: false,
         checkIntervalMs: 24 * 60 * 60 * 1e3
       },
+      support: {
+        bugReportEndpoint: "https://askexe.com/v1/support/bug-reports"
+      },
       orchestration: {
         phase: "phase_1_coo",
         phaseSetBy: "default"
@@ -4541,7 +4544,7 @@ var init_platform_procedures = __esm({
         title: "Customer patch triage \u2014 upstream bug vs customization",
         domain: "support",
         priority: "p0",
-        content: "When an agent encounters a suspected Exe OS bug, update breakage, MCP/tool failure, installer issue, memory/orchestration defect, or customer-local patch need, it MUST use create_bug_report. Do this before or alongside any local workaround so the report reaches AskExe support directly via the customer's license. Classify first: upstream_bug = reproducible exe-os/platform defect; customer_customization = identity, behavior, procedure, config, branding, workflow preference that belongs in customer-owned layers; emergency_hotfix = temporary local patch. For upstream bugs/emergency hotfixes include version, repro steps, expected/actual, files changed, workaround, and local diff summary. Avoid permanent platform-code patches unless founder approves; if a hotfix is unavoidable, document it in the bug report and re-check after npm update."
+        content: "When an agent encounters a suspected Exe OS bug, update breakage, MCP/tool failure, installer issue, memory/orchestration defect, or customer-local patch need, it MUST use create_bug_report. Do this before or alongside any local workaround so the report reaches AskExe support directly via the customer's license. Do NOT ask the founder for permission to file a required bug report. If create_bug_report is deferred/lazy-loaded, load it and call it. If it is unavailable in the live MCP surface, report 'create_bug_report unavailable in this session' and save a local report in exe/output \u2014 never claim the tool does not exist unless the live MCP surface was checked. Classify first: upstream_bug = reproducible exe-os/platform defect; customer_customization = identity, behavior, procedure, config, branding, workflow preference that belongs in customer-owned layers; emergency_hotfix = temporary local patch. For upstream bugs/emergency hotfixes include version, repro steps, expected/actual, files changed, workaround, and local diff summary. Avoid permanent platform-code patches unless founder approves; if a hotfix is unavoidable, document it in the bug report and re-check after npm update."
       },
       // --- Operations ---
       {

package/dist/hooks/stop.js

@@ -272,6 +272,9 @@ var init_config = __esm({
         autoInstall: false,
         checkIntervalMs: 24 * 60 * 60 * 1e3
       },
+      support: {
+        bugReportEndpoint: "https://askexe.com/v1/support/bug-reports"
+      },
       orchestration: {
         phase: "phase_1_coo",
         phaseSetBy: "default"
@@ -4615,7 +4618,7 @@ var init_platform_procedures = __esm({
         title: "Customer patch triage \u2014 upstream bug vs customization",
         domain: "support",
         priority: "p0",
-        content: "When an agent encounters a suspected Exe OS bug, update breakage, MCP/tool failure, installer issue, memory/orchestration defect, or customer-local patch need, it MUST use create_bug_report. Do this before or alongside any local workaround so the report reaches AskExe support directly via the customer's license. Classify first: upstream_bug = reproducible exe-os/platform defect; customer_customization = identity, behavior, procedure, config, branding, workflow preference that belongs in customer-owned layers; emergency_hotfix = temporary local patch. For upstream bugs/emergency hotfixes include version, repro steps, expected/actual, files changed, workaround, and local diff summary. Avoid permanent platform-code patches unless founder approves; if a hotfix is unavoidable, document it in the bug report and re-check after npm update."
+        content: "When an agent encounters a suspected Exe OS bug, update breakage, MCP/tool failure, installer issue, memory/orchestration defect, or customer-local patch need, it MUST use create_bug_report. Do this before or alongside any local workaround so the report reaches AskExe support directly via the customer's license. Do NOT ask the founder for permission to file a required bug report. If create_bug_report is deferred/lazy-loaded, load it and call it. If it is unavailable in the live MCP surface, report 'create_bug_report unavailable in this session' and save a local report in exe/output \u2014 never claim the tool does not exist unless the live MCP surface was checked. Classify first: upstream_bug = reproducible exe-os/platform defect; customer_customization = identity, behavior, procedure, config, branding, workflow preference that belongs in customer-owned layers; emergency_hotfix = temporary local patch. For upstream bugs/emergency hotfixes include version, repro steps, expected/actual, files changed, workaround, and local diff summary. Avoid permanent platform-code patches unless founder approves; if a hotfix is unavoidable, document it in the bug report and re-check after npm update."
       },
       // --- Operations ---
       {

package/dist/hooks/subagent-stop.js

@@ -244,6 +244,9 @@ var init_config = __esm({
         autoInstall: false,
         checkIntervalMs: 24 * 60 * 60 * 1e3
       },
+      support: {
+        bugReportEndpoint: "https://askexe.com/v1/support/bug-reports"
+      },
       orchestration: {
         phase: "phase_1_coo",
         phaseSetBy: "default"
@@ -4578,7 +4581,7 @@ var init_platform_procedures = __esm({
         title: "Customer patch triage \u2014 upstream bug vs customization",
         domain: "support",
         priority: "p0",
-        content: "When an agent encounters a suspected Exe OS bug, update breakage, MCP/tool failure, installer issue, memory/orchestration defect, or customer-local patch need, it MUST use create_bug_report. Do this before or alongside any local workaround so the report reaches AskExe support directly via the customer's license. Classify first: upstream_bug = reproducible exe-os/platform defect; customer_customization = identity, behavior, procedure, config, branding, workflow preference that belongs in customer-owned layers; emergency_hotfix = temporary local patch. For upstream bugs/emergency hotfixes include version, repro steps, expected/actual, files changed, workaround, and local diff summary. Avoid permanent platform-code patches unless founder approves; if a hotfix is unavoidable, document it in the bug report and re-check after npm update."
+        content: "When an agent encounters a suspected Exe OS bug, update breakage, MCP/tool failure, installer issue, memory/orchestration defect, or customer-local patch need, it MUST use create_bug_report. Do this before or alongside any local workaround so the report reaches AskExe support directly via the customer's license. Do NOT ask the founder for permission to file a required bug report. If create_bug_report is deferred/lazy-loaded, load it and call it. If it is unavailable in the live MCP surface, report 'create_bug_report unavailable in this session' and save a local report in exe/output \u2014 never claim the tool does not exist unless the live MCP surface was checked. Classify first: upstream_bug = reproducible exe-os/platform defect; customer_customization = identity, behavior, procedure, config, branding, workflow preference that belongs in customer-owned layers; emergency_hotfix = temporary local patch. For upstream bugs/emergency hotfixes include version, repro steps, expected/actual, files changed, workaround, and local diff summary. Avoid permanent platform-code patches unless founder approves; if a hotfix is unavoidable, document it in the bug report and re-check after npm update."
       },
       // --- Operations ---
       {

package/dist/hooks/summary-worker.js

@@ -373,6 +373,9 @@ var init_config = __esm({
         autoInstall: false,
         checkIntervalMs: 24 * 60 * 60 * 1e3
       },
+      support: {
+        bugReportEndpoint: "https://askexe.com/v1/support/bug-reports"
+      },
       orchestration: {
         phase: "phase_1_coo",
         phaseSetBy: "default"
@@ -4177,7 +4180,7 @@ var init_platform_procedures = __esm({
         title: "Customer patch triage \u2014 upstream bug vs customization",
         domain: "support",
         priority: "p0",
-        content: "When an agent encounters a suspected Exe OS bug, update breakage, MCP/tool failure, installer issue, memory/orchestration defect, or customer-local patch need, it MUST use create_bug_report. Do this before or alongside any local workaround so the report reaches AskExe support directly via the customer's license. Classify first: upstream_bug = reproducible exe-os/platform defect; customer_customization = identity, behavior, procedure, config, branding, workflow preference that belongs in customer-owned layers; emergency_hotfix = temporary local patch. For upstream bugs/emergency hotfixes include version, repro steps, expected/actual, files changed, workaround, and local diff summary. Avoid permanent platform-code patches unless founder approves; if a hotfix is unavoidable, document it in the bug report and re-check after npm update."
+        content: "When an agent encounters a suspected Exe OS bug, update breakage, MCP/tool failure, installer issue, memory/orchestration defect, or customer-local patch need, it MUST use create_bug_report. Do this before or alongside any local workaround so the report reaches AskExe support directly via the customer's license. Do NOT ask the founder for permission to file a required bug report. If create_bug_report is deferred/lazy-loaded, load it and call it. If it is unavailable in the live MCP surface, report 'create_bug_report unavailable in this session' and save a local report in exe/output \u2014 never claim the tool does not exist unless the live MCP surface was checked. Classify first: upstream_bug = reproducible exe-os/platform defect; customer_customization = identity, behavior, procedure, config, branding, workflow preference that belongs in customer-owned layers; emergency_hotfix = temporary local patch. For upstream bugs/emergency hotfixes include version, repro steps, expected/actual, files changed, workaround, and local diff summary. Avoid permanent platform-code patches unless founder approves; if a hotfix is unavoidable, document it in the bug report and re-check after npm update."
       },
       // --- Operations ---
       {

package/dist/index.js

@@ -309,6 +309,9 @@ var init_config = __esm({
         autoInstall: false,
         checkIntervalMs: 24 * 60 * 60 * 1e3
       },
+      support: {
+        bugReportEndpoint: "https://askexe.com/v1/support/bug-reports"
+      },
       orchestration: {
         phase: "phase_1_coo",
         phaseSetBy: "default"
@@ -8194,7 +8197,7 @@ var init_platform_procedures = __esm({
         title: "Customer patch triage \u2014 upstream bug vs customization",
         domain: "support",
         priority: "p0",
-        content: "When an agent encounters a suspected Exe OS bug, update breakage, MCP/tool failure, installer issue, memory/orchestration defect, or customer-local patch need, it MUST use create_bug_report. Do this before or alongside any local workaround so the report reaches AskExe support directly via the customer's license. Classify first: upstream_bug = reproducible exe-os/platform defect; customer_customization = identity, behavior, procedure, config, branding, workflow preference that belongs in customer-owned layers; emergency_hotfix = temporary local patch. For upstream bugs/emergency hotfixes include version, repro steps, expected/actual, files changed, workaround, and local diff summary. Avoid permanent platform-code patches unless founder approves; if a hotfix is unavoidable, document it in the bug report and re-check after npm update."
+        content: "When an agent encounters a suspected Exe OS bug, update breakage, MCP/tool failure, installer issue, memory/orchestration defect, or customer-local patch need, it MUST use create_bug_report. Do this before or alongside any local workaround so the report reaches AskExe support directly via the customer's license. Do NOT ask the founder for permission to file a required bug report. If create_bug_report is deferred/lazy-loaded, load it and call it. If it is unavailable in the live MCP surface, report 'create_bug_report unavailable in this session' and save a local report in exe/output \u2014 never claim the tool does not exist unless the live MCP surface was checked. Classify first: upstream_bug = reproducible exe-os/platform defect; customer_customization = identity, behavior, procedure, config, branding, workflow preference that belongs in customer-owned layers; emergency_hotfix = temporary local patch. For upstream bugs/emergency hotfixes include version, repro steps, expected/actual, files changed, workaround, and local diff summary. Avoid permanent platform-code patches unless founder approves; if a hotfix is unavoidable, document it in the bug report and re-check after npm update."
       },
       // --- Operations ---
       {

package/dist/lib/agent-config.js

@@ -106,6 +106,9 @@ var DEFAULT_CONFIG = {
     autoInstall: false,
     checkIntervalMs: 24 * 60 * 60 * 1e3
   },
+  support: {
+    bugReportEndpoint: "https://askexe.com/v1/support/bug-reports"
+  },
   orchestration: {
     phase: "phase_1_coo",
     phaseSetBy: "default"

package/dist/lib/cloud-sync.js

@@ -182,6 +182,9 @@ var init_config = __esm({
         autoInstall: false,
         checkIntervalMs: 24 * 60 * 60 * 1e3
       },
+      support: {
+        bugReportEndpoint: "https://askexe.com/v1/support/bug-reports"
+      },
       orchestration: {
         phase: "phase_1_coo",
         phaseSetBy: "default"

package/dist/lib/config.js

@@ -102,6 +102,9 @@ var DEFAULT_CONFIG = {
     autoInstall: false,
     checkIntervalMs: 24 * 60 * 60 * 1e3
   },
+  support: {
+    bugReportEndpoint: "https://askexe.com/v1/support/bug-reports"
+  },
   orchestration: {
     phase: "phase_1_coo",
     phaseSetBy: "default"

package/dist/lib/consolidation.js

@@ -135,6 +135,9 @@ var init_config = __esm({
         autoInstall: false,
         checkIntervalMs: 24 * 60 * 60 * 1e3
       },
+      support: {
+        bugReportEndpoint: "https://askexe.com/v1/support/bug-reports"
+      },
       orchestration: {
         phase: "phase_1_coo",
         phaseSetBy: "default"

package/dist/lib/database.js

@@ -127,6 +127,9 @@ var init_config = __esm({
         autoInstall: false,
         checkIntervalMs: 24 * 60 * 60 * 1e3
       },
+      support: {
+        bugReportEndpoint: "https://askexe.com/v1/support/bug-reports"
+      },
       orchestration: {
         phase: "phase_1_coo",
         phaseSetBy: "default"

package/dist/lib/db-daemon-client.js

@@ -118,6 +118,9 @@ var DEFAULT_CONFIG = {
     autoInstall: false,
     checkIntervalMs: 24 * 60 * 60 * 1e3
   },
+  support: {
+    bugReportEndpoint: "https://askexe.com/v1/support/bug-reports"
+  },
   orchestration: {
     phase: "phase_1_coo",
     phaseSetBy: "default"

package/dist/lib/db.js

@@ -127,6 +127,9 @@ var init_config = __esm({
         autoInstall: false,
         checkIntervalMs: 24 * 60 * 60 * 1e3
       },
+      support: {
+        bugReportEndpoint: "https://askexe.com/v1/support/bug-reports"
+      },
       orchestration: {
         phase: "phase_1_coo",
         phaseSetBy: "default"

package/dist/lib/device-registry.js

@@ -127,6 +127,9 @@ var init_config = __esm({
         autoInstall: false,
         checkIntervalMs: 24 * 60 * 60 * 1e3
       },
+      support: {
+        bugReportEndpoint: "https://askexe.com/v1/support/bug-reports"
+      },
       orchestration: {
         phase: "phase_1_coo",
         phaseSetBy: "default"

package/dist/lib/embedder.js

@@ -298,6 +298,9 @@ var init_config = __esm({
         autoInstall: false,
         checkIntervalMs: 24 * 60 * 60 * 1e3
       },
+      support: {
+        bugReportEndpoint: "https://askexe.com/v1/support/bug-reports"
+      },
       orchestration: {
         phase: "phase_1_coo",
         phaseSetBy: "default"

package/dist/lib/employee-templates.js

@@ -100,6 +100,9 @@ var init_config = __esm({
         autoInstall: false,
         checkIntervalMs: 24 * 60 * 60 * 1e3
       },
+      support: {
+        bugReportEndpoint: "https://askexe.com/v1/support/bug-reports"
+      },
       orchestration: {
         phase: "phase_1_coo",
         phaseSetBy: "default"
@@ -216,7 +219,7 @@ var PLATFORM_PROCEDURES = [
     title: "Customer patch triage \u2014 upstream bug vs customization",
     domain: "support",
     priority: "p0",
-    content: "When an agent encounters a suspected Exe OS bug, update breakage, MCP/tool failure, installer issue, memory/orchestration defect, or customer-local patch need, it MUST use create_bug_report. Do this before or alongside any local workaround so the report reaches AskExe support directly via the customer's license. Classify first: upstream_bug = reproducible exe-os/platform defect; customer_customization = identity, behavior, procedure, config, branding, workflow preference that belongs in customer-owned layers; emergency_hotfix = temporary local patch. For upstream bugs/emergency hotfixes include version, repro steps, expected/actual, files changed, workaround, and local diff summary. Avoid permanent platform-code patches unless founder approves; if a hotfix is unavoidable, document it in the bug report and re-check after npm update."
+    content: "When an agent encounters a suspected Exe OS bug, update breakage, MCP/tool failure, installer issue, memory/orchestration defect, or customer-local patch need, it MUST use create_bug_report. Do this before or alongside any local workaround so the report reaches AskExe support directly via the customer's license. Do NOT ask the founder for permission to file a required bug report. If create_bug_report is deferred/lazy-loaded, load it and call it. If it is unavailable in the live MCP surface, report 'create_bug_report unavailable in this session' and save a local report in exe/output \u2014 never claim the tool does not exist unless the live MCP surface was checked. Classify first: upstream_bug = reproducible exe-os/platform defect; customer_customization = identity, behavior, procedure, config, branding, workflow preference that belongs in customer-owned layers; emergency_hotfix = temporary local patch. For upstream bugs/emergency hotfixes include version, repro steps, expected/actual, files changed, workaround, and local diff summary. Avoid permanent platform-code patches unless founder approves; if a hotfix is unavoidable, document it in the bug report and re-check after npm update."
   },
   // --- Operations ---
   {

package/dist/lib/employees.js

@@ -121,6 +121,9 @@ var init_config = __esm({
         autoInstall: false,
         checkIntervalMs: 24 * 60 * 60 * 1e3
       },
+      support: {
+        bugReportEndpoint: "https://askexe.com/v1/support/bug-reports"
+      },
       orchestration: {
         phase: "phase_1_coo",
         phaseSetBy: "default"

package/dist/lib/exe-daemon-client.js

@@ -118,6 +118,9 @@ var DEFAULT_CONFIG = {
     autoInstall: false,
     checkIntervalMs: 24 * 60 * 60 * 1e3
   },
+  support: {
+    bugReportEndpoint: "https://askexe.com/v1/support/bug-reports"
+  },
   orchestration: {
     phase: "phase_1_coo",
     phaseSetBy: "default"

package/dist/lib/exe-daemon.js

@@ -309,6 +309,9 @@ var init_config = __esm({
         autoInstall: false,
         checkIntervalMs: 24 * 60 * 60 * 1e3
       },
+      support: {
+        bugReportEndpoint: "https://askexe.com/v1/support/bug-reports"
+      },
       orchestration: {
         phase: "phase_1_coo",
         phaseSetBy: "default"
@@ -5796,7 +5799,7 @@ var init_platform_procedures = __esm({
         title: "Customer patch triage \u2014 upstream bug vs customization",
         domain: "support",
         priority: "p0",
-        content: "When an agent encounters a suspected Exe OS bug, update breakage, MCP/tool failure, installer issue, memory/orchestration defect, or customer-local patch need, it MUST use create_bug_report. Do this before or alongside any local workaround so the report reaches AskExe support directly via the customer's license. Classify first: upstream_bug = reproducible exe-os/platform defect; customer_customization = identity, behavior, procedure, config, branding, workflow preference that belongs in customer-owned layers; emergency_hotfix = temporary local patch. For upstream bugs/emergency hotfixes include version, repro steps, expected/actual, files changed, workaround, and local diff summary. Avoid permanent platform-code patches unless founder approves; if a hotfix is unavoidable, document it in the bug report and re-check after npm update."
+        content: "When an agent encounters a suspected Exe OS bug, update breakage, MCP/tool failure, installer issue, memory/orchestration defect, or customer-local patch need, it MUST use create_bug_report. Do this before or alongside any local workaround so the report reaches AskExe support directly via the customer's license. Do NOT ask the founder for permission to file a required bug report. If create_bug_report is deferred/lazy-loaded, load it and call it. If it is unavailable in the live MCP surface, report 'create_bug_report unavailable in this session' and save a local report in exe/output \u2014 never claim the tool does not exist unless the live MCP surface was checked. Classify first: upstream_bug = reproducible exe-os/platform defect; customer_customization = identity, behavior, procedure, config, branding, workflow preference that belongs in customer-owned layers; emergency_hotfix = temporary local patch. For upstream bugs/emergency hotfixes include version, repro steps, expected/actual, files changed, workaround, and local diff summary. Avoid permanent platform-code patches unless founder approves; if a hotfix is unavoidable, document it in the bug report and re-check after npm update."
       },
       // --- Operations ---
       {

package/dist/lib/hybrid-search.js

@@ -362,6 +362,9 @@ var init_config = __esm({
         autoInstall: false,
         checkIntervalMs: 24 * 60 * 60 * 1e3
       },
+      support: {
+        bugReportEndpoint: "https://askexe.com/v1/support/bug-reports"
+      },
       orchestration: {
         phase: "phase_1_coo",
         phaseSetBy: "default"
@@ -4129,7 +4132,7 @@ var init_platform_procedures = __esm({
         title: "Customer patch triage \u2014 upstream bug vs customization",
         domain: "support",
         priority: "p0",
-        content: "When an agent encounters a suspected Exe OS bug, update breakage, MCP/tool failure, installer issue, memory/orchestration defect, or customer-local patch need, it MUST use create_bug_report. Do this before or alongside any local workaround so the report reaches AskExe support directly via the customer's license. Classify first: upstream_bug = reproducible exe-os/platform defect; customer_customization = identity, behavior, procedure, config, branding, workflow preference that belongs in customer-owned layers; emergency_hotfix = temporary local patch. For upstream bugs/emergency hotfixes include version, repro steps, expected/actual, files changed, workaround, and local diff summary. Avoid permanent platform-code patches unless founder approves; if a hotfix is unavoidable, document it in the bug report and re-check after npm update."
+        content: "When an agent encounters a suspected Exe OS bug, update breakage, MCP/tool failure, installer issue, memory/orchestration defect, or customer-local patch need, it MUST use create_bug_report. Do this before or alongside any local workaround so the report reaches AskExe support directly via the customer's license. Do NOT ask the founder for permission to file a required bug report. If create_bug_report is deferred/lazy-loaded, load it and call it. If it is unavailable in the live MCP surface, report 'create_bug_report unavailable in this session' and save a local report in exe/output \u2014 never claim the tool does not exist unless the live MCP surface was checked. Classify first: upstream_bug = reproducible exe-os/platform defect; customer_customization = identity, behavior, procedure, config, branding, workflow preference that belongs in customer-owned layers; emergency_hotfix = temporary local patch. For upstream bugs/emergency hotfixes include version, repro steps, expected/actual, files changed, workaround, and local diff summary. Avoid permanent platform-code patches unless founder approves; if a hotfix is unavoidable, document it in the bug report and re-check after npm update."
       },
       // --- Operations ---
       {

package/dist/lib/identity.js

@@ -100,6 +100,9 @@ var init_config = __esm({
         autoInstall: false,
         checkIntervalMs: 24 * 60 * 60 * 1e3
       },
+      support: {
+        bugReportEndpoint: "https://askexe.com/v1/support/bug-reports"
+      },
       orchestration: {
         phase: "phase_1_coo",
         phaseSetBy: "default"

package/dist/lib/license.js

@@ -103,6 +103,9 @@ var DEFAULT_CONFIG = {
     autoInstall: false,
     checkIntervalMs: 24 * 60 * 60 * 1e3
   },
+  support: {
+    bugReportEndpoint: "https://askexe.com/v1/support/bug-reports"
+  },
   orchestration: {
     phase: "phase_1_coo",
     phaseSetBy: "default"

package/dist/lib/messaging.js

@@ -123,6 +123,9 @@ var init_config = __esm({
         autoInstall: false,
         checkIntervalMs: 24 * 60 * 60 * 1e3
       },
+      support: {
+        bugReportEndpoint: "https://askexe.com/v1/support/bug-reports"
+      },
       orchestration: {
         phase: "phase_1_coo",
         phaseSetBy: "default"

package/dist/lib/reminders.js

@@ -100,6 +100,9 @@ var init_config = __esm({
         autoInstall: false,
         checkIntervalMs: 24 * 60 * 60 * 1e3
       },
+      support: {
+        bugReportEndpoint: "https://askexe.com/v1/support/bug-reports"
+      },
       orchestration: {
         phase: "phase_1_coo",
         phaseSetBy: "default"

package/dist/lib/schedules.js

@@ -288,6 +288,9 @@ var init_config = __esm({
         autoInstall: false,
         checkIntervalMs: 24 * 60 * 60 * 1e3
       },
+      support: {
+        bugReportEndpoint: "https://askexe.com/v1/support/bug-reports"
+      },
       orchestration: {
         phase: "phase_1_coo",
         phaseSetBy: "default"
@@ -3358,7 +3361,7 @@ var init_platform_procedures = __esm({
         title: "Customer patch triage \u2014 upstream bug vs customization",
         domain: "support",
         priority: "p0",
-        content: "When an agent encounters a suspected Exe OS bug, update breakage, MCP/tool failure, installer issue, memory/orchestration defect, or customer-local patch need, it MUST use create_bug_report. Do this before or alongside any local workaround so the report reaches AskExe support directly via the customer's license. Classify first: upstream_bug = reproducible exe-os/platform defect; customer_customization = identity, behavior, procedure, config, branding, workflow preference that belongs in customer-owned layers; emergency_hotfix = temporary local patch. For upstream bugs/emergency hotfixes include version, repro steps, expected/actual, files changed, workaround, and local diff summary. Avoid permanent platform-code patches unless founder approves; if a hotfix is unavoidable, document it in the bug report and re-check after npm update."
+        content: "When an agent encounters a suspected Exe OS bug, update breakage, MCP/tool failure, installer issue, memory/orchestration defect, or customer-local patch need, it MUST use create_bug_report. Do this before or alongside any local workaround so the report reaches AskExe support directly via the customer's license. Do NOT ask the founder for permission to file a required bug report. If create_bug_report is deferred/lazy-loaded, load it and call it. If it is unavailable in the live MCP surface, report 'create_bug_report unavailable in this session' and save a local report in exe/output \u2014 never claim the tool does not exist unless the live MCP surface was checked. Classify first: upstream_bug = reproducible exe-os/platform defect; customer_customization = identity, behavior, procedure, config, branding, workflow preference that belongs in customer-owned layers; emergency_hotfix = temporary local patch. For upstream bugs/emergency hotfixes include version, repro steps, expected/actual, files changed, workaround, and local diff summary. Avoid permanent platform-code patches unless founder approves; if a hotfix is unavoidable, document it in the bug report and re-check after npm update."
       },
       // --- Operations ---
       {

package/dist/lib/skill-learning.js

@@ -298,6 +298,9 @@ var init_config = __esm({
         autoInstall: false,
         checkIntervalMs: 24 * 60 * 60 * 1e3
       },
+      support: {
+        bugReportEndpoint: "https://askexe.com/v1/support/bug-reports"
+      },
       orchestration: {
         phase: "phase_1_coo",
         phaseSetBy: "default"

package/dist/lib/store.js

@@ -297,6 +297,9 @@ var init_config = __esm({
         autoInstall: false,
         checkIntervalMs: 24 * 60 * 60 * 1e3
       },
+      support: {
+        bugReportEndpoint: "https://askexe.com/v1/support/bug-reports"
+      },
       orchestration: {
         phase: "phase_1_coo",
         phaseSetBy: "default"
@@ -3358,7 +3361,7 @@ var init_platform_procedures = __esm({
         title: "Customer patch triage \u2014 upstream bug vs customization",
         domain: "support",
         priority: "p0",
-        content: "When an agent encounters a suspected Exe OS bug, update breakage, MCP/tool failure, installer issue, memory/orchestration defect, or customer-local patch need, it MUST use create_bug_report. Do this before or alongside any local workaround so the report reaches AskExe support directly via the customer's license. Classify first: upstream_bug = reproducible exe-os/platform defect; customer_customization = identity, behavior, procedure, config, branding, workflow preference that belongs in customer-owned layers; emergency_hotfix = temporary local patch. For upstream bugs/emergency hotfixes include version, repro steps, expected/actual, files changed, workaround, and local diff summary. Avoid permanent platform-code patches unless founder approves; if a hotfix is unavoidable, document it in the bug report and re-check after npm update."
+        content: "When an agent encounters a suspected Exe OS bug, update breakage, MCP/tool failure, installer issue, memory/orchestration defect, or customer-local patch need, it MUST use create_bug_report. Do this before or alongside any local workaround so the report reaches AskExe support directly via the customer's license. Do NOT ask the founder for permission to file a required bug report. If create_bug_report is deferred/lazy-loaded, load it and call it. If it is unavailable in the live MCP surface, report 'create_bug_report unavailable in this session' and save a local report in exe/output \u2014 never claim the tool does not exist unless the live MCP surface was checked. Classify first: upstream_bug = reproducible exe-os/platform defect; customer_customization = identity, behavior, procedure, config, branding, workflow preference that belongs in customer-owned layers; emergency_hotfix = temporary local patch. For upstream bugs/emergency hotfixes include version, repro steps, expected/actual, files changed, workaround, and local diff summary. Avoid permanent platform-code patches unless founder approves; if a hotfix is unavoidable, document it in the bug report and re-check after npm update."
       },
       // --- Operations ---
       {

package/dist/lib/task-router.js

@@ -100,6 +100,9 @@ var init_config = __esm({
         autoInstall: false,
         checkIntervalMs: 24 * 60 * 60 * 1e3
       },
+      support: {
+        bugReportEndpoint: "https://askexe.com/v1/support/bug-reports"
+      },
       orchestration: {
         phase: "phase_1_coo",
         phaseSetBy: "default"

package/dist/lib/tasks.js

@@ -316,6 +316,9 @@ var init_config = __esm({
         autoInstall: false,
         checkIntervalMs: 24 * 60 * 60 * 1e3
       },
+      support: {
+        bugReportEndpoint: "https://askexe.com/v1/support/bug-reports"
+      },
       orchestration: {
         phase: "phase_1_coo",
         phaseSetBy: "default"