Monorepo: curate hackmode-scripts into maintained source-only tooling #5

New issue

Closed

opened 2026-08-16 04:52:52 +00:00 by lost-rob0t · 0 comments

lost-rob0t commented

2026-08-16 04:52:52 +00:00

(Migrated from github.com)

Problem

lost-rob0t/hackmode-scripts contains useful recon/helper source, but also generated binaries, FASLs, duplicated dependency files, and shell glue that should not be copied wholesale into the Hackmode monorepo.

Current behavior

The repo mixes maintained source with artifacts such as large ralp executables and compiled Lisp files. Some recon scripts overlap with Common Lisp recon functions already present in hackmode.

Desired behavior

Move only useful source into lost-rob0t/hackmode, under clear ownership:

reusable Common Lisp/provider logic -> source/hackmode-tools/
temporary compatibility scripts -> tools/legacy/
rules/fixtures needed at runtime -> a source-controlled data/rules directory
generated binaries/FASLs -> excluded

Architecture

Scripts are migration inputs, not a permanent parallel product. Each migrated helper should either become a typed Hackmode command/provider or be explicitly marked legacy pending a Common Lisp port.

Implementation scope

inventory every script/source file
classify overlap with existing Hackmode recon code
migrate non-duplicated useful source
add .gitignore rules for generated Lisp/binary artifacts if needed
document replacement/port status
leave destructive/exploitation helpers outside the recon architecture unless separately designed

Dependencies

Depends on #4 monorepo layout.

Acceptance criteria

no large generated executables or FASLs enter the monorepo
every migrated helper has an owner/path and migration status
duplicated recon behavior is consolidated rather than copied
old repo can be archived/read-only after verification

Verification

compare source inventory before/after
inspect monorepo for generated artifacts
run smoke tests for migrated maintained helpers where dependencies are available

## Problem `lost-rob0t/hackmode-scripts` contains useful recon/helper source, but also generated binaries, FASLs, duplicated dependency files, and shell glue that should not be copied wholesale into the Hackmode monorepo. ## Current behavior The repo mixes maintained source with artifacts such as large `ralp` executables and compiled Lisp files. Some recon scripts overlap with Common Lisp recon functions already present in `hackmode`. ## Desired behavior Move only useful source into `lost-rob0t/hackmode`, under clear ownership: - reusable Common Lisp/provider logic -> `source/hackmode-tools/` - temporary compatibility scripts -> `tools/legacy/` - rules/fixtures needed at runtime -> a source-controlled data/rules directory - generated binaries/FASLs -> excluded ## Architecture Scripts are migration inputs, not a permanent parallel product. Each migrated helper should either become a typed Hackmode command/provider or be explicitly marked legacy pending a Common Lisp port. ## Implementation scope - inventory every script/source file - classify overlap with existing Hackmode recon code - migrate non-duplicated useful source - add `.gitignore` rules for generated Lisp/binary artifacts if needed - document replacement/port status - leave destructive/exploitation helpers outside the recon architecture unless separately designed ## Dependencies Depends on #4 monorepo layout. ## Acceptance criteria - no large generated executables or FASLs enter the monorepo - every migrated helper has an owner/path and migration status - duplicated recon behavior is consolidated rather than copied - old repo can be archived/read-only after verification ## Verification - compare source inventory before/after - inspect monorepo for generated artifacts - run smoke tests for migrated maintained helpers where dependencies are available