@link-assistant/hive-mind 1.67.0 → 1.67.1

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/CHANGELOG.md CHANGED
@@ -1,5 +1,11 @@
1
1
  # @link-assistant/hive-mind
2
2
 
3
+ ## 1.67.1
4
+
5
+ ### Patch Changes
6
+
7
+ - d37f752: Working session summary now always appears before the working session log on every PR comment thread. The per-iteration code in auto-restart-until-mergeable mode and watch / temporary auto-restart mode now posts the summary comment before uploading the log, matching the existing top-level flow.
8
+
3
9
  ## 1.67.0
4
10
 
5
11
  ### Minor Changes
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@link-assistant/hive-mind",
3
- "version": "1.67.0",
3
+ "version": "1.67.1",
4
4
  "description": "AI-powered issue solver and hive mind for collaborative problem solving",
5
5
  "main": "src/hive.mjs",
6
6
  "type": "module",
@@ -857,6 +857,43 @@ No further AI sessions will be started automatically for this run. Please review
857
857
  }
858
858
  }
859
859
 
860
+ // Issue #1761: Post the working session **summary** BEFORE uploading
861
+ // the working session **log** so the summary always appears above
862
+ // the log in PR comment chronological order. The summary acts as a
863
+ // human-readable header for the (potentially very long) log that
864
+ // follows, and reordering matches the top-level flow in
865
+ // src/solve.mjs (which calls maybeAttachWorkingSessionSummary
866
+ // before verifyResults / attachLogToGitHub).
867
+ //
868
+ // Issue #1728: Attach a "Working session summary" comment for this
869
+ // iteration if the AI didn't post any comments of its own (and
870
+ // --auto-attach-solution-summary is enabled, which it is by default).
871
+ // Before this fix, only the top-level solve.mjs flow honoured this
872
+ // flag, so iterations inside auto-restart-until-mergeable silently
873
+ // dropped the AI's last message — see #1728.
874
+ try {
875
+ await maybeAttachWorkingSessionSummary({
876
+ argv,
877
+ resultSummary: toolResult.resultSummary,
878
+ workStartTime: iterationStartTime,
879
+ owner,
880
+ repo,
881
+ prNumber,
882
+ issueNumber,
883
+ success: true,
884
+ });
885
+ } catch (summaryError) {
886
+ reportError(summaryError, {
887
+ context: 'attach_auto_restart_working_session_summary',
888
+ prNumber,
889
+ owner,
890
+ repo,
891
+ iteration,
892
+ operation: 'attach_working_session_summary',
893
+ });
894
+ await log(formatAligned('', `⚠️ Working session summary error: ${cleanErrorMessage(summaryError)}`, '', 2));
895
+ }
896
+
860
897
  // Attach log if enabled
861
898
  const shouldAttachLogs = argv.attachLogs || argv['attach-logs'];
862
899
  if (prNumber && shouldAttachLogs) {
@@ -905,35 +942,6 @@ No further AI sessions will be started automatically for this run. Please review
905
942
  }
906
943
  }
907
944
 
908
- // Issue #1728: Attach a "Working session summary" comment for this
909
- // iteration if the AI didn't post any comments of its own (and
910
- // --auto-attach-solution-summary is enabled, which it is by default).
911
- // Before this fix, only the top-level solve.mjs flow honoured this
912
- // flag, so iterations inside auto-restart-until-mergeable silently
913
- // dropped the AI's last message — see #1728.
914
- try {
915
- await maybeAttachWorkingSessionSummary({
916
- argv,
917
- resultSummary: toolResult.resultSummary,
918
- workStartTime: iterationStartTime,
919
- owner,
920
- repo,
921
- prNumber,
922
- issueNumber,
923
- success: true,
924
- });
925
- } catch (summaryError) {
926
- reportError(summaryError, {
927
- context: 'attach_auto_restart_working_session_summary',
928
- prNumber,
929
- owner,
930
- repo,
931
- iteration,
932
- operation: 'attach_working_session_summary',
933
- });
934
- await log(formatAligned('', `⚠️ Working session summary error: ${cleanErrorMessage(summaryError)}`, '', 2));
935
- }
936
-
937
945
  await log('');
938
946
  await log(formatAligned('✅', `${argv.tool.toUpperCase()} execution completed:`, 'Checking if PR is now mergeable...'));
939
947
  }
@@ -421,6 +421,42 @@ export const watchForFeedback = async params => {
421
421
  }
422
422
  }
423
423
 
424
+ // Issue #1761: Post the working session **summary** BEFORE uploading
425
+ // the working session **log** so the summary always appears above
426
+ // the log in PR comment chronological order. The summary acts as a
427
+ // human-readable header for the (potentially very long) log that
428
+ // follows, and reordering matches the top-level flow in
429
+ // src/solve.mjs (which calls maybeAttachWorkingSessionSummary
430
+ // before verifyResults / attachLogToGitHub).
431
+ //
432
+ // Issue #1728: Attach a "Working session summary" comment for this
433
+ // iteration if the AI didn't post any comments of its own (and
434
+ // --auto-attach-solution-summary is enabled, which it is by default).
435
+ // Same fix as in solve.auto-merge.lib.mjs — every working session,
436
+ // not just the top-level run, should honour the auto-attach flag.
437
+ try {
438
+ await maybeAttachWorkingSessionSummary({
439
+ argv,
440
+ resultSummary: toolResult.resultSummary,
441
+ workStartTime: iterationStartTime,
442
+ owner,
443
+ repo,
444
+ prNumber,
445
+ issueNumber,
446
+ success: true,
447
+ });
448
+ } catch (summaryError) {
449
+ reportError(summaryError, {
450
+ context: 'attach_watch_working_session_summary',
451
+ prNumber,
452
+ owner,
453
+ repo,
454
+ autoRestartCount,
455
+ operation: 'attach_working_session_summary',
456
+ });
457
+ await log(formatAligned('', `⚠️ Working session summary error: ${cleanErrorMessage(summaryError)}`, '', 2));
458
+ }
459
+
424
460
  // Issue #1107: Attach log after each auto-restart session with its own cost estimation
425
461
  // This ensures each restart has its own log comment instead of one combined log at the end
426
462
  const shouldAttachLogs = argv.attachLogs || argv['attach-logs'];
@@ -478,34 +514,6 @@ export const watchForFeedback = async params => {
478
514
  }
479
515
  }
480
516
 
481
- // Issue #1728: Attach a "Working session summary" comment for this
482
- // iteration if the AI didn't post any comments of its own (and
483
- // --auto-attach-solution-summary is enabled, which it is by default).
484
- // Same fix as in solve.auto-merge.lib.mjs — every working session,
485
- // not just the top-level run, should honour the auto-attach flag.
486
- try {
487
- await maybeAttachWorkingSessionSummary({
488
- argv,
489
- resultSummary: toolResult.resultSummary,
490
- workStartTime: iterationStartTime,
491
- owner,
492
- repo,
493
- prNumber,
494
- issueNumber,
495
- success: true,
496
- });
497
- } catch (summaryError) {
498
- reportError(summaryError, {
499
- context: 'attach_watch_working_session_summary',
500
- prNumber,
501
- owner,
502
- repo,
503
- autoRestartCount,
504
- operation: 'attach_working_session_summary',
505
- });
506
- await log(formatAligned('', `⚠️ Working session summary error: ${cleanErrorMessage(summaryError)}`, '', 2));
507
- }
508
-
509
517
  await log('');
510
518
  if (isTemporaryWatch) {
511
519
  await log(formatAligned('✅', `${argv.tool.toUpperCase()} execution completed:`, 'Checking for remaining changes...'));