microfe-ggnomad
Part of the Burdenoff platform by AlgoShred.
Getting Started
See AGENTS.md for development commands and architecture details.
Storybook
Component stories live under src/stories/*.stories.tsx. Every story that renders a
component driving a GraphQL mutation (BookingPanel, ListingEditDialog) wraps itself
with @apollo/client/testing's MockedProvider — never a live ApolloClient — plus
MemoryRouter and GGNomadProvider where the component needs routing/context.
bun run storybook # Dev server at http://localhost:6006
bun run build-storybook # Static build -> storybook-static/ (gitignored; CI uploads it as an artifact)
bun run test:storybook # Run interaction (play function) tests against an already-running Storybook
bun run test:storybook:ci # Build, serve, and test in one shot (what CI runs)
test:storybook is powered by @storybook/test-runner, which drives each story's play
function in a real (Playwright-controlled) browser — this is how interactive components
(quantity steppers, form saves, dialog cancel) get regression coverage without a full
app-shell E2E run. bun run sanity includes build-storybook (catches story build
breakage); CI (pr-check.yml) additionally runs the interaction-test pass via
test:storybook:ci and uploads the static build as a workflow artifact.
Travel planner
The /planner page supports an explicitly reviewed trip brief and personalized
recommendations through GGNomad's existing metered, read-only shared Ask
transport. Unknown brief facts remain unspecified. Recommendations can use
only the loaded, bounded inventory snapshot; model-supplied IDs, prices,
checkout fields and malformed responses are rejected. The traveler can apply
reviewed suggestions, prioritize a real listing, generate a grounded proposal,
select its items and explicitly save a trip plan. Saving uses the existing
server-side inventory, capacity, time and budget rules and re-prices live
listings. It does not book or pay for travel. A lost save response is reconciled
with the actor-owned proposal rather than automatically replaying the write.
Manual field entry and planning remain available when AI is unavailable.
Draft and request state is discarded across actor, tenant, organization,
workspace, project and API context changes; cancellation ignores late replies.
Dependency compatibility and interaction tests
The previous blanket glob override replaced NYC's declared glob 7 callback
API with an incompatible modern module. Blanket minimatch and
brace-expansion overrides also crossed their importers' supported major
versions. The lockfile now respects those declared ranges. Committed Bun
patches backport the upstream modern glob abort-return and minimatch
preprocessing-budget fixes, including glob 13's bundled CommonJS entry.
Legacy minimatch 3 does not have the affected preprocessing implementation.
Existing deepmerge prototype-poisoning protection remains patched.
tests/globCompat.test.ts executes real Node package imports. It checks the
legacy callback API, complete non-aborted traversal, no further directory I/O
after cancellation, bounded pattern expansion, ordinary matching and avoidance
of quadratic comparisons for large expansions in both CommonJS and ESM.
Sources: glob advisory and
minimatch upstream fix.
All 10 Chromium Storybook suites / 45 interactions passed after restoring compatible imports; the interaction step now fails the required sanity job on failure. The previous blanket claim that every story necessarily fails is superseded by this actual execution. Browser verification of the deployed product remains a separate release requirement. Package audits still identify patched package versions by their registry numbers; retain the audit findings and functional patch evidence rather than suppressing those advisories.
License
Proprietary — Copyright Burdenoff Consultancy Services Pvt. Ltd.
Package publication enables MFE_DTS=1 for both alpha and stable builds. The required PR build and both publication workflows run bun scripts/check-package-exports.mjs to verify every declared runtime and TypeScript entry before publication. The guard rejects missing or empty declarations and exports outside the packaged dist tree. Its offline tests include the JavaScript-only stable failure shape.